Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team at a regulated financial institution is architecting a data platform on Google Cloud that must comply with strict data residency regulations in Germany. The compliance rules mandate that all data at rest—including database records, object storage, analytical datasets, and cryptographic keys—must remain exclusively within Germany (europe-west3). Additionally, the relational database must maintain automated failover capabilities for business continuity without transferring data across country borders.
Which architecture meets all regulatory compliance, data residency, and high-availability requirements?
This architecture combines Google Cloud Resource Location Restriction organization policies with regional resource placement, in-region high availability, and localized Customer-Managed Encryption Keys (CMEK) via Cloud Key Management Service (Cloud KMS). It strictly aligns the resource hierarchy, data plane, and cryptographic key boundary within a single regulatory jurisdiction (europe-west3).
constraints/gcp.resourceLocations constraint restricted to europe-west3 ensures that no project within the resource hierarchy folder can provision services or compute outside of Germany.europe-west3 guarantees that object data and analytical tables remain strictly within the sovereign boundary.europe-west3-a and europe-west3-b) within the same region. This delivers automated sub-minute failover without transferring data across geographic borders.europe-west3 enforces localized cryptographic protection.Unlike dual-regional or multi-regional configurations that replicate data across multiple nations or geographic zones, a purely regional approach coupled with zonal high availability fulfills all uptime requirements without violating national data sovereignty laws.
This option configures multi-regional and dual-regional storage and processing services across the broader European Union (EU and eur4 which pairs europe-west4 in Eemshaven and europe-west1 in Belgium), along with cross-region replication for Cloud SQL.
EU) and dual-region Cloud Storage (eur4) distribute and replicate data across data centers outside Germany (such as the Netherlands and Belgium), violating the strict German residency mandate.europe-west1 in Belgium), breaching the national residency boundary.global keys, and global key rings do not restrict cryptographic material to specific sovereign regions.EU datasets can store and process data in any Google Cloud data center within the EU.in:eu-locations permits resource provisioning in any EU region, failing to enforce Germany-specific containment.The compliance policy permitted multi-national European Union data distribution and prioritized geographic disaster recovery across sovereign boundaries over single-country data residency.
This configuration uses a standalone, single-zone database instance in europe-west3 combined with multi-region backup storage and a centralized key management strategy in europe-west1 (Belgium).
EU Cloud Storage bucket causes backup files containing sensitive financial data to be replicated across various non-German data centers.europe-west1 cannot encrypt Cloud SQL, Cloud Storage, or BigQuery resources in europe-west3.The architecture allowed cross-border backup archiving and centralized key administration while accepting downtime during infrastructure outages.
This configuration correctly localizes the Cloud SQL database, BigQuery datasets, and Cloud Storage buckets within europe-west3, but specifies a multi-region EU Cloud KMS key ring for encryption management.
EU key ring cannot be bound to regional resources in europe-west3.EU multi-region key ring allows key material and cryptographic operations to reside and execute across Google Cloud data centers outside Germany, violating the mandate that cryptographic keys must remain exclusively in Germany.The entire platform—including BigQuery and Cloud Storage—was architected as multi-region EU workloads and organizational policies permitted pan-European cryptographic key storage.
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