Objective 1.2

PCDE

Managing infrastructure

Objective 1.2 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-2Bootstrapping and maintaining a Google Cloud organization

A team's module outputs an instance name by reading back the input variable that supplied it. What does that construction cost them?

Terraform rejects the output at plan timeNothing is rejected. The configuration stays valid and applies cleanly, which is what makes the defect hard to notice.
The implicit dependency on the resource is lostCorrect · your answerCorrect: point the output at an attribute of the created object.
The output stops appearing in generated documentationDescriptions are still expected on every output and are pulled into generated module documentation.
The output value is computed before apply runsTiming is not the issue here; the value is available either way, and ordering is what breaks.

Correct.

Concept

A declarative graph is built from references between resources. Reading a value from the same place that fed it in yields a value that looks correct and a graph that has quietly shed an edge.

Why B

Guidance is to reference an attribute of the resource itself. Routing a value back out through the variable that supplied it stops Terraform from recording that the output rests on the resource.

Source

pass outputs directly through input variables, because doing so prevents them from being properly added to the dependency graph.

Google Cloud: Best practices for general style and structure, checked August 2026
#terraform#modules#outputs

Now you: objective 1.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-2Bootstrapping and maintaining a Google Cloud organization

An engineer is deciding which module variables deserve default values. Which kind of variable should be left with no default at all?

Sample question 2 of 3

1-2Bootstrapping and maintaining a Google Cloud organization

A team maintaining a shared module wants to avoid breaking callers. Which change to the module's variables is the backwards-incompatible one?

Sample question 3 of 3

1-2Bootstrapping and maintaining a Google Cloud organization

An engineer sets count from a variable carrying an attribute of a resource that does not exist yet. Terraform reports that the value of count cannot be computed. What resolves it?

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