An architect is designing a mission-critical financial application on Google Cloud that must adhere to strict regulatory compliance and high-availability criteria: The architecture must deliver 99.999% database availability and survive a complete regional outage with zero data loss (RPO = 0). All data at rest and synchronous replicas must remain strictly within a single country (Germany) to satisfy national data residency laws. The compute layer must serve web traffic across multiple zones and automatically balance traffic across locations during disruptions. Which architecture should the architect recommend to satisfy these requirements while balancing cost, latency, and data residency?

Deploy a Cloud Spanner instance using a Germany dual-region configuration (`dual-region-germany1`), paired with regional Managed Instance Groups (MIGs) across both regions behind an external Application Load Balancer.: ### What Cloud Spanner Dual-Region Architecture Is **Cloud Spanner** dual-region configurations offer synchronous database replication across two Google Cloud regions located within the boundaries of a single nation. This setup provides active-active read serving and robust cross-region disaster recovery while guaranteeing that stored data never leaves the specified country. ### How It Meets the Requirements - **99.999% Availability & Regional Redundancy**: Dual-region Spanner configurations provide an industry-leading **99.999% availability SLA**, protecting the system against total regional outages by maintaining six replicas (including read-write and witness replicas) across two distinct regions (`europe-west10` Berlin and `europe-west3` Frankfurt). - **Zero Data Loss (RPO = 0)**: Synchronous replication guarantees that transactions are durably committed across voting replicas before returning success, ensuring a **Recovery Point Objective of zero** during regional service disruptions. - **Data Residency Compliance**: Base configurations such as `dual-region-germany1` enforce strict data locality within Germany, preventing regulatory violations that would occur with broader multi-region topologies. - **Compute Layer Resilience**: Utilizing **regional Managed Instance Groups (MIGs)** across zones in both regions behind an **external Application Load Balancer** provides multi-zone redundancy and seamless failover for incoming client traffic. ### Key Advantages - **Strong Consistency**: Provides external consistency and serializable transactions without sacrificing partition resilience. - **Low Read Latency**: Enables clients in both regions to perform low-latency local reads while managing writes through the default leader region. - **Automated Failover**: Google Cloud manages health monitoring and failover mechanisms across regions without requiring manual data recovery. - **Elimination of Single Points of Failure**: Combines multi-zone compute spreading with cross-region database durability. ### Why This Is Optimal A dual-region Spanner topology is specifically engineered for workloads that demand cross-region disaster recovery and 99.999% availability but are constrained by strict national data jurisdiction and governance mandates.

StudyCerts

Spanner Dual Region Data Residency High Availability | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Spanner Dual Region Data Residency High Availability

Section: High availability and fail-over design

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.

An architect is designing a mission-critical financial application on Google Cloud that must adhere to strict regulatory compliance and high-availability criteria:

The architecture must deliver 99.999% database availability and survive a complete regional outage with zero data loss (RPO = 0).
All data at rest and synchronous replicas must remain strictly within a single country (Germany) to satisfy national data residency laws.
The compute layer must serve web traffic across multiple zones and automatically balance traffic across locations during disruptions.

Which architecture should the architect recommend to satisfy these requirements while balancing cost, latency, and data residency?

Deploy a single-region Cloud Spanner instance in Frankfurt (europe-west3) with an asynchronous cross-region read-only replica located in Berlin (europe-west10).

Deploy Compute Engine VMs attached to Regional Persistent Disks configured to replicate synchronously between the Frankfurt and Berlin regions.

Deploy a Cloud Spanner instance using a Germany dual-region configuration (dual-region-germany1), paired with regional Managed Instance Groups (MIGs) across both regions behind an external Application Load Balancer.

Deploy a Cloud Spanner instance using a standard European multi-region configuration (eur5), alongside regional Managed Instance Groups in Frankfurt and Belgium.

Professional Cloud Architect

Spanner Dual Region Data Residency High Availability

Related questions