An enterprise runs a mission-critical transactional workload on a Cloud SQL instance in the us-central1 region. The organization needs to design a disaster recovery (DR) strategy that meets the following business continuity requirements: Provide cross-region redundancy to a secondary region (us-east4) with minimal Recovery Time Objective (RTO). Enable immediate failover to the secondary region during an unplanned regional outage. Ensure point-in-time recovery (PITR) is automatically established on the promoted instance. Prevent loss of un-replicated writes by automatically capturing a final backup of the original primary instance once it recovers, and re-establishing the cross-region replication topology. Which replication and recovery strategy should the cloud architect implement?

Configure a cross-region read replica in `us-east4` and use Cloud SQL advanced disaster recovery to invoke a replica failover during an outage.: ### What Cloud SQL cross-region replica failover is **Cloud SQL Advanced Disaster Recovery (DR)** allows organizations to provision a cross-region read replica in an alternate region (such as `us-east4`) and perform an immediate **replica failover** during an unexpected disaster or regional outage. ### How it meets the requirements - **Immediate cross-region failover**: Executing a replica failover immediately promotes the designated cross-region DR replica to assume the primary role, minimizing the **Recovery Time Objective (RTO)**. - **Automatic PITR provisioning**: Upon promotion, the backup and transaction log retention configuration is copied from the old primary to the new primary, and an initial backup is initiated immediately so that **Point-in-Time Recovery (PITR)** becomes available. - **Split-brain data preservation**: When the old primary instance in `us-central1` comes back online after the disaster, Cloud SQL automatically takes a final backup to preserve any split-brain transactions that occurred before the primary went offline. - **Automated topology rebuild**: After taking the final backup, Cloud SQL automatically rebuilds the recovered instance as a read replica of the newly promoted primary instance in `us-east4`. ### Key advantages and capabilities - **Automated topology re-establishment**: Avoids tedious manual reconstruction of replication streams after regional recovery. - **Endpoint updating**: Seamlessly directs database write endpoints to the promoted instance when using private network architectures. - **Comprehensive data integrity**: Retains previous backup policies while isolating un-replicated transactions via post-recovery backups. ### Why this is optimal This approach provides an out-of-the-box, fully managed solution that fulfills all data persistence, backup continuity, and automated multi-region topology requirements without custom scripting or significant administrative overhead.

StudyCerts

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

Section: Business continuity plan

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 runs a mission-critical transactional workload on a Cloud SQL instance in the us-central1 region. The organization needs to design a disaster recovery (DR) strategy that meets the following business continuity requirements:

Provide cross-region redundancy to a secondary region (us-east4) with minimal Recovery Time Objective (RTO).
Enable immediate failover to the secondary region during an unplanned regional outage.
Ensure point-in-time recovery (PITR) is automatically established on the promoted instance.
Prevent loss of un-replicated writes by automatically capturing a final backup of the original primary instance once it recovers, and re-establishing the cross-region replication topology.

Which replication and recovery strategy should the cloud architect implement?

Enable High Availability (HA) with regional persistent disks on the primary instance, and configure the recreate lagging replica parameter to 300 seconds.

Configure an external read replica in us-east4 using pglogical or binlog replication, manually execute a promote command during a regional failure, and rebuild the primary instance from a manual export after the disaster resolves.

Deploy a Cloud Storage multi-region bucket to store scheduled hourly database exports, and script an automated Cloud Function to spin up a new instance in us-east4 upon failure.

Configure a cross-region read replica in us-east4 and use Cloud SQL advanced disaster recovery to invoke a replica failover during an outage.

Professional Cloud Architect

Cloud Sql Cross Region Dr Replica Failover

Related questions