Question

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

A logistics company is preparing to migrate its hybrid workload portfolio to AWS. The on-premises infrastructure consists of 250 VMware vSphere VMs, 40 physical Linux servers, and 10 legacy physical servers running IBM AIX. Outbound internet access from the application subnets is blocked, but an outbound proxy server is available in a management subnet. The company must discover server system configurations, network dependencies, and performance characteristics for migration planning. They also want to track the overall migration progress using AWS Migration Hub.

Which combination of actions will meet these requirements while minimizing administrative overhead? (Select TWO.)

  1. Install the AWS Application Discovery Agent on the VMware VMs and physical Linux servers, configuring the agents to route outbound traffic through the management subnet proxy.Answer
  2. Import the configuration and dependency data of the IBM AIX physical servers manually by uploading a formatted CSV file to the AWS Application Discovery Service.Answer
  3. C
    Deploy the AWS Application Discovery Agentless Collector on VMware vSphere, configuring it to scan the physical Linux servers and IBM AIX servers remotely via SSH.
  4. D
    Install the AWS Application Discovery Agent on the IBM AIX physical servers, configuring the local daemon to communicate with the Application Discovery Service via the proxy.
  5. E
    Use AWS Resource Access Manager (RAM) to share the on-premises discovery data with the AWS Migration Hub in the target migration account.

Answer

Install the AWS Application Discovery Agent on the VMware VMs and physical Linux servers, configuring the agents to route outbound traffic through the management subnet proxy, and import the configuration and dependency data of the IBM AIX physical servers manually by uploading a formatted CSV file to the AWS Application Discovery Service.
The correct actions involve installing the AWS Application Discovery Agent on the supported environments (VMware VMs and physical Linux servers) to capture both system configuration and network dependency mappings, while using the management proxy. For the unsupported IBM AIX operating system, the configuration and dependency details must be imported manually using the Application Discovery Service CSV template.

Step-by-Step Solution

1
Determine the discovery mechanism for the VMware VMs and physical Linux servers where network dependencies must be mapped.
Identify that the AWS Application Discovery Agent is required because the Agentless Collector does not capture network connection mappings (dependencies). Configure these agents to route traffic through the allowed management subnet proxy.
Agents must be deployed to capture network dependencies, and security policies require using the outbound HTTPS proxy.
2
Determine the discovery mechanism for the IBM AIX servers.
Identify that IBM AIX is not supported by either the Discovery Agent or the Agentless Collector. Prepare a CSV file using the AWS Application Discovery Service import template containing the configuration and dependency data for the AIX servers, and upload it.
Manual CSV import is the only method to feed configuration and dependency data for unsupported operating systems into the discovery service.
3
Group the discovered servers into applications within AWS Migration Hub.
Track the overall migration progress of the defined applications using Migration Hub's dashboard.
Allows centralized tracking and grouping of discovered systems for planning migration waves.

Key Concept

AWS Application Discovery Service supports agent-based collection (which captures system dependencies and supports proxy configuration) and manual CSV import for unsupported operating systems like IBM AIX.
Rate this question