← PCDOE·Google Cloud

Question 110 of 500

Bootstrapping a Google Cloud organization for DevOps →hardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the Staging and Prod targets are missing the `require_approval` attribute set to `true`. This is the most likely cause because Cloud Deploy treats any target without this explicit flag as automatically approved, meaning the pipeline will promote to the next environment without pausing for a manual gate. When you set up a delivery pipeline with sequential targets, each target must individually declare `require_approval: true` to enforce an approval step; otherwise, the promotion proceeds immediately after a successful deployment, which explains why your pipeline skipped Staging and Prod approvals. On the Google Professional Cloud DevOps Engineer exam, this scenario tests your understanding of Cloud Deploy’s approval mechanics—a common trap is assuming that approval is inherited from a folder or project level, but it must be configured per target. A useful memory tip is "no flag, no gate"—if you don't see `require_approval: true` on a target, expect automatic promotion.

PCDOE Practice Question: Bootstrapping a Google Cloud organization for DevOps

This PCDOE practice question tests your understanding of bootstrapping a google cloud organization for devops. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Your company is bootstrapping a Google Cloud organization for DevOps. The organization consists of three folders: Dev, Staging, and Prod. Each folder contains multiple projects for different microservices. You have been tasked with setting up a centralized CI/CD pipeline using Cloud Build and Cloud Deploy. The pipeline must deploy to multiple environments in sequence: Dev → Staging → Prod. Each environment requires approval from a different approver group. You have set up Cloud Deploy delivery pipelines with targets pointing to each environment. However, during testing, you notice that after a successful deployment to Dev, the pipeline automatically proceeds to Staging without waiting for approval. What is the most likely cause and solution?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1hardmultiple choice

Full question →

A
Cause: The delivery pipeline is defined with a single target instead of multiple targets. Solution: Create separate delivery pipelines for each environment.
Why wrong: Incorrect: A single pipeline can have multiple targets; the issue is approval configuration.
B
Cause: The delivery pipeline has a single promotion sequence that includes all targets. Solution: Remove Staging and Prod from the pipeline and create separate pipelines.
Why wrong: Incorrect: A single promotion sequence is normal; approval is independent.
C
Cause: The Cloud Deploy service account lacks the `clouddeploy.approver` role on Staging and Prod projects. Solution: Grant the role to the service account.
Why wrong: Incorrect: Approval skipping is not due to permissions; the pipeline doesn't wait for approval if not configured.
D
Cause: The targets in Staging and Prod are missing the `require_approval` attribute set to `true`. Solution: Add `require_approval: true` to the Staging and Prod target definitions.
Correct: Without `require_approval: true`, Cloud Deploy proceeds automatically.

Full breakdown with real-world context →

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

✓

Cause: The targets in Staging and Prod are missing the `require_approval` attribute set to `true`. Solution: Add `require_approval: true` to the Staging and Prod target definitions.

The correct answer is D because Cloud Deploy requires explicit `require_approval: true` on each target to enforce manual approval gates. Without this attribute, the pipeline treats the target as automatically approved and proceeds to the next target in the promotion sequence. The behavior described—automatic progression after Dev—indicates that Staging and Prod targets lack this flag, causing the pipeline to skip the approval step.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Cause: The delivery pipeline is defined with a single target instead of multiple targets. Solution: Create separate delivery pipelines for each environment.
Why it's wrong here
Incorrect: A single pipeline can have multiple targets; the issue is approval configuration.
✗
Cause: The delivery pipeline has a single promotion sequence that includes all targets. Solution: Remove Staging and Prod from the pipeline and create separate pipelines.
Why it's wrong here
Incorrect: A single promotion sequence is normal; approval is independent.
✗
Cause: The Cloud Deploy service account lacks the `clouddeploy.approver` role on Staging and Prod projects. Solution: Grant the role to the service account.
Why it's wrong here
Incorrect: Approval skipping is not due to permissions; the pipeline doesn't wait for approval if not configured.
✓
Cause: The targets in Staging and Prod are missing the `require_approval` attribute set to `true`. Solution: Add `require_approval: true` to the Staging and Prod target definitions.
Why this is correct
Correct: Without `require_approval: true`, Cloud Deploy proceeds automatically.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the distinction between IAM roles (like `clouddeploy.approver`) and target-level configuration (`require_approval`), leading candidates to mistakenly focus on permissions when the real issue is a missing attribute in the target definition.

Detailed technical explanation

How to think about this question

In Cloud Deploy, each target can have `require_approval: true` set in the `deployPolicy` or directly in the target YAML. When this flag is absent, the pipeline automatically promotes to the next target after a successful rollout, bypassing any manual approval. This is a common misconfiguration when setting up multi-environment pipelines, as the default behavior is automatic promotion unless explicitly overridden.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related PCDOE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Bootstrapping a Google Cloud organization for DevOps practice questions

Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.

Managing service incidents practice questions

Practise PCDOE questions linked to Managing service incidents.

Managing Google Cloud costs practice questions

Practise PCDOE questions linked to Managing Google Cloud costs.

Building and implementing CI/CD pipelines practice questions

Practise PCDOE questions linked to Building and implementing CI/CD pipelines.

Implementing service monitoring strategies practice questions

Practise PCDOE questions linked to Implementing service monitoring strategies.

Optimizing service performance practice questions

Practise PCDOE questions linked to Optimizing service performance.

PCDOE fundamentals practice questions

Practise PCDOE questions linked to PCDOE fundamentals.

PCDOE scenario practice questions

Practise PCDOE questions linked to PCDOE scenario.

PCDOE troubleshooting practice questions

Practise PCDOE questions linked to PCDOE troubleshooting.

Practice this exam

Start a free PCDOE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

PCDOE practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this PCDOE question test?

Bootstrapping a Google Cloud organization for DevOps — This question tests Bootstrapping a Google Cloud organization for DevOps — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Cause: The targets in Staging and Prod are missing the `require_approval` attribute set to `true`. Solution: Add `require_approval: true` to the Staging and Prod target definitions. — The correct answer is D because Cloud Deploy requires explicit `require_approval: true` on each target to enforce manual approval gates. Without this attribute, the pipeline treats the target as automatically approved and proceeds to the next target in the promotion sequence. The behavior described—automatic progression after Dev—indicates that Staging and Prod targets lack this flag, causing the pipeline to skip the approval step.

What should I do if I get this PCDOE question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This PCDOE 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 PCDOE exam.