You are managing a Cloud SQL for MySQL environment in Google Cloud. You have deployed a primary instance in Zone A and a read replica instance in Zone B, both in the same region. You are notified…

Question

Options

• AUse the Google Cloud Console or gcloud CLI to manually create a new clone database.
• BUse the Google Cloud Console or gcloud CLI to manually create a new failover replica from
• CVerify that the new replica is created automatically.
• DStart the original primary instance and resume replication.

• A
  5% (2)
• C
  92% (34)
• D
  3% (1)

Explanation

Cloud SQL for MySQL automatically manages read replica availability. When a read replica experiences a brief outage (such as a zone-level disruption), Cloud SQL will automatically restart and recover the replica without manual intervention. After the 10-minute outage, the replica should self-heal. The correct action is simply to verify that the replica has automatically recovered and is replicating correctly. Option A (manually creating a new clone) is unnecessary and introduces unnecessary overhead. Option B (manually creating a new failover replica) is also unnecessary - failover replicas serve a different purpose (automatic failover for the primary) and manual creation is not needed here. Option D (starting the primary instance) is irrelevant since the primary in Zone A was not affected.

No community discussion yet for this question.