3.1 Design and Implement Data Migration and Replication PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   What is the purpose of a fallback plan in a database migration?

   • ATo eliminate the need for data validation
   • BTo revert to the source system if the migration fails or issues arise
   • CTo automatically convert DDL statements
   • DTo speed up the migration process
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A company is migrating a 5 TB MySQL database to Cloud SQL. The business requires near-zero downtime, but the team has limited experience with Database Migration Service. They are considering using a dual-write strategy instead. What is the most significant risk of the dual-write approach?

   • AData inconsistency between the source and target if a write fails on one side.
   • BThe source database will experience increased load due to the extra writes.
   • CThe application will need to be modified to write to two databases, which is complex.
   • DThe migration will take longer than using DMS.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A team is planning an extended outage migration of a 2 TB PostgreSQL database to Cloud SQL. The migration window is 3 hours. The team has already performed a test migration that took 2.5 hours. What should they do to ensure the actual migration fits within the window?

   • ASkip the validation step to save time.
   • BUse a larger Cloud SQL instance to speed up the migration.
   • CAllocate additional time for validation and rollback procedures in the migration plan.
   • DStart the migration earlier than the scheduled window.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   What is a key characteristic of an extended outage migration approach?

   • AIt requires no validation of data after migration
   • BIt requires a scheduled downtime window during which the source is stopped and data is migrated
   • CIt uses reverse replication to keep the source updated after cutover
   • DIt keeps the source and target synchronized in real time with no downtime
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A company is migrating its on-premises SQL Server database to Cloud SQL for SQL Server using Database Migration Service with continuous replication. The migration is planned to take several weeks, and the business requires the ability to revert to the on-premises database at any point during the migration if issues arise. What should the team configure to ensure this fallback capability?

   • ASet up reverse replication from Cloud SQL back to the on-premises SQL Server so that any changes on the target are applied to the source.
   • BTake a full backup of the source before starting the migration and restore it if needed, accepting that changes made during migration will be lost.
   • CUse a third-party tool to perform dual-writes from the application to both databases, ensuring both are always synchronized.
   • DKeep the source database in read-write mode and rely on the continuous replication job to keep it synchronized with the target.
   Reveal Solution Discussion Select an answer first