Your customer is running a MySQL database on-premises with read replicas. The nightly incremental backups are expensive and add maintenance overhead. You want to follow Google- recommended practices…

Question

Options

• ACreate a Google Kubernetes Engine (GKE) cluster, install MySQL on the cluster, and then import
• BUse the mysqldump utility to take a backup of the existing on-premises database, and then import
• CCreate a Compute Engine VM, install MySQL on the VM, and then import the dump file.
• DCreate an external replica, and use Cloud SQL to synchronize the data to the replica.

• A
  6% (2)
• B
  17% (6)
• C
  3% (1)
• D
  75% (27)

Explanation

Google's recommended practice for migrating MySQL to Google Cloud with minimal downtime is to create a Cloud SQL external replica, which continuously synchronizes data from the on-premises source database to Cloud SQL using replication. This approach keeps the Cloud SQL instance in sync with on-premises changes during the migration window, enabling a near-zero-downtime cutover. Installing MySQL on a GKE cluster (A) or a Compute Engine VM (C) sacrifices managed service benefits and is not Google-recommended. Using mysqldump (B) takes a point-in-time snapshot, so it does not stay in sync with new changes and typically requires downtime for cutover.

No community discussion yet for this question.