Google ACE Setting Up a Cloud Solution Environment Practice Question
A developer wants to use Cloud Shell for managing GCP resources. Which three statements about Cloud Shell are true? (Choose THREE.)
⚠ Common exam trap
The trap here is assuming Cloud Shell is a full VM with unlimited uptime and billing dependency — candidates often confuse its free, ephemeral nature with a persistent Compute Engine instance.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
It provides a web-based terminal in the GCP Console
Option C is correct because Cloud Shell is a web-based terminal accessible directly from the Google Cloud Console, allowing users to run commands and manage GCP resources without installing local tools. Option D is correct because Cloud Shell provides 5 GB of persistent disk storage mounted at $HOME, which persists across sessions and is tied to the user, not the VM instance. Option E is correct because Cloud Shell images come pre-installed with common tools including gcloud CLI, kubectl, and terraform, so developers can immediately manage GCP resources and Kubernetes clusters. Option A is not correct because Cloud Shell sessions have a timeout (typically 20 minutes of inactivity and a maximum session duration of 12 hours), so sessions are not unlimited. Option B is not correct because Cloud Shell can be used in projects without billing enabled, though some operations may require billing; Cloud Shell itself is free and available to any authenticated user.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It allows unlimited session duration without any timeout
Why it's wrong here
Cloud Shell sessions are subject to a 1-hour idle timeout and a 12-hour maximum session lifetime, even if you maintain continuous activity. This means you cannot keep a session running indefinitely, and any long-running processes that must survive beyond that time should be run on a Compute Engine VM or a different persistent infrastructure. The ephemeral nature is by design, as Cloud Shell is intended for interactive administrative work rather than as a general-purpose compute host.
- ✗
It can be used only for projects that have billing enabled
Why it's wrong here
Cloud Shell itself is a free service and does not require a billing account to be attached to your Google Cloud account or the current project. You can access the shell even in projects that have no billing enabled, as the shell runs on Google's infrastructure rather than on billable resources. However, if you use gcloud commands within the shell to create or modify resources like virtual machines, those resources must belong to a project with billing enabled for the charges to be applied.
- ✓
It provides a web-based terminal in the GCP Console
Why this is correct
Cloud Shell is a web-based terminal that launches directly from the Google Cloud Console, giving you authenticated command-line access to your GCP environment without needing to install the Google Cloud SDK locally. It automatically authenticates you using the same credentials as the console, and it also sets the current project so you can immediately run gcloud commands. This integration makes it the quickest way to test API calls, run kubectl against GKE clusters, or inspect resources while staying in the browser.
- ✓
It provides 5 GB of persistent disk storage in the user's home directory
Why this is correct
Each Cloud Shell user receives a persistent home directory stored on a 5 GB disk that survives session restarts and is available even after the underlying VM is reclaimed. This space is useful for storing your dotfiles, shell scripts, and small data files between sessions, but it is not shared across users and should not be treated as durable or backed-up storage. For significant data persistence you should use Cloud Storage or persistent disks attached to compute instances.
- ✓
It has gcloud, kubectl, and terraform pre-installed
Why this is correct
Cloud Shell comes pre-installed with the Google Cloud SDK (including gcloud and kubectl), Terraform, and many other utilities, and these tools are automatically updated to the latest versions whenever you start a new session. This removes the overhead of manual installation and version management, so you can immediately run commands like gcloud compute instances list, kubectl get pods, or terraform plan. The environment is based on a Debian Linux container, and you can additionally install other packages with apt if needed.
Go deeper
Related to this question
Learn chapter
Google Cloud Deploy for CD
Key term
Anthos
Anthos is a Google Cloud platform that lets you run applications consistently across different computing environments, like on-premises data centers and multiple public clouds.
Key term
Google Cloud
Google Cloud is a suite of cloud computing services offered by Google that provides infrastructure, platform, and software solutions over the internet.
About these practice questions
One of 775 original ACE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.