Free Google Professional Cloud Database Engineer Actual Exam Questions - Question 8 Discussion
backups are expensive and add maintenance overhead. You want to follow Google-recommended
practices to migrate the database to Google Cloud, and you need to ensure minimal downtime. What
should you do?
Makes sense to avoid the dump import since it’s slow and causes downtime. Option D sounds like the best fit because creating an external replica lets you keep data synced continuously without heavy maintenance. Plus, it matches Google’s recommended approach for minimal downtime migrations from on-prem MySQL to Cloud SQL.
D, external replica syncs live data, unlike C’s slow dump import.
I’m ruling out A right away since GKE isn’t really a managed database service and importing a dump can cause downtime. B relies on a dump which is slow and causes downtime, so that’s out too. Between C and D, D stands out because creating an external replica allows continuous data sync, reducing downtime. But if the network or MySQL version doesn’t support external replicas, then C could be needed as a fallback. Does the question imply if external replication is fully supported in their environment? That seems key to deciding between C and D.
C/D? I see why D is popular for minimal downtime since it syncs continuously, but if the on-prem version or network setup doesn’t support external replicas, it might not work. C could be a fallback if you want to control the environment fully, though it might mean more downtime during the dump/import. So if external replica setup isn’t feasible, spinning up MySQL on a Compute Engine VM and importing the dump could be the next best.
Minimal downtime and syncing data continuously fits option D best, no doubt. D
Probably D, external replica keeps sync with minimal downtime.