Troubleshooting AWS MGN: Boot Volume Missing Boot Sector
A company is using AWS Application Migration Service (MGN) to migrate hundreds of on-premises servers to AWS. After the migration, some servers fail a health check. What is the most efficient way to remediate the failed servers?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Launch test instances from MGN, diagnose the issues, then update the source servers and perform a final cutover.
It follows the recommended MGN workflow for remediation: launch test instances to identify issues, fix them on the source server, and then perform a final cutover. Option B is inefficient as it restarts the entire replication and cutover process without testing. Option C is incorrect because restoring from a backup AMI is not part of the MGN migration process and does not allow iterative fixes. Option D is wrong because CloudEndure Migration is the former name of MGN and is not a separate service for re-migration.
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 test instances from MGN, diagnose the issues, then update the source servers and perform a final cutover.
Why this is correct
MGN test instances let you validate each server in AWS before cutover, so boot and health-check failures are diagnosed and fixed on the source servers first. This avoids repeated cutover attempts, making remediation efficient across hundreds of servers.
- ✗
Rerun the MGN replication and perform a new cutover.
Why it's wrong here
Rerunning replication and cutover re-copies every block from source, so it cannot fix post-migration guest-level faults such as driver or service failures, and it repeats the full cutover window. It suits recovering from a corrupted initial sync or a botched cutover, not targeted remediation of individual failed servers.
- ✗
Restore the servers from the latest AMI and re-run the health check.
Why it's wrong here
Restoring the latest AMI reinstates the same post-migration state that already failed the health check, so the fault persists; it also discards any in-guest fixes. It is the right approach for recovering a server whose instance or root volume was corrupted after a successful migration.
- ✗
Use AWS CloudEndure Migration to re-migrate the servers.
Why it's wrong here
CloudEndure Migration is the predecessor product superseded by AWS Application Migration Service, so it cannot re-migrate servers already cut over by MGN. It is tempting because it performed the same lift-and-shift function historically, and would be correct only for legacy migrations not already using MGN.
Go deeper
Related to this question
About these practice questions
One of 984 original SAP-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.