Enforce Data Residency Bigquery Organization Policy

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A financial enterprise is building a data analytics platform on Google Cloud to process highly confidential transaction records subject to strict national data residency mandates. Regulatory compliance requires that all data at rest, data processing workloads, and API traffic termination remain strictly within Belgium (europe-west1), preventing any cross-border data transfer.

Which architectural strategy should the data engineering team implement to satisfy these compliance and data residency requirements?

Enforce the Resource Locations Organization Policy constraint restricted to europe-west1, create Cloud Storage buckets and BigQuery datasets in the europe-west1 region, and direct API traffic to BigQuery regional endpoints.

Enforce the Resource Locations Organization Policy constraint for the EU multi-region, provision Cloud Storage buckets and BigQuery datasets in the EU multi-region location, and use global BigQuery API endpoints.

Create Cloud Storage buckets in europe-west1, create BigQuery datasets in the europe-west4 region, and use BigQuery Data Transfer Service to replicate tables between regions.

Deploy an EUR4 dual-region Cloud Storage bucket, create the BigQuery dataset in the europe-west1 region, and rely on BigQuery dynamic location routing to manage query execution.

Professional Cloud Data Engineer

Enforce Data Residency Bigquery Organization Policy

Related questions