AWS Certified Solutions Architect Professional SAP-C02 Practice Question

The correct approach is to deploy the AWS Application Discovery Agent on all in-scope servers. The agent-based approach is necessary to meet all the stated requirements. The AWS Application Discovery Agent can be installed on both virtual machines and physical servers. A key feature of the agent is its ability to collect detailed data, including running processes and inbound/outbound network connections, which is essential for mapping application dependencies. This data is sent to AWS Migration Hub, where it can be analyzed to group servers into applications and plan migration waves, directly addressing the core requirement of the scenario.

Using the AWS Agentless Discovery Connector is incorrect because, while it can discover VMware VMs, it does not support physical servers. More importantly, the agentless method does not collect the detailed network connection and process-level data required for deep dependency mapping.

Using AWS Application Migration Service (MGN) for discovery is incorrect. MGN is a service for executing the migration (a 'lift-and-shift' tool), not for discovery and planning. While a test cutover might expose some broken dependencies, it is a reactive and inefficient method for comprehensive discovery.

Manually uploading data from a CMDB is incorrect because it is labor-intensive, prone to errors, and unlikely to contain the dynamic, real-time network dependency information needed. The scenario highlights a poorly documented environment, making reliance on existing documentation and interviews insufficient and risky.