Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
Your financial enterprise processes sensitive customer transaction records subject to strict European Union data residency and sovereignty regulations. The compliance policy mandates the following requirements:
europe-west3 (Frankfurt) region.europe-west3, while maintaining resilience against potential single-zone capacity constraints or outages.How should you configure the architecture to enforce compliance and data sovereignty while ensuring job execution resilience?
europe-west3. Enforce the gcp.resourceLocations organization policy for europe-west3. Launch the Dataflow job specifying --region=europe-west3 without setting the --zone parameter.This architecture establishes strict regional data residency and governance controls using location-bound Cloud KMS keys, organization policy constraints, and Cloud Dataflow regional job execution.
europe-west3 satisfies data sovereignty and complies with CMEK location constraints.gcp.resourceLocations organization policy constraint restricted to europe-west3 guarantees that no storage, compute, or cryptographic resources can be provisioned outside the authorized boundary.--region=europe-west3 and omitting the --zone flag directs Dataflow to route worker VMs dynamically across any healthy zone strictly within europe-west3 based on availability, ensuring resilience against zonal failures while maintaining geographic containment.europe-west3.europe-west3 regional boundary.This approach directly satisfies EU regulatory data boundaries and CMEK requirements while leveraging regional elasticity for fault tolerance.
europe-west3 and generate Cloud KMS keys in the europe multi-region location. Launch the Dataflow job specifying --region=europe-west3 and an explicit --zone=europe-west3-a parameter.This option attempts to use a multi-regional Cloud KMS location (europe) to protect single-region storage assets while pinning Dataflow worker execution to a single specific zone (europe-west3-a).
global. CMEK rules mandate that regional resources must use keys from the exact same regional location.europe-west3.--zone=europe-west3-a pins worker instances to a single zone, causing job failures if that specific zone suffers resource exhaustion or outages.The workload had pan-European multi-region availability requirements and did not require strict single-region data residency.
europe-west3 and provision Cloud KMS keys in the global location. Launch the Dataflow pipeline specifying --region=europe-west3 and configure Dataflow workers to execute in europe-west1.This option proposes using global Cloud KMS keys and configuring Dataflow's control plane in europe-west3 while executing compute worker nodes in a separate region (europe-west1).
global location replicates key metadata globally, which violates sovereignty mandates. Furthermore, executing worker nodes in europe-west1 while data resides in europe-west3 transmits unencrypted data in transit across regional boundaries.gcp.resourceLocations constraint would block worker creation in europe-west1.The application was globally distributed with no geographic data residency restrictions.
europe-west3 and generate Cloud KMS keys in europe-west3. Enforce the gcp.restrictNonCmekServices constraint, and execute Dataflow jobs by setting --zone=europe-west3-b while omitting the --region flag.This configuration attempts to run Dataflow by configuring an explicit worker zone (--zone=europe-west3-b) without specifying the required Dataflow regional endpoint (--region).
--region flag for job submission and control plane management; relying solely on --zone is anti-pattern and can lead to execution failures or default routing.europe-west3-b removes Dataflow's capability to mitigate zonal outages by automatically scheduling worker VMs in other available zones within the region.gcp.resourceLocations leaves the project vulnerable to unauthorized deployments in other geographic regions.A dedicated single-zone deployment was explicitly required and multi-zone failover was undesirable.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated