Examkin

Question

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

A healthcare provider is planning to migrate its legacy patient portal and billing system from an on-premises VMware vCenter environment to AWS. The security compliance policy strictly prohibits the installation of any software agents on the virtual machines (VMs) hosting the billing system due to regulatory constraints. However, the legacy patient portal runs on physical bare-metal Linux servers where network dependency mapping is required to identify all upstream and downstream database connections. The architect wants to centralize the discovery and track the migration status in a single dashboard.

Which of the following approaches should the Solutions Architect implement? (Select TWO.)

  1. Deploy the AWS Application Discovery Agentless Collector as an Open Virtualization Archive (OVA) template on VMware vCenter to discover the billing system VMs.Answer
  2. Install the AWS Application Discovery Agent on the physical Linux servers hosting the patient portal to collect network dependencies.Answer
  3. C
    Install the AWS Application Discovery Agent on the billing system VMs to capture detailed disk configuration and OS process details.
  4. D
    Deploy the AWS Application Discovery Agentless Collector on the physical Linux servers to perform agentless discovery of the patient portal database dependencies.

Answer

Deploy the AWS Application Discovery Agentless Collector as an OVA template on VMware vCenter to discover the billing system VMs, and install the AWS Application Discovery Agent on the physical Linux servers hosting the patient portal.
The correct approach is to deploy the AWS Application Discovery Agentless Collector as an OVA template on VMware vCenter, and install the AWS Application Discovery Agent on the physical Linux servers. The Agentless Collector runs at the vCenter hypervisor level, which retrieves configuration and utilization data for the billing VMs without installing any software on the guest operating systems, thereby complying with security rules. The Application Discovery Agent is required on the physical servers because they are bare-metal systems, and only the agent can capture the necessary network dependency mappings for the patient portal.

Step-by-Step Solution

1
Analyze the discovery requirements and constraints for the billing system VMs.
The security policy forbids agent installation on the billing VMs, and they run on VMware vCenter. Therefore, the VMware-compatible AWS Application Discovery Agentless Collector must be used.
The Agentless Collector gathers configuration and performance metrics at the hypervisor level without requiring guest operating system access or agent installation.
2
Analyze the discovery requirements for the patient portal on physical servers.
The portal runs on physical bare-metal servers (not VMware) and requires network dependency mapping. Therefore, the agentless collector cannot be used, and the AWS Application Discovery Agent must be installed on these servers.
The Application Discovery Agent is required for physical servers and is the only mechanism that can capture TCP/UDP port connections and network dependencies.
3
Select the correct combination of options.
The solution requires deploying the Agentless Collector as an OVA on vCenter and installing the Agent on the physical Linux servers.
This dual approach respects both the VM security policies and the requirement to map network dependencies on the physical servers.

Key Concept

Selecting the appropriate AWS Application Discovery Service tool (Agent-based vs. Agentless Collector) based on physical vs. virtual infrastructure and compliance constraints.
Rate this question

Topics

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

More questions from this topic