SAP-C03 practice question: Discovery, portfolio assessment and migration waves
Resilience, Migration, and Business Continuity A free question from our original SAP-C03 practice exam. Try it, then open the answer to see why each option is right or wrong.
A utility company plans to move about 600 applications out of its data centers over three years. The portfolio has no complete list of which servers talk to which applications, and some business systems share a single Oracle database.
The migration office wants waves that move each application together with the systems it depends on, so no wave breaks a live process. Each wave must also fit the maintenance windows the operations team already runs.
Which approach meets these requirements?
Choose one answer.
AA. Group the applications by the department that owns them, and move each department in one wave in the order shown on the org chart.
BB. Use AWS Transform to collect server inventory and network dependency data over a full business cycle, then plan waves that move dependent systems, including shared-database ones, together.
CC. Move the largest applications first, because their cost savings are the biggest, and then move the smaller applications in whatever order the application teams request during each maintenance window.
DD. Migrate all 600 applications in a single weekend cutover with a rollback plan, so that the dependency questions do not need answering before the move.
Show the answer and explanation
Answer: B
A. Wrong: Department groupings ignore the network and database links between applications, so a wave can move a system while the systems it calls stay behind. The approach breaks live processes.
B. Right: Correct. Dependency data collected over a full cycle exposes the real links between systems, including shared databases and month-end traffic. Waves built from that map keep dependent systems together and can be scheduled inside the existing maintenance windows.
C. Wrong: Size and savings do not show which systems depend on each other, so the first waves can break the smaller systems that call them. The order also ignores the maintenance windows.
D. Wrong: A single cutover of 600 applications has no realistic rollback window, and the operations team would need to coordinate every dependency at once. The approach fails the wave and window requirements.
Explanation
Discovery over a full business cycle reveals the real dependencies, including shared databases, and waves built from it move dependent systems together inside the existing windows. Org-chart groupings, size-based ordering and a single cutover all ignore dependencies or the operations constraints.
Want more on Discovery, portfolio assessment and migration waves? The 5 full-length practice sets have 6 more Discovery, portfolio assessment and migration waves questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →