Google Professional Cloud Database Engineer Question 228
Select 2Google Cloud PlatformYour company is planning to migrate its MySQL database from an on-premises data center to Google Cloud. The database is 3 TB in size, has minimal downtime tolerance, and includes complex stored procedures and triggers. Which database migration tool(s) should you use to achieve this migration efficiently?
- A
Database Migration Service (DMS)
- B
Backup and Restore using Cloud Storage
- C
Cloud SQL Auth Proxy
- D
Third-party replication tools like Striim or Attunity
- E
Custom JDBC/ODBC-based migration script
Show answer and explanation
Correct answers: A, D
Explanation
Database Migration Service (DMS) is the best choice for migrating MySQL databases to Google Cloud with minimal downtime, as it supports replication and handles complex database features. Third-party tools like Striim or Attunity can also be used when additional flexibility or compatibility is required. Other options like backup and restore or custom scripts are less efficient and do not satisfy the minimal downtime requirement.
- A. Correct.
Database Migration Service (DMS) is a managed solution provided by Google Cloud that supports MySQL migrations. It allows minimal downtime migrations using continuous replication and is highly suitable for this use case.
- B. Incorrect.
Backup and Restore using Cloud Storage is a viable option for database migration, but it does not support minimal downtime as it requires a full database backup and restore process, potentially leading to extended downtime.
- C. Incorrect.
Cloud SQL Auth Proxy is a tool for securely connecting to Cloud SQL instances but is not a database migration tool. It is irrelevant for this scenario.
- D. Correct.
Third-party replication tools like Striim or Attunity can handle large database migrations with minimal downtime, and they support complex scenarios such as stored procedures and triggers. This makes them a valid choice for this use case.
- E. Incorrect.
A custom JDBC/ODBC-based migration script may be used for migrations but requires significant development effort and does not inherently support minimal downtime, making it less efficient for this scenario.