Google Professional Cloud Database Engineer Question 223
Select 3Google Cloud PlatformYour company is planning to migrate its on-premises PostgreSQL database to Cloud SQL for PostgreSQL on Google Cloud. The existing database has custom stored procedures and uses a proprietary extension not supported by Cloud SQL. Which of the following steps should you take to ensure a successful migration with fallback options in case of issues?
- A
Perform a schema conversion and validate compatibility using the Database Migration Assessment Tool.
- B
Set up a one-time export of data and import it directly into Cloud SQL without testing.
- C
Implement a rollback strategy by maintaining the on-premises database until the migration is fully validated.
- D
Rewrite the unsupported stored procedures and replace the proprietary extension functionality with equivalent supported features.
- E
Migrate the database directly to Cloud SQL and troubleshoot issues in production if they arise.
Show answer and explanation
Correct answers: A, C, D
Explanation
Migrating databases to Cloud SQL requires careful planning and execution. Using tools like the Database Migration Assessment Tool ensures schema compatibility, while rewriting unsupported features ensures functionality in the target database. Maintaining the source database as a fallback allows for a rollback in case of migration issues.
- A. Correct.
This is correct because the Database Migration Assessment Tool helps identify schema and compatibility issues, ensuring a smoother migration process.
- B. Incorrect.
This is incorrect because performing a one-time export without testing increases the risk of data loss or compatibility issues during migration.
- C. Correct.
This is correct since maintaining the on-premises database as a fallback ensures that you can revert if any issues arise post-migration.
- D. Correct.
This is correct because rewriting unsupported features ensures that the database remains functional and compatible in Cloud SQL.
- E. Incorrect.
This is incorrect as migrating directly to production without proper preparation or testing is a risky approach that can lead to significant downtime or data inconsistencies.