An enterprise is deploying a mission-critical relational database on Google Cloud using Cloud SQL for MySQL. The database design must meet the following disaster recovery and availability requirements: Provide automated failover with zero data loss (RPO = 0) and minimal downtime during an unexpected zonal outage in the primary region. Provide business continuity and disaster recovery capabilities in a secondary region with low RTO and RPO in the event of an entire regional failure. Maintain architectural simplicity by using managed Google Cloud native replication mechanisms. Which database architecture should you implement?

Configure the primary Cloud SQL instance with high availability (HA) enabled across two zones in the primary region, and create a cross-region read replica in the secondary region that can be promoted in a disaster.: ### What Cloud SQL HA and Cross-Region Replication Is **Cloud SQL High Availability (HA)** uses synchronous data replication across two zones within the same region (a primary instance and a standby instance). A **cross-region read replica** replicates data asynchronously from the primary instance to a distinct secondary Google Cloud region, where it serves read traffic during normal operations and can be manually or programmatically promoted to a standalone read-write primary database during a catastrophic regional disaster. ### How It Meets the Requirements - **Zonal Availability (RPO = 0, Low RTO):** Cloud SQL HA uses synchronous block-level regional persistent disk storage across two zones. If the primary zone fails, Cloud SQL automatically detects the failure and initiates an **automated failover** to the standby instance in the secondary zone without data loss (RPO = 0) in under a few minutes. - **Regional Disaster Recovery (Low RPO & RTO):** Asynchronous replication to the **cross-region read replica** continuously streams database changes. In a regional outage, promoting the replica creates a functional primary database in the secondary region with minimal Recovery Point Objective (RPO) and low Recovery Time Objective (RTO). - **Architectural Simplicity:** Both HA configuration and read replica provisioning are native, fully managed features of Cloud SQL. ### Key Advantages and Capabilities - **Automated Zonal Failover:** Eliminates manual intervention for localized infrastructure failures. - **Independent Compute and Storage Failover:** Uses managed regional persistent disks to ensure storage consistency across zones. - **Disaster Recovery Promotion:** The replica promotion command dissociates the replica and turns it into an independent read-write primary instance quickly. - **Read Offloading:** The cross-region replica can serve local read queries during normal operational periods. ### Why This Is Optimal This architecture pairs **synchronous zonal replication** for continuous high availability with **asynchronous cross-region replication** for disaster recovery, perfectly balancing performance, cost, and stringent RTO/RPO objectives.

StudyCerts

Cloud Sql Ha Cross Region Dr Architecture | 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

Cloud Sql Ha Cross Region Dr Architecture

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 enterprise is deploying a mission-critical relational database on Google Cloud using Cloud SQL for MySQL. The database design must meet the following disaster recovery and availability requirements:

Provide automated failover with zero data loss (RPO = 0) and minimal downtime during an unexpected zonal outage in the primary region.
Provide business continuity and disaster recovery capabilities in a secondary region with low RTO and RPO in the event of an entire regional failure.
Maintain architectural simplicity by using managed Google Cloud native replication mechanisms.

Which database architecture should you implement?

Deploy a single Cloud SQL instance and configure an external on-premises replica using binary logging and manual GTID synchronization.

Configure a single-zone Cloud SQL instance with automated daily backups stored in a multi-region Cloud Storage bucket, and restore the backup to the secondary region during an outage.

Configure the primary Cloud SQL instance with high availability (HA) enabled across two zones in the primary region, and create a cross-region read replica in the secondary region that can be promoted in a disaster.

Deploy two standalone single-zone Cloud SQL instances in different regions and configure the application tier to perform synchronous dual writes to both database endpoints.

Professional Cloud Architect

Cloud Sql Ha Cross Region Dr Architecture

Related questions