An automotive manufacturer headquartered in Germany is deploying its autonomous vehicle telemetry and clinical research dataset on Google Cloud. To satisfy European Union data sovereignty regulations and internal governance policies, the cloud architecture must strictly ensure two outcomes: first, that storage and compute infrastructure cannot be provisioned outside designated European Union geographic locations; second, that Google support personnel cannot access customer data without explicit, loggable customer approval. Which TWO architectural mechanisms should the Lead Cloud Architect implement to satisfy these compliance requirements? (Select TWO.)
- Configure an Organization Policy with the Resource Locations constraint (constraints/gcp.resourceLocations) restricted to the EU location group across the resource hierarchy.Answer
- Enable Access Approval at the Organization level to require administrative review and approval before Google personnel can access data during support operations.Answer
- CApply restrictive IAM Custom Roles with view-only privileges across all storage buckets to guarantee that authorized internal users cannot copy data to external Cloud Storage buckets in other regions.
- DMandate Customer-Supplied Encryption Keys (CSEK) for all Cloud Storage buckets and BigQuery datasets to enforce region-restricted key ring locations managed in Cloud KMS.
Answer
The architect should enforce an Organization Policy with the Resource Locations constraint restricted to EU regions, and enable Access Approval at the Organization level to require customer consent before Google personnel can access data.
Enforcing the Resource Locations organization policy ensures that all newly provisioned resources (such as Compute Engine, GKE, BigQuery, and Cloud Storage) are constrained to European Union regions. Enabling Access Approval complements this by ensuring Google support and operations engineers cannot access customer datasets without explicit, audited authorization from the customer.
Step-by-Step Solution
Key Concept
Data Sovereignty and Administrative Access Controls in GCP