A multinational retail corporation is planning to migrate its hybrid e-commerce and invent… — AWS Certified Solutions Architect - Professional

A multinational retail corporation is planning to migrate its hybrid e-commerce and inventory management platform to AWS. The on-premises infrastructure is distributed as follows:

* $300$ virtual machines (VMs) hosted on a VMware vSphere cluster. The Solutions Architect must perform detailed network dependency mapping (including active inbound and outbound TCP connections and process-level details) to design AWS Security Groups and identify migration waves.
* $50$ bare-metal physical servers running Red Hat Enterprise Linux (RHEL) that host the core database tier. The corporate security and compliance policy strictly prohibits the installation of any third-party software agents on these database systems.
* $10$ legacy bare-metal physical servers running IBM AIX that run proprietary inventory lookup services.

The migration must be tracked centrally in AWS Migration Hub. The business requires the integration of both AWS migration tools and custom third-party migration tracking systems to monitor the migration status of all servers.

Which of the following actions should the Solutions Architect take to meet these requirements? (Select TWO.)

Install the AWS Application Discovery Agent on the $300$ VMware VMs to capture network connections and running processes, and manually import the metadata and dependency information for the $50$ RHEL and $10$ AIX bare-metal servers using the Application Discovery Service import CSV template.Answer
Group the discovered and imported servers into logical applications within the AWS Migration Hub console, and configure the third-party migration tools to update the migration status of these applications using the AWS Migration Hub Home Region API.Answer
C
Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server to gather the required network connection maps and process lists, and install the AWS Application Discovery Agent on all RHEL and AIX physical servers to stream their inventory data.
D
Deploy the AWS Application Discovery Agent on all VMware, RHEL, and AIX servers, ensuring that port $1500$ is opened on the on-premises firewalls to allow the agents to stream the dependency data directly to the AWS Migration Hub endpoint.
E
Manually import all server configurations via a CSV file, and use AWS Resource Access Manager (RAM) to share the AWS Migration Hub discovery data with target member accounts to allow localized tracking of migration waves.
F
Deploy the AWS Application Discovery Agentless Collector to discover the VMware VMs. For the physical servers, configure a pilot light disaster recovery replication to AWS using AWS Application Migration Service (MGN), which will automatically populate the Migration Hub with system and network dependencies.

Answer

The correct answer is to install the AWS Application Discovery Agent on the VMware VMs, manually import metadata for the RHEL and AIX physical servers using the import CSV template, group the servers into applications in the AWS Migration Hub console, and use the Migration Hub Home Region API to integrate the third-party migration tools.

To satisfy the requirement of gathering detailed network dependencies (active TCP connections) and process details for the VMware VMs, the Solutions Architect must install the AWS Application Discovery Agent on those VMs, as the Agentless Collector does not support gathering network connection mapping. Because the RHEL bare-metal database servers cannot host agents due to security policies, and the AIX bare-metal servers do not support the agent, the metadata for these physical servers must be manually collected and uploaded using the AWS Application Discovery Service CSV import template. To aggregate tracking for both AWS and third-party tools, the servers must be grouped into applications in AWS Migration Hub, and third-party tracking tools can write status updates to the centralized Migration Hub using the Migration Hub Home Region API.

Step-by-Step Solution

Determine the discovery mechanism for the VMware VMs.

The VMware VMs require detailed network dependency mapping and process-level info, which cannot be captured by the Agentless Collector. Therefore, the AWS Application Discovery Agent must be installed on these VMs.

The Agentless Collector only collects VM configurations, disk I/O, and CPU/RAM utilization. Detailed network connection mappings (source/destination IP and port) require the OS-installed Agent.

Determine the discovery mechanism for the physical RHEL and AIX servers.

Since RHEL physical servers cannot have agents due to policy, AIX is unsupported by the agent, and both are bare-metal (preventing VMware-level agentless collection), their configuration data must be manually gathered and imported using the Application Discovery Service import CSV template.

Manual CSV import allows registering inventory metadata with AWS Application Discovery Service when automated agents or collectors are constrained by policies or platform compatibility.

Determine how to centralize and integrate third-party tracking in AWS Migration Hub.

Group the discovered and imported servers into logical applications in Migration Hub, and configure the third-party migration tools to publish status updates using the Migration Hub Home Region API.

Migration Hub enables tracking at the application level. Third-party tools and custom scripts write updates directly to the AWS Migration Hub Home Region endpoint to populate the central dashboard.

Key Concept

AWS Application Discovery Service supports both agent-based (Agent) and agentless (Collector) discovery modes, alongside manual CSV uploads. Choosing the right mode depends on hypervisor availability, OS compatibility, security policies, and the required depth of network dependency mapping.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic