A multinational financial services company must design an analytics architecture in Google Cloud that adheres to strict European Union (EU) data sovereignty regulations and organizational disaster recovery (DR) mandates. The system has the following requirements: Cloud Storage Data Lake: Raw transaction logs must provide cross-region active-active redundancy with an automated failover (RTO = 0), a predictable Recovery Point Objective (RPO) of 15 minutes or less, and guarantee that data never leaves two designated EU regions: Netherlands (europe-west4) and Frankfurt (europe-west3). BigQuery Data Warehouse: Analytical data must be protected against regional outages within the allowed sovereign boundaries, recognizing that default multi-region dataset configurations do not provide automated cross-region replication. Regulatory & Compliance: Data at rest and during replication must strictly remain within the specified geographic borders without traversing unapproved regional locations. Which combination of storage topologies and configurations meets these requirements?

Configure a Cloud Storage custom dual-region bucket using `europe-west4` and `europe-west3` with turbo replication enabled; deploy BigQuery datasets in `europe-west4` and configure BigQuery cross-region dataset replication to `europe-west3`.: ### What the Solution Is This configuration leverages **Cloud Storage dual-regions** with **turbo replication** alongside **BigQuery cross-region dataset replication** between two specifically chosen regions (`europe-west4` and `europe-west3`) to achieve high availability, tight RPO/RTO goals, and strict data residency compliance. ### How It Meets the Requirements - **Cloud Storage Data Lake**: A dual-region bucket allows precise selection of the two geographic regions (`europe-west4` and `europe-west3`), ensuring that data at rest never leaves the approved jurisdictions. Enabling **turbo replication** guarantees a **15-minute RPO** (replicating 100% of newly written objects within 15 minutes), while dual-region architecture inherently provides active-active access with an **RTO of zero** during a regional outage. - **BigQuery Data Warehouse**: Because standard BigQuery multi-region configurations (such as the `EU` multi-region) store data within a single region without cross-region replication, explicitly deploying a primary dataset in `europe-west4` and setting up **cross-region dataset replication** (or managed disaster recovery) to `europe-west3` ensures cross-region durability and failover capability. - **Regulatory & Compliance**: Explicit regional pairings ensure total adherence to data sovereignty laws by restricting replication traffic exclusively between the Netherlands and Frankfurt. ### Key Advantages - **Guaranteed RPO SLA**: Turbo replication lowers the dual-region RPO target from 12 hours to 15 minutes. - **Deterministic Data Locality**: Avoids undefined multi-region data placement, satisfying granular data residency mandates. - **Seamless Object Access**: Cloud Storage dual-regions maintain a single bucket namespace with transparent failover. - **Resilient Data Warehousing**: Protects BigQuery analytics against catastrophic regional loss. ### Why This Is Optimal Unlike multi-regional buckets that dynamically place data across broader geographic areas, custom dual-regions provide exact geographic control over physical storage locations while meeting rigorous disaster recovery benchmarks.