Examkin

Question

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

A medical device manufacturing company is planning to migrate its core supply chain and regulatory compliance systems to AWS. The on-premises environment consists of two distinct segments:

1. A cluster of VMware vSphere 7.0 virtual machines (VMs) running supported Enterprise Linux operating systems inside a secure network zone. These VMs have no direct internet access but can communicate outbound through an authenticated HTTP/HTTPS proxy. The company's compliance policy strictly prohibits installing any software at the hypervisor level (ESXi hosts), but permits guest-level agent installations.
2. Several physical bare-metal servers running a highly customized legacy Linux kernel that does not support the installation of the AWS Application Discovery Agent.

The migration team must discover the server configurations, monitor CPU and memory utilization for right-sizing, map network dependencies (specifically active TCP connections between servers), and track the overall migration status in AWS Migration Hub. The team also wants to integrate this tracking with their existing Jira Service Management platform for change management.

Which two actions should a solutions architect recommend to satisfy these discovery and tracking requirements? (Select two.)

  1. Install the AWS Application Discovery Agent on the VMware VMs, configure the agents to use the authenticated HTTP/HTTPS proxy for outbound communication, and enable the Jira Service Management integration in AWS Migration Hub.Answer
  2. Manually record the hardware configuration and network connections of the bare-metal servers, format the data into the standard Application Discovery Service CSV import templates, and upload them to the Migration Hub console.Answer
  3. C
    Deploy the AWS Application Discovery Agentless Collector in the VMware environment, configure it to run network dependency scanning on the VMs via vCenter APIs, and use a custom script to run the Agentless Collector in loopback mode on the bare-metal servers.
  4. D
    Install the AWS Application Discovery Agent directly on the VMware ESXi hosts to capture network packet flows from all VMs without VM-level installation, and import the bare-metal server data using AWS Application Migration Service (AWS MGN) replication templates.
  5. E
    Configure AWS Application Discovery Agentless Collector to query the VMware VMs using guest OS credentials, and deploy a third-party discovery agent on the bare-metal servers that syncs directly to AWS Systems Manager Inventory to bypass Migration Hub.

Answer

Install the AWS Application Discovery Agent on the VMware VMs while routing outbound data through the proxy, integrate Migration Hub with Jira Service Management, and manually import the bare-metal server configurations and network dependencies using the CSV import templates.
The correct options state that we must install the guest-level AWS Application Discovery Agent on the VMware VMs (configuring it to use the proxy) and manually import the configuration and dependency data of the bare-metal servers using CSV templates. The Discovery Agent is required because the Agentless Collector does not collect the requested network connection details. Since the bare-metal legacy Linux servers cannot run agents and are not virtualized on VMware, their data must be uploaded manually via CSV. Additionally, AWS Migration Hub natively integrates with Jira Service Management to centralize and track ticketed migration workflows.

Step-by-Step Solution

1
Determine the discovery mechanism for the VMware VMs based on the network dependency mapping requirement.
Since network connection mapping (TCP dependencies) is required, the Agentless Collector cannot be used. The AWS Application Discovery Agent must be installed on the VMs.
Agentless Collector only gathers VM specifications and utilization metrics at the vCenter level, lacking the capability to map process-to-process or network connections.
2
Configure the Application Discovery Agents to comply with the secure zone's network constraints.
Configure the agent's proxy settings using the authenticated HTTP/HTTPS proxy configuration options.
The agents require outbound connectivity to AWS endpoints to upload collected data, which must route through the proxy in a no-direct-internet zone.
3
Evaluate the discovery options for the physical bare-metal legacy Linux servers.
Since the legacy Linux kernel prevents agent installation and they are physical servers (excluding VMware Agentless collection), use the Application Discovery Service CSV import templates.
Importing via CSV is the standard mechanism to manually inject server configuration, performance, and dependency data for unsupported or untracked legacy infrastructure.
4
Configure the centralized tracking integration in AWS Migration Hub.
Link AWS Migration Hub with Jira Service Management using the integrated connector.
This satisfies the requirement to track the overall migration progress and coordinate change management tickets within the existing Jira platform.

Key Concept

Selecting and configuring the correct AWS Application Discovery Service tool (Agent-based vs. Agentless vs. CSV Import) based on OS compatibility, virtualization type, network topology, and the requirement to map network dependencies.
Rate this question

Topics

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

More questions from this topic