Q: 2
Your organization is moving an application to Google Cloud. As part of that effort, it needs to migrate
the application’s working database from another cloud provider to Cloud SQL. The database runs on
the MySQL engine. The migration must cause minimal disruption to users. Data must be secured
while in transit.
Which should your organization use?
Options
Discussion
C . Database Migration Service is built for moving MySQL databases with minimal downtime and encrypts data in transit, which fits the question's requirements. BigQuery DTS isn't for transactional DB migration, and batch insert would cause more disruption. Not 100% if there's edge cases I missed!
C
Option C
Option C is the go-to here. Database Migration Service is built for MySQL migrations and supports minimal downtime plus encrypts data in transit. Seen similar advice in official guides, almost always points to DMS for this use case. Anyone see this handled differently?
C . Had something like this in a mock, and DMS (option C) was correct for MySQL migrations with tight downtime and secure transit. BigQuery Data Transfer isn’t meant for this kind of DB migration, and batch insert would be disruptive. Not 100% but feels right here.
A tbh
Feels like it could be A. BigQuery Data Transfer Service does handle data moves, just not sure about the minimal disruption part.
Database Migration Service (C) really fits here since it's designed for MySQL migrations with minimal user impact and secures the connection. Batch insert and BQ transfer can’t meet those downtime or security needs. I'm pretty sure DMS is what Google recommends for this, but open to correction if someone’s done it differently.
Does "minimal disruption" mean zero downtime, or is a short maintenance window acceptable? That could change if Database Migration Service (C) is the clear choice, since it supports continuous replication for near-zero downtime migration.
Be respectful. No spam.
