Correct Answer: Only files stored in the $HOME directory (/home/user), which is backed by a persistent 5 GB disk
Cloud Shell provides a persistent 5 GB home directory (`$HOME`) backed by a disk that persists across sessions. Files written outside `$HOME` (e.g., in `/tmp`, installed system pac...
Correct Answer
Only files stored in the $HOME directory (/home/user), which is backed by a persistent 5 GB disk
Why This Answer Is Correct
Cloud Shell provides a persistent 5 GB home directory (`$HOME`) backed by a disk that persists across sessions. Files written outside `$HOME` (e.g., in `/tmp`, installed system packages via `apt`) are lost when the session ends — the VM itself is ephemeral. This means you can persist scripts, SSH keys, `.bashrc`, `.gcloud` config, and project files in `$HOME`, but not globally installed tools (re-install them in `~/.bashrc` or use `cloudshell_open` startup scripts).
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?
A developer needs to preview a web application running on port 8080 inside Cloud Shell without exposing it publicly. What feature enables this?