Examkin

Question

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

A retail company is planning to migrate its supply chain platform to AWS. The on-premises infrastructure consists of 400 virtual machines running on VMware vCenter, and 30 physical bare-metal database servers. The company's security policy strictly prohibits the installation of any software agents on the production application servers running on the virtual machines. Additionally, the physical database servers run a mix of legacy Red Hat Enterprise Linux (RHEL) 5 (which is not supported by the AWS Application Discovery Agent) and Windows Server 2019 (which is supported). The database subnet has no direct outbound internet access, but traffic can be routed through an internal HTTPS proxy. The company wants to perform system discovery and track the migration progress in AWS Migration Hub. Which of the following actions should the Solutions Architect recommend? (Select TWO.)

  1. Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware vCenter environment to discover the application tier virtual machines without installing agents.Answer
  2. Import the inventory details for the unsupported RHEL 5 physical database servers using a CSV template in AWS Migration Hub, and install the AWS Application Discovery Agent on the supported physical Windows servers configured with an HTTPS proxy for outbound communications.Answer
  3. C
    Install the AWS Application Discovery Agent on all VMware virtual machines to capture detailed database schemas, and use an AWS Direct Connect connection to route discovery traffic directly to AWS Migration Hub.
  4. D
    Deploy the AWS Application Discovery Agentless Collector on a physical gateway server in the database subnet, configuring it to scan the bare-metal database servers via WMI and SSH to bypass local firewall restrictions.
  5. E
    Utilize AWS Database Migration Service (DMS) schema assessment tools to discover host-level network dependencies, and configure AWS Migration Hub to automatically query the on-premises vCenter server directly over the internet.

Answer

Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware vCenter environment, and import the inventory details for the unsupported RHEL 5 physical database servers using a CSV template while installing the Application Discovery Agent on the supported physical Windows servers configured with an HTTPS proxy.
Deploying the Agentless Collector as a virtual appliance in the VMware environment fulfills the requirement to discover the virtual machine fleet without violating the policy against agent installations. For the physical servers, using a CSV import handles the legacy RHEL 5 servers which lack agent support, while the supported Windows servers can run the Application Discovery Agent configured to route its traffic through the internal HTTPS proxy.

Step-by-Step Solution

1
Evaluate the discovery mechanism for the VMware virtual machines.
Identify that the AWS Application Discovery Agentless Collector is required to satisfy the security policy against installing agents on the virtual machines.
The Agentless Collector gathers VM metadata, configuration, and performance info directly from vCenter Server without requiring in-guest agent software.
2
Address the discovery requirements for the physical database servers.
Divide the physical database discovery into manual CSV import for unsupported RHEL 5 servers and agent-based discovery for Windows Server 2019 servers using an HTTPS proxy.
The Application Discovery Agent does not support legacy RHEL 5, necessitating a CSV upload for those hosts. Windows Server 2019 is supported, and the agent can communicate outbound via an HTTPS proxy to bypass the subnet's direct internet restriction.
3
Consolidate the discovery outputs into the central tracking system.
Track the collected virtual and physical inventory data directly within the AWS Migration Hub dashboard.
AWS Migration Hub integrates both the Agentless Collector data, the agent-collected data, and manually imported server inventories for unified tracking.

Key Concept

Selecting the correct discovery mechanism (Agent vs. Agentless) and import options in AWS Application Discovery Service and tracking migration progress in AWS Migration Hub.
Rate this question

Topics

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

More questions from this topic