A retail group must migrate 240 VMware, Hyper-V, and bare-metal store and e-commerce applications in seven waves over ten months. Leaders need agentless data collection, visualized service dependencies, cost estimates, and a sequenced wave plan with minimal store disruption. Which discovery and portfolio assessment solution maps dependencies and plans migration waves?
Select an answer to reveal the explanation.
Short Explanation
Planning waves without a map is like rearranging a busy kitchen blindfolded during dinner rush. You'll love how agentless-discovery draws your dependency map and cost story before you move a single server.
Full Explanation
AWS Transform is correct because it is the current AWS-recommended path for migration assessment: AWS Application Discovery Service and AWS Migration Hub are closed to new customers and point to AWS Transform. Its discovery tool or agentless collector gathers VMware inventory and utilization without installing agents, and inventory imports (such as RVTools exports or partner tool data) cover other server types, which suits a mixed VMware, Hyper-V, and bare-metal estate. The service maps network dependencies to group servers into applications, produces right-sized EC2 recommendations and a TCO business case, and sequences applications into waves that migration leads can review and adjust. Using AWS Config with Inspector fails by concept because Config records AWS resource configuration and Inspector finds vulnerabilities, neither performing on-premises inventory nor dependency mapping needed for wave design. Using Control Tower with CloudTrail Lake fails by concept because they govern accounts and audit API activity, not discover on-premises servers, performance, or service-to-service dependencies. Using DataSync discovery fails by concept because its assessment targets storage and transfer performance for file movement, not application portfolio dependencies, cost modeling, or multi-wave planning. For the exam, dependency plus waves points to a discovery and assessment service, and in practice validate discovery window length, open required collection ports, and freeze wave membership after dependency sign-off.