-
Hi Karl,
Thanks for bringing this up. Your interpretation is entirely understandable. The wording in Option 6 focuses on “tracking the status of application migration,” which suggests it occurs only after migration has started. That makes it easy to see why it feels out of place in a question specifically asking about planning.
However, according to AWS documentation, Migration Hub is also a planning tool, not just a tracking tool. AWS states that Migration Hub provides visibility into application inventories, server data, and dependencies discovered through AWS Application Discovery Service. All of this information is used during the planning stage to understand the current environment, group servers into migration waves, map dependencies, and estimate migration effort and cost.
In the scenario given, the company has thousands of servers, outdated documentation, and workloads spread across environments. Centralizing all discovery data in Migration Hub is a crucial step in building an accurate migration plan. That’s why it’s included in the correct set of answers, even though the phrasing emphasizes tracking rather than its planning capabilities.
Your feedback is valid, and we’ll revisit the question wording to make the Migration Hub’s planning role more straightforward and avoid confusion.
Regards,
Nikee @ Tutorials Dojo
