1Z0-1123-25 Question 34
Single answerAn enterprise is planning to migrate a multi-tier on-premises application to Oracle Cloud Infrastructure using the Oracle Cloud Migrations Service. The application� web and application servers depend on a shared database, and the migration team wants to ensure minimal downtime while preserving these dependencies. Which approach should they use to maintain proper order of migration tasks so that the database and its dependent servers continue to work correctly throughout the migration?
- A
Use wave-based migrations within Oracle Cloud Migrations, grouping dependent servers and the database in the same wave to ensure automated orchestration and minimal downtime.
- B
Migrate the web and application servers independently first, and then handle the database migration as a separate process once all application tiers have been moved.
- C
Shut down the database before starting any migration tasks to ensure data consistency, and then restart the database after the servers have been migrated.
- D
Assign all servers to a single wave without distinguishing dependencies, allowing tasks to run in any order and relying on final synchronization steps.
Show answer and explanation
Correct answer: A
Explanation
Oracle Cloud Migrations Service supports creating migration plans with wave-based groupings, allowing you to orchestrate migration tasks in a prescribed sequence. By placing servers and their databases in the same wave, you ensure the necessary dependency connections remain intact throughout the migration. This approach aligns with OCI best practices and is covered in the Oracle Cloud Infrastructure documentation on orchestrating migrations with waves.
- A. Correct.
Correct. Wave-based migrations in Oracle Cloud Migrations allow you to group interdependent resources in a single wave, ensuring the migration tasks execute in a specific order and maintaining minimal downtime for related components.
- B. Incorrect.
Incorrect. Migrating web and application servers first could cause downtime or data access issues if the database isn�t migrated in sync. Oracle Cloud Migrations recommends grouping dependent resources together for seamless transition.
- C. Incorrect.
Incorrect. Forcing a complete shutdown of the database before migrating any servers is excessively disruptive and does not leverage the orchestration features of Oracle Cloud Migrations that help minimize downtime.
- D. Incorrect.
Incorrect. Placing everything in a single wave without considering dependencies leads to uncoordinated migration steps. While Oracle Cloud Migrations does allow wave-based or single-wave migrations, ignoring dependencies can result in significant application downtime.