mediumMultiple ChoiceObjective-mapped
Data Residency with Organization Policy — Resource Location Constraints
A multinational organization must ensure that data for European users is stored only within the European Union to comply with GDPR. They use Cloud Storage and BigQuery. Which design should they implement?
Quick Answer
The answer is to set an organization policy with the constraint `gcp.resourceLocations` to restrict resource creation to EU regions. This is correct because this organization policy constraint acts as a proactive, API-level guardrail that denies any attempt to create a Cloud Storage bucket or BigQuery dataset outside of allowed locations, such as `europe-west1` or `europe-west4`. For the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of how to enforce data residency with organization policy resource locations, a key concept for GDPR compliance. A common trap is to rely on IAM permissions or bucket-level retention policies, which only react to data after it exists, rather than preventing non-compliant resource creation at the source. Remember the memory tip: “Policy before provision” — organization policies are the only way to enforce location constraints before a resource is even created, making them the definitive tool for proactive data residency control.
⚠ Common exam trap
Google Cloud often tests the distinction between data access control and data residency enforcement; the trap here is confusing geo-based access controls (Cloud Armor) or data exfiltration prevention (VPC Service Controls) with the ability to restrict where data is physically stored, which requires a resource location policy.
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 an organization policy with constraints/gcp.resourceLocations to restrict resource creation to EU regions.
The organization policy constraint `gcp/resourceLocations` is the only design that proactively prevents data from being stored outside the EU. By setting this constraint to allow only EU regions (e.g., `europe-west1`, `europe-west4`), any attempt to create a Cloud Storage bucket or BigQuery dataset in a non-EU region will be denied at the API level, ensuring GDPR compliance by design.
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 Cloud DLP to inspect and tag data for European origin.
Why it's wrong here
DLP does not enforce where data is stored.
- ✗
Use VPC Service Controls to create a perimeter around European resources.
Why it's wrong here
VPC Service Controls prevent exfiltration but do not enforce storage location.
- ✓
Set an organization policy with constraints/gcp.resourceLocations to restrict resource creation to EU regions.
Why this is correct
Organization policies can enforce that resources like buckets and datasets are created only in allowed locations.
- ✗
Use Cloud Armor with geo-based access control to restrict access from non-EU locations.
Why it's wrong here
Cloud Armor controls access to applications, not storage location of data.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PCSE question from scratch — 960 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PCSE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A multinational organization must store customer data only in specific geographic regions to comply with data residency regulations. They use Cloud Spanner for their primary database. What should they do to enforce that data is stored only in approved regions?
easy- ✓ A.Apply an organization policy with a constraint that restricts the location of Cloud Spanner resources to approved regions.
- B.Create a Cloud Spanner instance in the desired region and configure a backup in a different region for disaster recovery.
- C.Configure a VPC Service Controls perimeter to restrict access to Cloud Spanner.
- D.Use Cloud Spanner with data residency constraints by selecting a multi-region configuration that includes only approved regions.
Why A: Organization policies with resource location constraints allow you to enforce that Cloud Spanner instances are created only in approved geographic regions. This policy is evaluated at resource creation time and prevents the deployment of Spanner instances outside the specified regions, directly addressing data residency compliance requirements.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCSE 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 PCSE exam.