- A
Use 'constraints/compute.vmExternalIpAccess' with a condition that denies external IPs unless the project has a specific label.
Why wrong: Organization policies cannot use labels in conditions; they use resource tags or other attributes.
- B
Set the policy 'constraints/compute.vmExternalIpAccess' to 'Allowed' at the organization level and 'Denied' on each project except the approved ones.
Why wrong: This would require manual configuration on every project; not scalable.
- C
Create a custom constraint to block external IPs and apply it to all projects except the approved ones.
Why wrong: Custom constraints are not needed; the built-in constraint works with conditions.
- D
Set 'constraints/compute.vmExternalIpAccess' to 'Deny' at the organization level, then create a tag-based condition to allow external IPs for approved projects.
This is the correct method: deny at org level, then use conditions to allow for projects with a specific tag.
PCDE Practice Question: Bootstrapping a Google Cloud Organisation for DevOps
This PCDE practice question tests your understanding of bootstrapping a google cloud organisation for devops. 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 DevOps engineer needs to ensure that no Compute Engine VM in the organization can have an external IP address, except for a specific set of approved projects. Which organization policy configuration 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
Set 'constraints/compute.vmExternalIpAccess' to 'Deny' at the organization level, then create a tag-based condition to allow external IPs for approved projects.
Organization policies support inheritance and conditions. Setting policy to 'Enforce' at the organization level with a condition to exclude approved projects (e.g., resource.matchTag:env/approved-external-ip) ensures only those projects can have external IPs.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use 'constraints/compute.vmExternalIpAccess' with a condition that denies external IPs unless the project has a specific label.
Why it's wrong here
Organization policies cannot use labels in conditions; they use resource tags or other attributes.
- ✗
Set the policy 'constraints/compute.vmExternalIpAccess' to 'Allowed' at the organization level and 'Denied' on each project except the approved ones.
Why it's wrong here
This would require manual configuration on every project; not scalable.
- ✗
Create a custom constraint to block external IPs and apply it to all projects except the approved ones.
Why it's wrong here
Custom constraints are not needed; the built-in constraint works with conditions.
- ✓
Set 'constraints/compute.vmExternalIpAccess' to 'Deny' at the organization level, then create a tag-based condition to allow external IPs for approved projects.
Why this is correct
This is the correct method: deny at org level, then use conditions to allow for projects with a specific tag.
Related concept
Standard ACLs match source addresses.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
- Standard ACLs match source addresses.
- Extended ACLs can match source, destination, protocol and ports.
- The first matching ACL entry is used.
- There is usually an implicit deny at the end.
TExam Day Tips
- Check inbound versus outbound direction.
- Read the ACL from top to bottom.
- Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
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.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related PCDE ACL questions on filtering logic and placement.
- →
Bootstrapping a Google Cloud Organisation for DevOps — study guide chapter
Learn the concepts, then practise the questions
- →
Bootstrapping a Google Cloud Organisation for DevOps practice questions
Targeted practice on this topic area only
- →
All PCDE questions
1,000 questions across all exam domains
- →
Google Professional Cloud Database Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Building and Implementing CI/CD Pipelines for a Service practice questions
Practise PCDE questions linked to Building and Implementing CI/CD Pipelines for a Service.
Bootstrapping a Google Cloud Organisation for DevOps practice questions
Practise PCDE questions linked to Bootstrapping a Google Cloud Organisation for DevOps.
Applying Site Reliability Engineering Practices to a Service practice questions
Practise PCDE questions linked to Applying Site Reliability Engineering Practices to a Service.
Implementing Service Monitoring Strategies practice questions
Practise PCDE questions linked to Implementing Service Monitoring Strategies.
Optimising Service Performance practice questions
Practise PCDE questions linked to Optimising Service Performance.
Plan and manage database infrastructure practice questions
Practise PCDE questions linked to Plan and manage database infrastructure.
Define data structures and implement SQL for Business Intelligence practice questions
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Design and implement database schemas practice questions
Practise PCDE questions linked to Design and implement database schemas.
Monitor and optimize database performance practice questions
Practise PCDE questions linked to Monitor and optimize database performance.
PCDE fundamentals practice questions
Practise PCDE questions linked to PCDE fundamentals.
PCDE scenario practice questions
Practise PCDE questions linked to PCDE scenario.
PCDE troubleshooting practice questions
Practise PCDE questions linked to PCDE troubleshooting.
Practice this exam
Start a free PCDE 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 PCDE question test?
Bootstrapping a Google Cloud Organisation for DevOps — This question tests Bootstrapping a Google Cloud Organisation for DevOps — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Set 'constraints/compute.vmExternalIpAccess' to 'Deny' at the organization level, then create a tag-based condition to allow external IPs for approved projects. — Organization policies support inheritance and conditions. Setting policy to 'Enforce' at the organization level with a condition to exclude approved projects (e.g., resource.matchTag:env/approved-external-ip) ensures only those projects can have external IPs.
What should I do if I get this PCDE question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related PCDE ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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: Jul 4, 2026
This PCDE 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 PCDE 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.