Examkin

Question

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

A global shipping and logistics enterprise is preparing to migrate its supply chain management platform to AWS. The on-premises environment consists of a mix of VMware vSphere virtual machines and physical bare-metal servers running Red Hat Enterprise Linux and Windows Server. The enterprise security policy prohibits any direct outbound internet access from the on-premises datacenter. All outbound traffic must go through an on-premises HTTP proxy that performs SSL decryption and inspection. To plan the migration, the solutions architect must collect detailed CPU and memory utilization, active running processes, and network dependencies (source/destination IPs and ports) for all servers. The migration tracking dashboard must consolidate status updates from both AWS migration services and integrated third-party migration tools. Which strategy should the solutions architect implement to perform the discovery and track the migration?

  1. Deploy the AWS Application Discovery Agent on all physical servers and virtual machines. Configure the agents to communicate through the on-premises HTTP proxy, and register the agents with AWS Application Discovery Service. Enable data collection, and use the AWS Migration Hub console to track the status of both AWS migration tools and integrated third-party migration tools.Answer
  2. B
    Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware vCenter environment. Configure the collector to route traffic through the on-premises HTTP proxy to gather hardware specifications, CPU/memory utilization, process lists, and network connection details for all servers, then track the migration status in AWS Migration Hub.
  3. C
    Deploy the AWS Application Migration Service (MGN) replication agent on all servers to perform initial discovery and map network dependencies. Configure the agents to route traffic through the HTTP proxy over TCP port 1500 to send performance and dependency data to the AWS Migration Hub dashboard, and integrate third-party tools using the MGN API.
  4. D
    Import the server inventory details into AWS Migration Hub using a CSV import template. Deploy the AWS Systems Manager (SSM) Agent on all servers to collect running processes and network dependencies, and configure SSM Inventory to stream this data through the on-premises HTTP proxy directly to the AWS Migration Hub dashboard.

Answer

Deploy the AWS Application Discovery Agent on all physical servers and virtual machines, configure the agents to use the HTTP proxy, enable data collection under AWS Application Discovery Service, and track the migration status of both AWS and third-party tools in AWS Migration Hub.
The correct strategy involves deploying the AWS Application Discovery Agent on all physical and virtual servers. This agent runs inside the operating system, allowing it to collect system performance metrics, active processes, and network dependencies (source/destination IPs and ports) regardless of the hypervisor. It also natively supports routing its outbound HTTPS communication through an on-premises HTTP/HTTPS proxy. Finally, AWS Migration Hub acts as a single pane of glass to track the migration progress of both AWS tools and integrated third-party migration tools.

Step-by-Step Solution

1
Analyze environment and collection requirements.
The target environment contains physical bare-metal servers, and the architect must collect OS-level network dependencies and active running processes.
Since the environment has physical servers and requires OS-level process and network connection mapping, the AWS Application Discovery Agentless Collector cannot be used (as it is VMware-only and doesn't collect process or network dependencies). The Application Discovery Agent (agent-based) is required.
2
Configure egress connectivity for the agents.
Install the AWS Application Discovery Agent on each host and configure it with the proxy settings (e.g., HTTP_PROXY/HTTPS_PROXY) to communicate with AWS endpoints through the local proxy.
The local datacenter prohibits direct outbound internet access and mandates HTTP proxy routing with SSL inspection. The agents support proxy configuration to securely transmit metadata to AWS.
3
Consolidate and track migration progress in AWS Migration Hub.
Integrate third-party migration tools with the AWS Migration Hub API and use the unified dashboard to monitor migration state.
AWS Migration Hub is designed to act as a central portfolio and migration tracking dashboard, aggregating data from discovery agents and supporting tracking for both native AWS migration tools and registered third-party software.

Key Concept

AWS Application Discovery Agent vs. Agentless Collector Trade-offs and Migration Hub Tracking Integration
Rate this question

Topics

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

More questions from this topic