An enterprise hosts a critical transaction processing application on Google Cloud. The primary database runs on Cloud SQL in the us-central1 region. As part of a business continuity audit, the architecture team must design a cross-region disaster recovery (DR) strategy to protect against a total regional outage while meeting the following technical requirements: Minimize Recovery Point Objective (RPO) and Recovery Time Objective (RTO) by maintaining continuous data replication to the us-east4 region. Allow immediate promotion of the secondary database instance during a disaster event. Automatically redirect database write traffic without requiring manual IP updates across application tiers. Automatically re-establish automated backup schedules and Point-in-Time Recovery (PITR) in the recovery region after promotion. Which disaster recovery architecture should you implement to satisfy these requirements?

Create a cross-region read replica in `us-east4` as a designated DR replica, configure applications to connect using the Cloud SQL DNS write endpoint, and execute a replica failover to promote the instance during a disaster.: What Cloud SQL Cross-Region DR Replica and Replica Failover Is Cloud SQL cross-region replication provides asynchronous replication of database transactions from a primary instance in one region to a read replica in a secondary region. When combined with Cloud SQL Advanced Disaster Recovery (DR) features, administrators can designate a replica for disaster recovery and invoke an immediate replica failover during a regional outage. How It Meets the Requirements Continuous Replication & Low RPO/RTO: Asynchronous cross-region replication continuously streams transactions to us-east4, keeping data up to date and enabling an immediate promotion with minimal replication lag. Immediate DR Promotion: Executing a replica failover immediately promotes the designated us-east4 DR replica to assume the primary role. Automated Traffic Redirection: By using the Cloud SQL DNS write endpoint, client connection strings do not require modification; the DNS write endpoint automatically updates its mapping to resolve to the newly promoted primary instance upon failover. Automated Backup & PITR Resumption: Upon promotion via replica failover, Cloud SQL automatically copies backup configuration and transaction log retention policies to the new primary, enables transaction logging, and initiates a baseline backup to re-enable Point-in-Time Recovery (PITR). Key Advantages and Capabilities Seamless failover orchestration: Native gcloud sql instances promote-replica --failover command coordinates promotion and metadata reconfiguration. DNS write endpoint integration: Eliminates hardcoded IP dependencies across microservices. Automated state reconciliation: When the original primary in us-central1 recovers, Cloud SQL can automatically reconfigure it as a read replica of the new primary. End-to-end data protection: Preserves automated backup schedules across regional boundaries. Why This Is Optimal This solution uses Google Cloud's fully managed database replication and disaster recovery lifecycle management. It eliminates custom failover scripting, manual IP address reconfigurations, and manual backup reconfiguration in the target region.

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 Cross Region Dr Failover

Section: Disaster recovery

An enterprise hosts a critical transaction processing application on Google Cloud. The primary database runs on Cloud SQL in the us-central1 region. As part of a business continuity audit, the architecture team must design a cross-region disaster recovery (DR) strategy to protect against a total regional outage while meeting the following technical requirements:

Minimize Recovery Point Objective (RPO) and Recovery Time Objective (RTO) by maintaining continuous data replication to the us-east4 region.
Allow immediate promotion of the secondary database instance during a disaster event.
Automatically redirect database write traffic without requiring manual IP updates across application tiers.
Automatically re-establish automated backup schedules and Point-in-Time Recovery (PITR) in the recovery region after promotion.

Which disaster recovery architecture should you implement to satisfy these requirements?

Set up Database Migration Service (DMS) continuous change data capture (CDC) to a standalone Cloud SQL instance in us-east4, and trigger a migration promote operation during a regional failure.

Configure Cloud SQL high availability (HA) with regional persistent disks across zones, and configure an external Application Load Balancer with Serverless NEGs to route database traffic across regions.

Export daily Cloud SQL automated backups to a multi-regional Cloud Storage bucket, and restore the backup to a newly created instance in us-east4 during a disaster.

Create a cross-region read replica in us-east4 as a designated DR replica, configure applications to connect using the Cloud SQL DNS write endpoint, and execute a replica failover to promote the instance during a disaster.

Professional Cloud Architect

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Cloud Sql Cross Region Dr Failover

Section: Disaster recovery

Minimize Recovery Point Objective (RPO) and Recovery Time Objective (RTO) by maintaining continuous data replication to the us-east4 region.
Allow immediate promotion of the secondary database instance during a disaster event.
Automatically redirect database write traffic without requiring manual IP updates across application tiers.
Automatically re-establish automated backup schedules and Point-in-Time Recovery (PITR) in the recovery region after promotion.

Which disaster recovery architecture should you implement to satisfy these requirements?

Set up Database Migration Service (DMS) continuous change data capture (CDC) to a standalone Cloud SQL instance in us-east4, and trigger a migration promote operation during a regional failure.

Export daily Cloud SQL automated backups to a multi-regional Cloud Storage bucket, and restore the backup to a newly created instance in us-east4 during a disaster.

Explanations

What Cloud SQL Cross-Region DR Replica and Replica Failover Is

Cloud SQL cross-region replication provides asynchronous replication of database transactions from a primary instance in one region to a read replica in a secondary region. When combined with Cloud SQL Advanced Disaster Recovery (DR) features, administrators can designate a replica for disaster recovery and invoke an immediate replica failover during a regional outage.

How It Meets the Requirements

Continuous Replication & Low RPO/RTO: Asynchronous cross-region replication continuously streams transactions to us-east4, keeping data up to date and enabling an immediate promotion with minimal replication lag.
Immediate DR Promotion: Executing a replica failover immediately promotes the designated us-east4 DR replica to assume the primary role.
Automated Traffic Redirection: By using the Cloud SQL DNS write endpoint, client connection strings do not require modification; the DNS write endpoint automatically updates its mapping to resolve to the newly promoted primary instance upon failover.
Automated Backup & PITR Resumption: Upon promotion via replica failover, Cloud SQL automatically copies backup configuration and transaction log retention policies to the new primary, enables transaction logging, and initiates a baseline backup to re-enable Point-in-Time Recovery (PITR).

Key Advantages and Capabilities

Seamless failover orchestration: Native gcloud sql instances promote-replica --failover command coordinates promotion and metadata reconfiguration.
DNS write endpoint integration: Eliminates hardcoded IP dependencies across microservices.
Automated state reconciliation: When the original primary in us-central1 recovers, Cloud SQL can automatically reconfigure it as a read replica of the new primary.
End-to-end data protection: Preserves automated backup schedules across regional boundaries.

Why This Is Optimal

This solution uses Google Cloud's fully managed database replication and disaster recovery lifecycle management. It eliminates custom failover scripting, manual IP address reconfigurations, and manual backup reconfiguration in the target region.

View source documentation

Professional Cloud Architect

Cloud Sql Cross Region Dr Failover

Professional Cloud Architect

Cloud Sql Cross Region Dr Failover

What Cloud SQL Cross-Region DR Replica and Replica Failover Is

How It Meets the Requirements

Key Advantages and Capabilities

Why This Is Optimal

Related questions