Q: 15
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 to migrate the database to Google Cloud, and you need to ensure minimal downtime. What should you do?
Options
Discussion
Its B in my opinion. Using mysqldump and importing into Cloud SQL seems easier and more straightforward, even though it might mean a bit more downtime. Maybe I'm missing something but that's how I've done smaller migrations before.
Not B, D. Live replication to Cloud SQL helps minimize downtime and Google's docs say this is preferred.
Nah, mysqldump (B) isn't right if you want minimal downtime-D lets you sync changes while staying live.
Yeah, D makes sense since using an external replica lets you sync changes and do a quick cutover. Full dump/import like in B would mean much more downtime. Pretty sure this is the right Google-recommended approach unless there's a version mismatch.
Its D, super clear scenario and matches what Google recommends for minimal downtime migrations.
Be respectful. No spam.