You currently have a MySQL database running on Cloud SQL with a read replica in a different zone for non-mission critical analytics workloads. You want to enable high availability (HA) for the analyti

Question

Options

• AIncrease the size of the read replica instance and enable HA.
• BEnable HA on the current read replica.
• CCreate a new HA instance in the same zone as the primary.
• DCreate a new HA instance in a different region than the primary.

• A
  11% (3)
• B
  4% (1)
• C
  85% (23)

Explanation

Creating a new HA instance in the same zone as the primary is the correct approach. In Cloud SQL for MySQL, read replicas do not support High Availability configuration - HA (with automatic failover to a standby) can only be enabled on standalone instances, not on existing read replicas. Therefore, to provide HA for analytics workloads, you must create a separate Cloud SQL instance with HA enabled. Placing it in the same zone as the primary keeps inter-zone data transfer costs low. Option A is incorrect because increasing the size of the read replica does not enable HA - Cloud SQL does not allow HA on read replicas regardless of size. Option B is incorrect for the same reason: you cannot enable HA on an existing read replica in Cloud SQL for MySQL. Option D creates an HA instance in a different region, which introduces significantly higher cross-region replication latency and egress costs - not cost-effective when the analytics workload is in the same region.

No community discussion yet for this question.