Examkin

Question

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

An aerospace defense company is migrating its multi-tier application portfolio to AWS and must centralize tracking in AWS Migration Hub. The current on-premises environment consists of:

* 200 standard VMware vSphere virtual machines (VMs) running supported Windows and Linux distributions where network dependency mapping is required to group servers into applications.
* 50 highly secured VMware vSphere VMs containing export-controlled data. Regulatory compliance strictly forbids installing third-party agent software or modifying guest configurations, though hypervisor-level monitoring is permitted.
* 50 legacy physical servers running custom Linux distributions with kernels older than version 2.6.18, which cannot be virtualized or upgraded prior to migration.

The migration will be executed using a combination of AWS Application Migration Service (MGN) and a supported partner-developed migration tool.

Which of the following actions must the Solutions Architect take to perform discovery and track migration progress? (Select TWO.)

  1. For discovery, deploy the AWS Application Discovery Agent on the 200 standard VMware VMs to collect network dependencies; deploy the AWS Application Discovery Agentless Collector in the VMware environment to discover the 50 secured VMs; and import the metadata for the 50 legacy physical servers using the Application Discovery Service import CSV template.Answer
  2. For migration tracking, configure the partner-developed migration tool to call the AWS Migration Hub API to publish migration status updates, ensuring that all API payloads and discovery data target the designated Migration Hub Home Region.Answer
  3. C
    For discovery, deploy the AWS Application Discovery Agentless Collector, configure it with administrative credentials, and use guest-level SSH and WMI queries to perform process-to-process network dependency mapping across all 300 servers.
  4. D
    For discovery, install the AWS Application Discovery Agent on all 300 servers, configure a local HTTPS proxy to route compliance-sensitive data, and bypass the operating system kernel check for the 50 legacy physical servers.
  5. E
    For migration tracking, share the AWS Migration Hub discovery datastore across the AWS Organization using AWS Resource Access Manager (RAM), and configure the partner migration tool to write status JSON payloads directly to the shared Amazon S3 bucket.

Answer

To perform discovery and track migration, the Solutions Architect must deploy the AWS Application Discovery Agent on the 200 standard VMware VMs, deploy the AWS Application Discovery Agentless Collector in the VMware environment for the 50 secured VMs, and manually import metadata for the 50 legacy physical servers via a CSV template. For migration tracking, they must configure the partner-developed migration tool to call the AWS Migration Hub API while targeting the designated Migration Hub Home Region.
The correct strategy combines the AWS Application Discovery Agent on the standard VMs (which allows collecting network dependency information), the VMware-based AWS Application Discovery Agentless Collector on the secured VMs (which collects VM metadata from vCenter without installing guest software), and manual CSV import for the legacy physical servers (since their OS kernels are too old to support the agent, and they are not virtualized). For migration tracking, the partner tool must publish status updates using the Migration Hub API targeting the designated Migration Hub Home Region.

Step-by-Step Solution

1
Assess agent and agentless capabilities against server types.
The 200 standard VMs require network dependency mapping, which is only supported by the Application Discovery Agent. The 50 compliance VMs forbid agents but permit hypervisor-level data, which is supported by the VMware-based Agentless Collector. The 50 legacy physical servers cannot run the agent due to unsupported operating systems (older than kernel 2.6.18) and cannot use the Agentless Collector because they are not on vSphere.
Correct mapping of discovery tools is necessary to ensure data is collected without violating compliance boundaries or failing due to compatibility limits.
2
Determine the discovery mechanism for the unsupported legacy physical servers.
Since neither agent-based nor agentless discovery is feasible, the metadata must be imported manually using the Application Discovery Service import CSV template.
This guarantees that all 300 servers are cataloged in AWS Migration Hub for planning.
3
Configure tracking for the partner-developed migration tool.
The partner tool must be configured to call the AWS Migration Hub API to publish status updates. All API calls and discovery data must target the selected Migration Hub Home Region.
Migration Hub tracks migration progress by aggregating data published via its API from supported tools in the selected Home Region.

Key Concept

Selecting appropriate discovery mechanisms (Agent, Agentless, CSV import) based on OS compatibility and compliance requirements, and integrating third-party migration tools using the AWS Migration Hub API and Home Region.
Rate this question

Topics

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

More questions from this topic