This PCDOE practice question tests your understanding of bootstrapping a google cloud organization for devops. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
An organization is using Cloud Source Repositories and wants to enforce that all commits are signed with a verified GPG key. How can they enforce this?
Use a branch protection rule in Cloud Source Repositories.
Why wrong: Does not enforce signed commits.
Use Cloud Functions to validate commits after push.
Why wrong: Reactive and not enforceable.
Enable the Signed Commits policy in the repository settings.
Native feature to require GPG-signed commits.
Use a pre-receive hook in Cloud Source Repositories.
Why wrong: Pre-receive hooks are not supported in Cloud Source Repositories.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Enable the Signed Commits policy in the repository settings.
Option C is correct because Cloud Source Repositories provides a built-in 'Signed Commits' policy in the repository settings that, when enabled, rejects any push containing commits that are not signed with a verified GPG key. This policy is enforced server-side at the repository level, ensuring that only signed commits are accepted without requiring external tools or custom scripts.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Use a branch protection rule in Cloud Source Repositories.
Why it's wrong here
Does not enforce signed commits.
Use Cloud Functions to validate commits after push.
Why it's wrong here
Reactive and not enforceable.
Enable the Signed Commits policy in the repository settings.
Why this is correct
Native feature to require GPG-signed commits.
Related concept
Read the scenario before looking for a memorised answer.
Use a pre-receive hook in Cloud Source Repositories.
Why it's wrong here
Pre-receive hooks are not supported in Cloud Source Repositories.
Common exam traps
The trap here is that candidates confuse branch protection rules (which control merge behavior) with commit signing enforcement, or assume pre-receive hooks are available in Cloud Source Repositories when they are not supported in this managed service.
Detailed technical explanation
The Signed Commits policy leverages Git's built-in GPG signing mechanism, where each commit includes a signature header (e.g., 'gpgsig') that is verified against the committer's public key. When enabled, Cloud Source Repositories checks the signature during the push operation using the 'git receive-pack' protocol, rejecting the entire push if any commit lacks a valid signature. This is critical in regulated environments (e.g., SOC 2, PCI DSS) where non-repudiation and code provenance must be enforced at the commit level, not just at merge time.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Bootstrapping a Google Cloud organization for DevOps — study guide chapter
Learn the concepts, then practise the questions
Bootstrapping a Google Cloud organization for DevOps practice questions
Targeted practice on this topic area only
All PCDOE questions
500 questions across all exam domains
Google Professional Cloud DevOps Engineer study guide
Full concept coverage aligned to exam objectives
PCDOE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Practise PCDOE questions linked to Managing service incidents.
Practise PCDOE questions linked to Managing Google Cloud costs.
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Practise PCDOE questions linked to Implementing service monitoring strategies.
Practise PCDOE questions linked to Optimizing service performance.
Practise PCDOE questions linked to PCDOE fundamentals.
Practise PCDOE questions linked to PCDOE scenario.
Practise PCDOE questions linked to PCDOE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
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..
The correct answer is: Enable the Signed Commits policy in the repository settings. — Option C is correct because Cloud Source Repositories provides a built-in 'Signed Commits' policy in the repository settings that, when enabled, rejects any push containing commits that are not signed with a verified GPG key. This policy is enforced server-side at the repository level, ensuring that only signed commits are accepted without requiring external tools or custom scripts.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
Last reviewed: Jun 25, 2026
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.
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.