In Cloud SQL for MySQL, which deployment achieves high availability and disaster recovery while maintaining low read and write latency in the primary region?

Question

Options

• ASingle zonal Cloud SQL instance
• BCloud SQL primary in one region with cross region read replica
• CAlloyDB for PostgreSQL
• DCloud SQL primary in one zone with same region read replica in another zone

• A
  4% (1)
• B
  18% (5)
• C
  7% (2)
• D
  71% (20)

Explanation

A Cloud SQL primary instance with an HA standby and a read replica both placed in different zones within the same region achieves: (1) High availability-automatic failover to the standby zone keeps the service up during a zone outage; (2) Read offloading-the in-region read replica handles analytical or reporting queries without leaving the region; (3) Low write latency-all writes stay within the region, avoiding cross-region replication lag. Option A (single zone) has no redundancy. Option B (cross-region replica) introduces write latency because replication crosses regions and does not improve primary-region HA. Option C (AlloyDB) is a different product entirely.

No community discussion yet for this question.