- A
Cloud Source Repositories pull requests without restrictions.
Why wrong: Any user can merge without review.
- B
Cloud Deploy with manual approval.
Why wrong: Cloud Deploy is for deployment, not source control.
- C
Cloud Source Repositories with branch protection rules that require pull request reviews and passing status checks.
Enforces mandatory code reviews and CI checks.
- D
Cloud Build triggers with approval gates.
Why wrong: Approval gates are for deployment pipelines, not code reviews.
Quick Answer
The correct tool is Cloud Source Repositories with branch protection rules that require pull request reviews and passing status checks. This is the native Git-based mechanism within CSR that enforces code reviews by blocking direct pushes to protected branches and mandating approval from designated reviewers before a merge can occur. On the Google Professional Cloud Developer exam, this concept tests your understanding of how to integrate Cloud Build status checks with branch policies to create a secure, compliant CI/CD workflow. A common trap is assuming a separate third-party tool is needed, when in fact CSR’s built-in branch protection rules, combined with Cloud Build triggers, provide the complete enforcement. Remember it as “protect the branch, require the review, pass the check” — that’s the three-part rule for mandatory code reviews in Cloud Source Repositories.
PCD Building and testing applications Practice Question
This PCD practice question tests your understanding of building and testing applications. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
A team is using Cloud Source Repositories and wants to enforce code reviews before merging. What tool should they use?
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
Cloud Source Repositories with branch protection rules that require pull request reviews and passing status checks.
Cloud Source Repositories (CSR) integrates with Cloud Build and Git. To enforce mandatory code reviews before merging, you configure branch protection rules on the CSR repository. These rules require pull request reviews and passing status checks (e.g., from Cloud Build), preventing direct pushes to protected branches. This is the native Git-based mechanism for enforcing review workflows.
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.
- ✗
Cloud Source Repositories pull requests without restrictions.
Why it's wrong here
Any user can merge without review.
- ✗
Cloud Deploy with manual approval.
Why it's wrong here
Cloud Deploy is for deployment, not source control.
- ✓
Cloud Source Repositories with branch protection rules that require pull request reviews and passing status checks.
Why this is correct
Enforces mandatory code reviews and CI checks.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Cloud Build triggers with approval gates.
Why it's wrong here
Approval gates are for deployment pipelines, not code reviews.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing deployment approval gates (Cloud Deploy or Cloud Build) with repository-level merge controls, leading candidates to pick a CI/CD tool instead of the correct branch protection feature within Cloud Source Repositories.
Detailed technical explanation
How to think about this question
Branch protection rules in CSR are enforced server-side via Git hooks and the CSR API, rejecting any push that violates the rules (e.g., missing required reviews or failing status checks). The required status checks can be configured to reference specific Cloud Build trigger results, ensuring that only code passing CI/CD pipelines can be merged. In a real-world scenario, a team might require two approvals and a passing Cloud Build test before merging, with the rule blocking any direct push to the main branch even from repository admins.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
- →
Building and testing applications — study guide chapter
Learn the concepts, then practise the questions
- →
Building and testing applications practice questions
Targeted practice on this topic area only
- →
All PCD questions
500 questions across all exam domains
- →
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
- →
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Designing highly scalable, available, and reliable cloud-native applications practice questions
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Building and testing applications practice questions
Practise PCD questions linked to Building and testing applications.
Deploying applications practice questions
Practise PCD questions linked to Deploying applications.
Integrating Google Cloud services practice questions
Practise PCD questions linked to Integrating Google Cloud services.
Managing application performance monitoring practice questions
Practise PCD questions linked to Managing application performance monitoring.
PCD fundamentals practice questions
Practise PCD questions linked to PCD fundamentals.
PCD scenario practice questions
Practise PCD questions linked to PCD scenario.
PCD troubleshooting practice questions
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Start a free PCD practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PCD question test?
Building and testing applications — This question tests Building and testing applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Cloud Source Repositories with branch protection rules that require pull request reviews and passing status checks. — Cloud Source Repositories (CSR) integrates with Cloud Build and Git. To enforce mandatory code reviews before merging, you configure branch protection rules on the CSR repository. These rules require pull request reviews and passing status checks (e.g., from Cloud Build), preventing direct pushes to protected branches. This is the native Git-based mechanism for enforcing review workflows.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 25, 2026
This PCD 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 PCD exam.
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.
Sign in to join the discussion.