How to restrict resource location to europe-west3?
You are on the data governance team and are implementing security requirements to deploy resources. You need to ensure that resources are limited to only the europe-west3 region. You want to follow Google-recommended practices. What should you do?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This tests knowledge of Organization Policy constraints for location governance, specifically distinguishing between specific regions like europe-west3 and broader multi-regions like eu.
To restrict resource locations in Google Cloud, use the constraints/gcp.resourceLocations organization policy. The community confirms that setting this constraint to in:europe-west3-locations is the correct method to enforce regional limits.
Selecting Option C (in:eu-locations) is a common error because it restricts resources to all of Europe rather than specifically to the europe-west3 region.
Community Discussion (6 comments)
- The constraints/gcp.resourceLocations organization policy constraint is used to define where resources in the organization can be created. - Setting it to in:europe-west3-locations would specify that resources can only be created in the europe-west3 region.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A is correct because theconstraints/gcp.resourceLocations Organization Policy is the Google-recommended method to enforce where resources can be created. Setting the value to in:europe-west3-locations ensures strict compliance by preventing resource creation in any other region.Why the Other Options Are Wrong
Option B is incorrect because Terraform validations are client-side and can be bypassed by deploying via the Console or API. Option C is incorrect becausein:eu-locations permits resources in any European region, violating the requirement for europe-west3 only. Option D is incorrect because reactive remediation (destroying resources) is inefficient and risky compared to preventive policy enforcement.Community Comment Notes
Community comments overwhelmingly support Option A, citing the official Google Cloud documentation on defining location types. Commenters emphasize that this specific constraint syntax is the standard way to implement data residency and governance controls.Official Reference
Exam Strategy
For governance questions involving resource restrictions, prioritize Organization Policies over Infrastructure as Code (IaC) logic or reactive scripts. Pay close attention to whether the question requires a specific region or a broader multi-region to avoid selecting overly permissive options.