Courseiva
← SAP-C02
Full test
Accelerate Workload Migration and Modernization →mediumMultiple ChoiceObjective-mapped

Troubleshooting AWS MGN: Boot Volume Missing Boot Sector

A company is migrating its application stack from on-premises to AWS using a rehost strategy. The stack includes a web server, an application server, and a MySQL database. The company wants to automate the migration using AWS Application Migration Service (MGN). After configuring MGN, the web server test instance fails to start because the boot volume is missing the boot sector. What is the most likely cause?

Quick Answer

The answer is that the source volume was not shut down cleanly before replication. This is the most likely cause because AWS Application Migration Service (MGN) relies on consistent, crash-consistent snapshots to replicate boot volumes; if the source server is still running or was not properly shut down, the file system may be in an inconsistent state, causing the boot sector to be missing or corrupted on the test instance. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of MGN’s prerequisite for clean volume state, often appearing as a distractor where candidates mistakenly blame instance type or volume size. A common trap is assuming that any supported OS will always replicate cleanly, but the key is that MGN requires a clean shutdown to ensure the boot sector is intact. Memory tip: think “Shut down before you spin up” — a clean source shutdown ensures a bootable target.

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

✓

The source volume was not shut down cleanly before replication.

If the source volume is not shut down cleanly before replication, the replicated volume may be in an inconsistent state, leading to a missing boot sector. AWS Application Migration Service requires consistent volumes to ensure successful boot. Option A is incorrect because the EBS volume size does not affect the boot sector; a smaller volume would likely cause a different error. Option C is incorrect because the instance type does not impact the boot sector; MGN supports various instance types. Option D is incorrect because an unsupported OS would typically result in an incompatibility error, not a missing boot sector.

Answer analysis

Option-by-option breakdown

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

  • ✗

    The EBS volume size is smaller than the source volume.

    Why it's wrong here

    MGN preserves volume size.

  • ✓

    The source volume was not shut down cleanly before replication.

    Why this is correct

    Dirty shutdown can corrupt boot sector.

  • ✗

    The source web server uses an unsupported instance type.

    Why it's wrong here

    Instance type doesn't affect boot sector.

  • ✗

    The source OS is not supported by MGN.

    Why it's wrong here

    MGN supports many OSes.

About these practice questions

Courseiva writes every SAP-C02 question from scratch — 1,660 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on SAP-C02

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. 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?

easy
  • ✓ A.Launch test instances from MGN, diagnose the issues, then update the source servers and perform a final cutover.
  • B.Rerun the MGN replication and perform a new cutover.
  • C.Restore the servers from the latest AMI and re-run the health check.
  • D.Use AWS CloudEndure Migration to re-migrate the servers.

Why A: 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.

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.