SAP-C02 Practice Question: Accelerate Workload Migration and Modernization

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Launch a test instance to validate the migration

  Why this is correct

  From READY_FOR_TEST, MGN has completed initial replication and the staging area holds a bootable snapshot, so the next step is launching a test instance to validate the migrated Windows server before cutover. Testing confirms boot, drivers and applications without affecting the source, satisfying the stem's validation requirement prior to final launch.

• ✗

  Perform the cutover to the AWS environment

  Why it's wrong here

  READY_FOR_TEST signals that initial replication finished and a test instance should be launched and validated first; cutting over immediately skips that verification. Cutover is the correct action only after the test launch confirms the server boots and applications work, since it makes the AWS instance the production system.

• ✗

  Modify the source server's recommended instance type to a smaller size

  Why it's wrong here

  READY_FOR_TEST means replication has completed and the server is staged for a test launch; changing the recommended instance type is a launch-template setting, not the required next step. Resizing is legitimate later, during test or cutover configuration, when the default target instance does not match the source workload's performance profile.

• ✗

  Resume data replication from the source server

  Why it's wrong here

  Replication is already complete in READY_FOR_TEST, so resuming data replication addresses nothing; that state is reached precisely because the initial sync finished. Resuming replication is the right action after a cutover or test, when you want to return the source server to continuous replication before the next launch.

Go deeper

Related to this question