An enterprise application deployed on Google Cloud requires regional high availability for a relational database workload operating within a single region. The solution must support standard ACID compliance and provide automatic failover to a secondary availability zone with minimal recovery time objective (RTO) in the event of a zonal outage. Which deployment strategy fulfills these technical availability requirements while avoiding unnecessary architectural complexity?
- Configure a Cloud SQL instance with High Availability (HA) enabled, utilizing regional persistent disk replication and a standby instance in a secondary zone within the same region.Answer
- BDeploy a multi-region Cloud Spanner instance spanning multiple geographic regions to host the relational database workload.
- CDeploy a standalone single-zone Cloud SQL instance and configure an Application Load Balancer health check to query a database table directly to trigger failover.
- DDeploy a standalone single-zone Cloud SQL instance and schedule automated daily export backups to restore manually during a zonal failure.
Answer
Configuring a Cloud SQL instance with High Availability (HA) using regional persistent disk replication and a secondary zone standby instance satisfies the single-region high availability requirements with minimal operational complexity.
Configuring Cloud SQL with High Availability (HA) provisions a primary instance in one zone and a standby instance in another zone within the same region. Data is synchronously replicated at the persistent disk layer, allowing Google Cloud to automatically fail over to the standby instance if the primary zone becomes unavailable.
Step-by-Step Solution
Key Concept
Designing Cloud SQL High Availability for Single-Region Relational Workloads