professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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.
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.
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.
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.
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.
This architecture combines Google Cloud Organization Policies, localized single-region resource placement in BigQuery and Cloud Storage, and BigQuery regional endpoints to enforce strict data sovereignty and residency boundaries within a single geographic territory.
StudyCerts
StudyCertsconstraints/gcp.resourceLocations) at the organization or folder level restricts the deployment of all supported storage and compute resources exclusively to europe-west1, blocking non-compliant provisioning attempts.europe-west1 single region ensures data at rest is stored strictly within Belgium. When BigQuery runs queries against or loads data from colocated single-region datasets, the compute execution and temporary shuffle data remain confined to that specific region.bigquery.europe-west1.rep.googleapis.com ensures that TLS sessions terminate inside europe-west1 and prevents API requests or in-transit data from being routed through global entry points outside the regulatory boundary.This configuration provides end-to-end data residency at the resource configuration, query processing, and network transit layers without risking the broader geographic distribution inherent in multi-region or dual-region services.
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.
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.
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.