
Ultimate access to all questions.
A company is migrating several applications to AWS but lacks a comprehensive understanding of its application estate, which includes both physical machines and VMs. One specific application has numerous latency-sensitive dependencies using a custom IP-based protocol on port 1000. The company aims to migrate these dependencies simultaneously with the application. They have been using the AWS Application Discovery Agent for data collection. How should the company identify and group these dependencies for a coordinated migration?
A
Utilize AWS Migration Hub to select the application's hosting servers, visualize the network graph to identify interacting servers, enable data exploration in Amazon Athena, and query server communications on port 1000. Based on Athena's findings, create a migration group in Migration Hub.
B
Employ AWS Application Migration Service to select the application's hosting servers, visualize the network graph to identify interacting servers, configure test instances for these servers, conduct acceptance tests, and form a migration group from the successfully tested servers.
C
Leverage AWS Migration Hub to select the application's hosting servers, activate data exploration in Network Access Analyzer, select servers with a Network Access Scope of port 1000, and create a migration group in Migration Hub based on Network Access Analyzer's findings.
D
Use AWS Migration Hub to select the application's hosting servers, deploy Amazon CloudWatch agents via the AWS Application Discovery Agent, export CloudWatch logs to Amazon S3, query these logs in Amazon Athena for servers on port 1000, and create a migration group in Migration Hub based on Athena's queries.