Examkin

Question

Difficulty: MediumMigration Discovery, Planning, and Tracking (Application Discovery Service, Migration Hub)

A financial services firm is planning to migrate its core transactional systems to AWS. The on-premises environment consists of 150 physical bare-metal servers running supported versions of Red Hat Enterprise Linux and Windows Server, and 300 virtual machines hosted on Nutanix AHV. The compliance team requires process-level network dependency mapping for all servers to group them into applications before migration. The network security policy prohibits direct outbound internet access from individual database and application servers, but allows traffic to pass through a centralized administrative proxy server. Which strategy should a Solutions Architect recommend to discover the environment and track the migration in AWS Migration Hub?

  1. Install the AWS Application Discovery Agent on all physical and virtual servers. Configure the agents to route outbound discovery metadata through the centralized administrative proxy server. Use the collected dependency data in AWS Migration Hub to group the servers into applications.Answer
  2. B
    Deploy the AWS Application Discovery Agentless Collector in the Nutanix AHV environment and configure it to query the hypervisor APIs. For the physical servers, configure a central log collector to forward system syslog and event logs to AWS Migration Hub for dependency analysis.
  3. C
    Install the AWS Application Discovery Agent on all physical and virtual servers. Configure the local server firewalls to bypass the security policy and allow outbound HTTPS traffic directly over TCP port 443 to the public AWS Application Discovery Service endpoints.
  4. D
    Deploy AWS Database Migration Service (DMS) agents on the database servers to capture schema and dependency data. For the application servers, deploy the AWS Application Discovery Agentless Collector on a dedicated management server configured to scan the subnet ranges.

Answer

Install the AWS Application Discovery Agent on all physical and virtual servers, configure them to route discovery metadata through the centralized administrative proxy server, and use AWS Migration Hub to group the servers into applications.
The correct strategy is to deploy the AWS Application Discovery Agent on all physical and virtual servers. The agent-based approach is necessary because the environment includes physical bare-metal servers and Nutanix AHV VMs, which are not supported by the VMware-only Agentless Collector. Furthermore, the agent is required to capture the process-level network dependency mapping demanded by the compliance team. To respect the network security policy that bans direct internet access, the agents can be configured to forward metadata through the central administrative proxy server.

Step-by-Step Solution

1
Determine the appropriate discovery mechanism based on virtualization and OS requirements.
Since the environment has bare-metal servers and Nutanix AHV (non-VMware), and requires process-level network dependency mapping, the agentless collector cannot be used. The AWS Application Discovery Agent must be selected.
The Agentless Collector only supports VMware vCenter and does not gather OS process-level dependency detail, which is needed to map applications for compliance.
2
Configure the agent networking to comply with security guidelines.
Configure the AWS Application Discovery Agents to route their HTTPS outbound traffic (port 443) through the centralized administrative proxy server.
This complies with the network security policy prohibiting direct outbound internet access while still allowing metadata to reach the AWS Application Discovery Service.
3
Group the discovered servers into applications within AWS Migration Hub.
Visualize and analyze the dependency mapping in Migration Hub to organize the servers into logical application groups for migration tracking.
Grouping servers helps in planning migration waves and tracking migration status in a centralized dashboard.

Key Concept

AWS Application Discovery Service deployment choices and networking configurations
Rate this question

Topics

Migration Discovery, Planning, and Tracking (Application Discovery Service, Migration Hub)

More questions from this topic