The answer is to use the Organization Policy service with a custom constraint to enforce labels on Compute Engine instances. This is correct because custom constraints act as a preventive control, using the `compute.googleapis.com/instance` resource type and CEL syntax to block the creation of any instance missing required labels like env, team, or cost-center at the moment of provisioning. On the Google Professional Cloud Architect exam, this scenario tests your understanding of policy-driven governance versus reactive solutions like Cloud Functions or IAM-based restrictions—a common trap is choosing a post-creation audit approach instead of a real-time enforcement mechanism. Remember that Organization Policies are evaluated before the resource is created, making them the only way to automatically enforce label requirements without relying on manual or scripted remediation. A useful memory tip: think of custom constraints as a "bouncer at the door" that checks labels before the instance is allowed in, not a "security camera" that catches violations later.
Google PCA Manage implementation of cloud architecture Practice Question
This PCA practice question tests your understanding of manage implementation of cloud architecture. 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.
Your organization has a policy that all Compute Engine instances must have specific labels (env, team, cost-center) applied. You want to enforce this automatically when instances are created. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the Organization Policy service with a custom constraint to require labels on Compute Engine instances.
Option D is correct because Organization Policy Service with a custom constraint allows you to enforce that all Compute Engine instances must have specific labels (env, team, cost-center) at creation time. This is a preventive control that blocks creation of non-compliant instances, unlike reactive or permission-based approaches. Custom constraints use the `compute.googleapis.com/instance` resource type and can require label keys or values using CEL (Common Expression Language) syntax.
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.
✗
Enable Cloud Audit Logs and set up a metric-based alert to detect instances without labels.
Why it's wrong here
This is detective, not preventive.
✗
Create a Cloud Function that listens for instance creation events and adds labels automatically.
Why it's wrong here
This is reactive; the instance is created without labels temporarily.
✗
Assign a custom IAM role that includes permission to label instances, and remove the default compute.instances.create permission.
Why it's wrong here
This does not enforce labels; it just restricts creation.
✓
Use the Organization Policy service with a custom constraint to require labels on Compute Engine instances.
Why this is correct
Organization policies can enforce label requirements at creation time.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose reactive solutions (like Cloud Functions or alerts) because they seem simpler, but the exam emphasizes preventive enforcement using Organization Policy constraints for compliance-driven requirements.
Detailed technical explanation
How to think about this question
Organization Policy custom constraints use the `constraints/compute.requireOsLogin` pattern but for labels, you define a custom constraint with a condition like `resource.has('labels.env') && resource.has('labels.team') && resource.has('labels.cost-center')`. This constraint is evaluated synchronously during the instance creation API call, and if it fails, the creation is denied with a PERMISSION_DENIED error. Under the hood, the constraint is enforced by the Resource Manager service, which intercepts the Compute Engine API call and checks the condition before the instance is provisioned.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this PCA question in full detail.
Manage implementation of cloud architecture — This question tests Manage implementation of cloud architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the Organization Policy service with a custom constraint to require labels on Compute Engine instances. — Option D is correct because Organization Policy Service with a custom constraint allows you to enforce that all Compute Engine instances must have specific labels (env, team, cost-center) at creation time. This is a preventive control that blocks creation of non-compliant instances, unlike reactive or permission-based approaches. Custom constraints use the `compute.googleapis.com/instance` resource type and can require label keys or values using CEL (Common Expression Language) syntax.
What should I do if I get this PCA 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 →
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.
This PCA 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 PCA 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.