- A
Create a VPC firewall rule blocking all outbound internet traffic.
Why wrong: A firewall rule can block traffic but doesn't prevent VMs from being assigned external IPs — the IP assignment happens at VM creation, before traffic policies apply.
- B
Apply the `compute.vmExternalIpAccess` org policy constraint set to deny all VMs.
This list constraint controls which VMs can have external IPs. An empty or deny-all allowedValues list prevents any VM in the folder from being created with an external IP address.
- C
Remove the `compute.instanceAdmin` role from developers so they cannot configure network interfaces.
Why wrong: Revoking compute.instanceAdmin prevents VM creation entirely — too restrictive. The requirement is to allow VM creation but only without external IPs.
- D
Configure the default VPC network to use internal-only routes.
Why wrong: Route configuration doesn't prevent external IP assignment at VM creation. VMs can be assigned external IPs regardless of route configuration.
Quick Answer
The answer is the `compute.vmExternalIpAccess` organization policy constraint set to deny all VMs. This constraint is the native Google Cloud mechanism for controlling external IP assignment on Compute Engine VMs, and when applied at the folder level, it blocks developers from provisioning VMs with public IPs while still allowing internal-only instances. On the Google Associate Cloud Engineer exam, this scenario tests your understanding of organization policy constraints versus IAM roles—a common trap is confusing this with a custom role or firewall rule, but only the `compute.vmExternalIpAccess` constraint enforces the restriction at the resource hierarchy level. Remember that organization policies are inherited, so applying a deny at the folder automatically covers all child projects. A helpful memory tip: think "VM External IP Access" as the gatekeeper—set it to deny, and no public IPs get through.
Google ACE Configuring access and security Practice Question
This ACE practice question tests your understanding of configuring access and security. 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.
You need to prevent developers from creating Compute Engine VMs with external IP addresses in a specific folder. Developers must still be able to create VMs with internal IPs only. Which org policy constraint enforces this?
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
Apply the `compute.vmExternalIpAccess` org policy constraint set to deny all VMs.
The `compute.vmExternalIpAccess` organization policy constraint is specifically designed to control whether Compute Engine VMs can be assigned external IP addresses. By setting this constraint to deny all VMs in the folder, developers are prevented from creating VMs with external IPs while still being able to create VMs with only internal IPs. This is the correct, native Google Cloud mechanism for enforcing this requirement at the folder level.
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.
- ✗
Create a VPC firewall rule blocking all outbound internet traffic.
- ✓
Apply the `compute.vmExternalIpAccess` org policy constraint set to deny all VMs.
- ✗
Remove the `compute.instanceAdmin` role from developers so they cannot configure network interfaces.
- ✗
Configure the default VPC network to use internal-only routes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse network-layer controls (firewall rules) with resource-level policies (org policy constraints), leading them to choose a firewall rule instead of the correct org policy constraint that directly governs VM creation.
Detailed technical explanation
How to think about this question
The `compute.vmExternalIpAccess` constraint is a list constraint that can be set at the organization, folder, or project level, and it uses a deny list or allow list to control which VMs can have external IPs. Under the hood, when a VM creation request includes an external IP, the Compute Engine API checks this constraint before provisioning the network interface; if denied, the request fails with a permission error. A real-world scenario is a multi-tenant folder where you want to allow internal-only VMs for security compliance while still permitting internet-facing VMs in a separate folder for public services.
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.
- →
Configuring access and security — study guide chapter
Learn the concepts, then practise the questions
- →
Configuring access and security practice questions
Targeted practice on this topic area only
- →
All ACE questions
500 questions across all exam domains
- →
Google Associate Cloud Engineer study guide
Full concept coverage aligned to exam objectives
- →
ACE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Setting up a cloud solution environment practice questions
Practise ACE questions linked to Setting up a cloud solution environment.
Planning and configuring a cloud solution practice questions
Practise ACE questions linked to Planning and configuring a cloud solution.
Deploying and implementing a cloud solution practice questions
Practise ACE questions linked to Deploying and implementing a cloud solution.
Ensuring successful operation of a cloud solution practice questions
Practise ACE questions linked to Ensuring successful operation of a cloud solution.
Configuring access and security practice questions
Practise ACE questions linked to Configuring access and security.
ACE fundamentals practice questions
Practise ACE questions linked to ACE fundamentals.
ACE scenario practice questions
Practise ACE questions linked to ACE scenario.
ACE troubleshooting practice questions
Practise ACE questions linked to ACE troubleshooting.
Practice this exam
Start a free ACE 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 ACE question test?
Configuring access and security — This question tests Configuring access and security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Apply the `compute.vmExternalIpAccess` org policy constraint set to deny all VMs. — The `compute.vmExternalIpAccess` organization policy constraint is specifically designed to control whether Compute Engine VMs can be assigned external IP addresses. By setting this constraint to deny all VMs in the folder, developers are prevented from creating VMs with external IPs while still being able to create VMs with only internal IPs. This is the correct, native Google Cloud mechanism for enforcing this requirement at the folder level.
What should I do if I get this ACE 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 11, 2026
This ACE 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 ACE 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.