A company plans to migrate thousands of VMs from a VMware ESXi environment to AWS. The company lacks a configuration management database and has limited visibility into VM utilization. A solutions architect must deliver an accurate inventory for migration planning with the least operational overhead. Which approach meets this requirement?

The correct approach leverages Migration Evaluator's agentless collector, which runs on the ESXi hypervisor. This method efficiently gathers comprehensive inventory and utilization data for thousands of VMs without requiring individual agent installations, minimizing operational overhead. The collected data is then directly available in Migration Evaluator for analysis, allowing for easy identification and removal of inactive servers from the migration scope before importing the refined inventory into AWS Migration Hub for planning. Incorrect options: Patch Manager is for patching, not for deploying Migration Evaluator agents or collecting utilization data. Analyzing high-utilization servers for exclusion is generally not the primary goal; rather, it's about understanding their resource needs in AWS. Manually inspecting CSV files for thousands of VMs is time-consuming and error-prone, contradicting the "least operational overhead" requirement. AWS SMS is a legacy service largely superseded by AWS Application Migration Service (AWS MGN). Installing agents on every VM is operationally intensive, especially for thousands of VMs, and using Redshift/QuickSight for this initial discovery adds unnecessary complexity and cost compared to Migration Evaluator's built-in analysis.