BrightTrail Outfitters is moving an order processing platform from its data center to Google Cloud. The application depends on a MySQL backend that must remain highly available because it supports…

Question

Options

• AMigrate the database to multi region Cloud Spanner and refactor the schema and application so
• BSet up Cloud SQL for MySQL with regional high availability and rely on scheduled backups to
• CProvision Cloud SQL for MySQL with regional high availability and create a cross region read
• DDeploy Cloud SQL for MySQL as a single zone instance and add a read replica in another zone

• A
  3% (2)
• B
  10% (7)
• C
  82% (55)
• D
  4% (3)

Explanation

The requirements are: managed MySQL, RTO ≤ 12 minutes, RPO ≤ 12 minutes, regional incident coverage. Option C satisfies all requirements. Cloud SQL for MySQL with regional high availability uses a standby instance in a different zone within the same region; a zone failure triggers automatic failover in under 60 seconds. A cross-region read replica continuously receives binary log replication from the primary, giving an RPO measured in seconds to minutes. If the entire primary region fails, the cross-region replica can be manually promoted to a standalone instance. The total promotion time is well within the 12-minute RTO/RPO window. Option A (multi-region Cloud Spanner) would require rewriting both the schema and application code, which is a major project and not a straightforward MySQL migration. Option B relies on scheduled backups, which have an RPO equal to the backup interval (typically hours), violating the 12-minute RPO. Option D uses a single-zone instance with no HA, meaning a zone failure causes downtime until manual intervention.

No community discussion yet for this question.