Explanation:
To minimize performance impact on the currently running Cloud SQL for MySQL instance during a one-time migration to a new instance in a different region, the recommended approach is to use a SQL dump file. This method involves creating a snapshot of the data in a Cloud Storage bucket using a temporary instance, which can then be imported into the new instance. This approach is less intrusive and avoids continuous load on the source instance, unlike streaming methods. Options A and B involve more complex setups (Dataflow job and Datastream) that are better suited for continuous data replication rather than one-time migrations. Option D, while feasible, involves manual steps and potential data consistency issues, making it less ideal compared to the SQL dump method.
Ultimate access to all questions.
No comments yet.
How can you execute a one-time data migration from an active Cloud SQL for MySQL instance in us-central1 to a new instance in us-east1 while adhering to Google's best practices to reduce performance impact on the source instance?
A
Create and run a Dataflow job that uses JdbcIO to copy data from one Cloud SQL instance to another.
B
Create two Datastream connection profiles, and use them to create a stream from one Cloud SQL instance to another.
C
Create a SQL dump file in Cloud Storage using a temporary instance, and then use that file to import into a new instance.
D
Create a CSV file by running the SQL statement SELECT...INTO OUTFILE, copy the file to a Cloud Storage bucket, and import it into a new instance.