FirstTry

Objective 1.5

PCDE

Enabling secure cloud development environments

Objective 1.5 sits in Bootstrapping and maintaining a Google Cloud organization, which carries 20% of the Cloud DevOps Engineer exam. The questions below are original, written from the official objective title above, and each explanation cites the Google Cloud page it rests on.

Objective title verbatim from the official objectives. Google Cloud exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

1-5Bootstrapping and maintaining a Google Cloud organization

A developer on your team saves files outside the home directory and stops the workstation overnight. What is left at the next start?

The files survive on the attached persistent diskOnly the home directory is backed by that disk, and only when the configuration asks for it.
The files are archived into the workstation clusterA cluster groups machines in a region and attaches them to a network; it stores nothing.
The files are gone with the deleted ephemeral VMCorrect · your answerCorrect: anything outside the durable path vanishes.
The files reappear once the configuration is reappliedReapplying a template rebuilds the environment but cannot recover data that was never persisted.

Correct.

Concept

A development box rebuilt on every start gives a reproducible environment and takes away the habit of leaving state lying around. Only storage explicitly declared as durable comes back.

Why C

Stopping the machine destroys the underlying instance and everything that lived on it. Only a home directory configured for persistence is kept, on a disk attached at session start and detached at the end.

Source

When a workstation stops, its ephemeral VM is deleted along with all workstation runtime data. Administrators and platform teams can optionally configure a persistent home directory on a workstation configuration, so all data saved to the home directory persists between sessions. This persistent storage is implemented as a persistent disk that is attached to the workstation VM when the session starts, and detached when the session ends.

Google Cloud: Cloud Workstations overview, checked August 2026
#cloud-workstations#persistent-storage#developer-environments

Now you: objective 1.5 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-5Bootstrapping and maintaining a Google Cloud organization

An administrator changes the machine type inside a workstation configuration. When does an already running workstation pick that change up?

Sample question 2 of 3

1-5Bootstrapping and maintaining a Google Cloud organization

A platform team sets a running timeout on a workstation configuration. Beyond cutting cost, what does that timeout guarantee?

Sample question 3 of 3

1-5Bootstrapping and maintaining a Google Cloud organization

An engineer new to Cloud Workstations assumes a workstation cluster is a GKE cluster. What does a workstation cluster actually define?

Full Cloud DevOps Engineer question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Bootstrapping and maintaining a Google Cloud organization