Examkin

Question

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

A national energy grid operator is planning to migrate its hybrid workload portfolio to AWS. The portfolio includes:

* 300 VMware vSphere VMs running enterprise Linux and Windows Server OS.
* 10 physical bare-metal servers running CentOS 7 that handle sensitive telemetry data. These servers are located in a secure network zone with no direct outbound internet access, but they can route traffic through an on-premises HTTP proxy.
* 8 legacy physical servers running IBM AIX that run critical database backends.

The operator requires a discovery solution that maps network dependencies to group servers into applications, gathers CPU and memory utilization data for right-sizing, and tracks the migration status in a centralized dashboard using AWS Migration Hub. Due to strict security policies, the virtualization team refuses to install any agents on the hypervisors or inside the VMware VMs, but they allow read-only vCenter read access.

Which combination of discovery mechanisms and configuration steps will meet these requirements while mapping dependencies and tracking the migration? (Select TWO.)

  1. Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware environment to discover VM configurations and resource utilization, and manually populate the AWS Migration Hub import template CSV file to record the IBM AIX servers' configurations and dependencies.Answer
  2. Install the AWS Application Discovery Agent on the 10 CentOS physical servers, and configure the agents to route traffic through the HTTP proxy by setting the HTTPS_PROXY environment variable during installation.Answer
  3. C
    Install the AWS Application Discovery Agent on the VMware VMs, and configure the AWS Application Discovery Agentless Collector to discover the IBM AIX and CentOS physical servers.
  4. D
    Deploy the AWS Application Discovery Agentless Collector, and configure it to perform network dependency scanning across both the VMware VMs and the CentOS physical servers.
  5. E
    Use AWS Application Migration Service (MGN) replication agents to automatically discover the OS configurations of the VMware VMs and IBM AIX servers, and sync the metadata directly to AWS Migration Hub.

Answer

Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware environment to discover VM configurations and resource utilization, and manually populate the AWS Migration Hub import template CSV file to record the IBM AIX servers' configurations and dependencies. Install the AWS Application Discovery Agent on the 10 CentOS physical servers, and configure the agents to route traffic through the HTTP proxy by setting the HTTPS_PROXY environment variable during installation.
The correct combination requires using the Agentless Collector for VMware VMs to respect the no-agent policy, while using the Agent-based discovery on the CentOS physical servers to map network dependencies (using the HTTP proxy settings). For unsupported architectures like physical IBM AIX, manual inventory collection and CSV import into AWS Migration Hub is the appropriate mechanism.

Step-by-Step Solution

1
Evaluate the discovery mechanism for the VMware vSphere VMs.
Since the virtualization team forbids installing agents inside the VMs or on the hypervisors, the AWS Application Discovery Agentless Collector is selected. It deploys as an OVA in vCenter and collects metadata and performance history without agents.
Meets the constraint of not installing agents while gathering VM configurations and performance history.
2
Determine the discovery mechanism for the physical CentOS telemetry servers.
The AWS Application Discovery Agent is installed on the physical CentOS servers. Since they are in a secure network zone with HTTP proxy egress, the HTTPS_PROXY environment variable is configured to allow the agent to register and send discovery data to AWS.
Allows process-level network dependency tracking and performance data collection for compatible Linux systems behind a proxy.
3
Address the legacy physical IBM AIX servers.
Because IBM AIX is not supported by either the Application Discovery Agent or the Agentless Collector, and they are physical systems, their configuration and network dependency data must be collected manually and uploaded via the AWS Migration Hub CSV import template.
Ensures unsupported operating systems are included in the overall migration plan and application grouping in Migration Hub.

Key Concept

Selecting and configuring AWS Application Discovery Service agents, collectors, and import options based on OS support, virtualization type, proxy network constraints, and security policies.
Rate this question

Topics

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

More questions from this topic