Examkin

Question

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

A global pharmaceutical manufacturing company is planning to migrate its regulated drug development platform to AWS. The on-premises environment consists of 200 VMware vSphere virtual machines (VMs) running Red Hat Enterprise Linux (RHEL) and 15 physical bare-metal servers running IBM AIX that host legacy database systems. The company's security policy prohibits any inbound traffic to the on-premises environment, and all outbound traffic to the internet must route through a designated forward proxy. The migration team requires detailed process-to-process network dependency mapping for the VMware VMs to group applications correctly, and system inventory details for the AIX servers. The team also wants to consolidate all discovery data and track the migration status of all assets in AWS Migration Hub. Which combination of discovery mechanisms and configurations should a solutions architect recommend to satisfy these requirements?

  1. Deploy the AWS Application Discovery Agentless Collector on the VMware cluster to perform initial inventory discovery. Install the AWS Application Discovery Agent on the in-scope RHEL VMs, configuring the agent to use the forward proxy for outbound communications, to gather process-to-process network dependencies. For the AIX physical servers, manually populate the AWS Migration Hub import CSV template with their inventory details and upload it, then group all discovered and imported assets into applications within AWS Migration Hub to track the migration.Answer
  2. B
    Install the AWS Application Discovery Agent on all VMware RHEL VMs and the IBM AIX physical servers. Configure the agents to route discovery data through the forward proxy. Since the security policy prohibits inbound traffic, configure a temporary site-to-site VPN to allow the Application Discovery Service to poll the agents, ensuring TCP port 1500 is opened in the local firewall for data replication.
  3. C
    Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server and configure it to collect process-level network dependency mappings from the RHEL VMs. For the legacy AIX database servers, use the AWS Schema Conversion Tool (SCT) to perform a source database discovery assessment, then configure AWS Database Migration Service (DMS) with Change Data Capture (CDC) to automatically register and track the servers in AWS Migration Hub.
  4. D
    Deploy the AWS Application Discovery Agentless Collector to discover the VMware VMs. For the AIX physical servers, request an AWS Snowball Edge Storage Optimized device, run a local discovery script on the AIX servers to export inventory data to the device's S3-compatible storage, and ship the device to AWS to automate the import of configurations into the AWS Migration Hub tracking dashboard.

Answer

Deploy the AWS Application Discovery Agentless Collector on the VMware cluster for initial VMware VM discovery, install the AWS Application Discovery Agent on the in-scope RHEL VMs configured to use the outbound forward proxy for detailed network dependencies, manually upload the AIX server details using the AWS Migration Hub import CSV template, and group and track all assets within AWS Migration Hub.
The correct solution uses the agentless collector for initial vCenter discovery and the agent-based collector on Linux VMs to gather process-level network connections. The agent supports outbound-only connectivity through a proxy. For unsupported operating systems like IBM AIX on physical hardware, the manual CSV import template is the standard, supported method to register those assets. AWS Migration Hub serves as the central hub to group and track both discovered and imported assets.

Step-by-Step Solution

1
Evaluate the discovery requirements for VMware VMs.
The requirement for process-to-process network dependency mapping dictates the use of the agent-based AWS Application Discovery Agent, as the Agentless Collector only gathers host-level configuration and utilization metrics from vCenter.
Agentless discovery cannot inspect OS-level processes and their active network connections.
2
Address the operating system support and collection limits for IBM AIX physical servers.
Identify that the AWS Application Discovery Agent only supports specific Windows and Linux distributions, and does not support Unix operating systems like IBM AIX. The Agentless Collector also cannot discover physical bare-metal servers.
Alternate discovery mechanisms, such as manual CSV import or supported third-party discovery integrations, must be used for unsupported operating systems and non-virtualized physical hardware.
3
Assess the network connectivity and firewall restrictions.
Confirm that the Application Discovery Agent supports outbound communication over port 443 through a forward proxy, matching the company's security requirement of no inbound traffic.
The agents push data outbound to the Application Discovery Service endpoints using standard HTTPS connections.
4
Consolidate and track all discovered assets.
Import the AIX inventory using the CSV template and associate both the agent-discovered VMware assets and CSV-imported AIX assets into the same applications inside AWS Migration Hub.
AWS Migration Hub allows for a unified repository of discovered and imported assets to plan and track migration status across the entire application portfolio.

Key Concept

Selecting and configuring AWS Application Discovery Service agents, collectors, and import methods based on OS compatibility, network constraints, and tracking requirements in AWS Migration Hub.
Estimated Time:3m 0s
Rate this question

Topics

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

More questions from this topic