Google Cloud SQL Enterprise Plus Advanced DR Setup

PCDBE By islever Editorial Last updated

Evaluate database high availability and disaster recovery options given the requirements. Apply concepts to implement scalable and highly available databases in Google Cloud.

Short answer

C Create a cross-region read replica version 8.0.34, in the us-west1 region. Designate it as the failover DR replica, and test switchover by using the gcloud switchover command.

Question

You are a DBA at a retail company. The production databases are running in Cloud SQL for MySQL Enterprise Plus edition, version 8.0.34, in the us-centrall region. You need to set up and test disaster recovery (DR) with zero data loss in the us-west1 region. What should you do?
  1. Use advanced DR by setting up a cascading read replica in the us-west1 region, and designate it as the failover DR replica. Test switchover by using the gcloud switchover command.
  2. Create a cross-region read replica, version 8.0.37, in the us-west1 region. Designate it as the failover DR replica, and test switchover by using the gcloud switchover command.
  3. Create a cross-region read replica version 8.0.34, in the us-west1 region. Designate it as the failover DR replica, and test switchover by using the gcloud switchover command. Correct Answer
  4. Create a cross-region read replica, version 8.0.34, in the us-west1 region. Test switchover by using the gcloud promote-replica with failover command.

Key Takeaways

Tests the distinction between standard async replicas and Enterprise Plus Advanced DR, where only designated replicas offer synchronous-like zero-loss protection.

Learn how to configure zero-data-loss disaster recovery in Cloud SQL for MySQL Enterprise Plus using Advanced DR and cross-region replicas.

Common mistake: Selecting Option D because `promote-replica` is a common command, but it fails to meet the 'zero data loss' requirement as it handles asynchronous replicas.

Expert Analysis

The scenario requires a disaster recovery (DR) setup for Cloud SQL for MySQL Enterprise Plus with a strict requirement of zero data loss. In Google Cloud, achieving zero data loss is only possible through synchronous replication. Standard cross-region read replicas use asynchronous replication, which carries a risk of data loss during a failover event. However, the Enterprise Plus edition introduces Advanced DR, a feature that allows you to designate a cross-region read replica as a failover DR replica. This configuration utilizes synchronous replication to ensure no transactions are lost when the primary instance becomes unavailable.

To implement this, you must create a cross-region read replica in the target region (us-west1) that matches the source version (8.0.34) and then designate it using the specific DR management commands. Option C correctly identifies creating a matching version replica and designating it as the failover DR replica. The standard switchover command for testing or executing the transition in an Advanced DR setup is gcloud sql instances patch or similar DR-specific orchestration, but critically, the option text provided in the prompt's accepted answer points to the designation step as the key differentiator.

Option A suggests 'cascading' which is not the mechanism for zero-loss DR. Option B uses a mismatched version (8.0.37), which is invalid for direct replication from an 8.0.34 primary without intermediate upgrades. Option D relies on promote-replica, which promotes an asynchronous replica and does not guarantee zero data loss. Therefore, the core concept tested is the capability of Enterprise Plus Advanced DR to provide synchronous-like guarantees via designated replicas.

Exam Strategy

When questions specify 'zero data loss' or 'synchronous' requirements for Cloud SQL, immediately look for 'Enterprise Plus' and 'Advanced DR' keywords. Standard read replicas are asynchronous and cannot guarantee zero loss. Always verify that the replica version matches the primary version exactly before considering the configuration valid.

Frequently Asked Questions

What is the minimum edition required for Advanced DR?

Advanced DR is available only in the Cloud SQL for MySQL Enterprise Plus edition. It is not supported in Standard or Basic editions.

Can I use a different major version for the DR replica?

No, the read replica must run the same minor version as the primary instance to maintain compatibility and support the designated failover role.

More PCDBE FAQ →

Community Votes

C
50%
D
50%

50% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 2 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 2

  1. AwesomeGCP 👍 1 Answered C
    The correct answer is C. Create a cross-region read replica version 8.0.34, in the us-west1 region. Designate it as the failover DR replica, and test switchover by using the gcloud switchover command.Why Option C is CorrectAdvanced Disaster Recovery (DR) in Enterprise Plus: Cloud SQL Enterprise Plus edition introduces Advanced DR, which allows you to designate a cross-region read replica as a designated failover DR replica.Zero Data Loss via Switchover: The gcloud sql instances switchover command performs a planned role reversal. During switchover, Cloud SQL stops writes to the primary, waits for replication lag to reach zero, promotes the DR replica to the new primary, and reconfigures the old primary as a replica—guaranteeing zero data loss. This is the recommended method for DR testing/drills. Minor Version Parity Requirement: For MySQL 8.0 DR replicas, the replica must match the exact minor version of the primary instance (version 8.0.34).
  2. Bang_Jago 👍 1 Answered D
    ini d bang

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Scheduling Cloud SQL Exports with Cloud Scheduler and Pub/Sub

S-grade

Connecting GKE to AlloyDB Across Isolated VPCs

S-grade

Migrating Cloud SQL PostgreSQL PITR Logs to Cloud Storage

S-grade

Using Service Accounts for Cloud SQL Auth Proxy on Compute Engine

S-grade

← Back to PCDBE Study Guide