Correct Answer: Use Cloud Shell's Web Preview feature on port 8080, which proxies traffic through Google's infrastructure with the developer's identity
Cloud Shell's built-in **Web Preview** allows you to proxy traffic from a specific port (e.g., 8080) through Google's infrastructure to your browser session. The preview URL is aut...
Correct Answer
Use Cloud Shell's Web Preview feature on port 8080, which proxies traffic through Google's infrastructure with the developer's identity
Why This Answer Is Correct
Cloud Shell's built-in **Web Preview** allows you to proxy traffic from a specific port (e.g., 8080) through Google's infrastructure to your browser session. The preview URL is authenticated — only the logged-in user can access it. This is ideal for testing web servers, APIs, or UIs running inside Cloud Shell without any public exposure or firewall rules. Ports 8080–8084 are commonly used; others may also be available.
Your Cloud Function processes images uploaded to Cloud Storage. It intermittently times out on large files. The function is configured with 60s timeout and 256MB memory. What is the most effective fix?
A Cloud Function triggered by Pub/Sub is executing duplicate processing for some messages. Your team suspects at-least-once delivery is causing duplicate triggers. What is the recommended pattern to achieve exactly-once processing?
A developer uses Cloud Shell to run `gcloud` commands that modify production resources. As a Cloud Architect, what control should you implement to prevent accidental production changes from Cloud Shell?
A Cloud Architect needs to run a resource-intensive script (processing 10GB of data) that takes 2+ hours to complete. Cloud Shell sessions terminate after 20 minutes of inactivity. What is the best approach?
What persists between Cloud Shell sessions?