Objective 1.2

PCD

Designing secure applications

Objective 1.2 sits in Designing highly scalable, secure, and reliable cloud-native applications, which carries 32% of the Cloud Developer 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-2Designing highly scalable, secure, and reliable cloud-native applications

A team stores a database password and asks which object actually holds the bytes an application reads. Which one carries the payload?

The secret version created under itCorrect · your answerCorrect. It is the numbered layer beneath the name.
The label attached to the secretLabels describe the container so it can be found and grouped.
The secret resource and its metadataThe parent holds labels and annotations, and no payload of its own.
The IAM policy binding on itA binding decides who may read, and holds nothing readable itself.

Correct.

Concept

Separating the named container from the values it has held over time is what lets an identity and a set of permissions outlive any particular value.

Why A

The secret is a global resource holding metadata such as labels, annotations and permissions. The stored data itself lives in a version, each identified by a unique ID or timestamp.

Source

A secret is a global resource that contains a collection of metadata and secret versions. The metadata can include labels, annotations, and permissions. A secret version stores the actual secret data, such as API keys, passwords, or certificates. Each version is identified by a unique ID or timestamp.

Secret Manager overview, checked August 2026
#gcp#secret-manager#secrets#resource-model

Now you: objective 1.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-2Designing highly scalable, secure, and reliable cloud-native applications

A team needs its secrets present in a set of regions it names itself, and accepts being charged for each of those locations. Which replication policy fits?

Sample question 2 of 3

1-2Designing highly scalable, secure, and reliable cloud-native applications

After a deployment writes a bad credential into a secret, every call starts failing. Which capability restores the working value?

Sample question 3 of 3

1-2Designing highly scalable, secure, and reliable cloud-native applications

A team weighs a secrets store against a key management service for material an application reads at runtime. What separates what each will hand back?

Full Cloud Developer 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 Designing highly scalable, secure, and reliable cloud-native applications