Examkin

Question

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

A logistics company is planning to migrate its on-premises infrastructure to AWS. The environment consists of 150 VMware virtual machines and 20 legacy physical servers running custom Linux distributions that cannot be virtualized. The physical servers require detailed CPU and memory utilization data at the process level to optimize AWS target sizing. However, the corporate security policy strictly forbids installing any third-party agents or making OS-level modifications on the VMware VMs. Both environments have outbound internet connectivity blocked, but they can access a VPC via an existing AWS Direct Connect connection. The migration team wants to track all migration phases, including discovery and server replication progress, from a single centralized dashboard. Which discovery and tracking strategy should the solutions architect recommend to meet these requirements?

  1. Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server, and install the AWS Application Discovery Agent on the physical servers. Configure both discovery mechanisms to communicate with the AWS Application Discovery Service using VPC endpoints. Track the discovery and migration replication status using AWS Migration Hub.Answer
  2. B
    Install the AWS Application Discovery Agent on both the VMware VMs and the legacy physical servers. Configure Systems Manager Fleet Manager to collect discovery data and proxy the data transfer over the Direct Connect connection. Use AWS Systems Manager to track the overall migration progress.
  3. C
    Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server, and use it to discover both the VMs and the legacy physical servers by configuring subnet scanning. Configure the collector to send discovery data via a public proxy over the internet. Track the migration progress using the AWS Application Migration Service console.
  4. D
    Deploy the AWS Application Discovery Agentless Collector on the VMware VMs, and install the AWS Application Discovery Agent on the legacy physical servers. Configure both to use a public proxy to forward discovery metrics. Track the discovery status using AWS Systems Manager Distributor.

Answer

Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server, and install the AWS Application Discovery Agent on the physical servers. Configure both discovery mechanisms to communicate with the AWS Application Discovery Service using VPC endpoints. Track the discovery and migration replication status using AWS Migration Hub.
The correct strategy involves deploying the Agentless Collector on VMware vCenter to respect the constraint against OS-level agent installation on virtual machines, and installing the Application Discovery Agent on the physical servers to capture process-level utilization metrics. Using VPC endpoints accommodates the outbound internet block by routing data over Direct Connect, and AWS Migration Hub provides the unified tracking dashboard.

Step-by-Step Solution

1
Determine the discovery mechanism for VMware virtual machines.
Since the security policy restricts OS-level changes on VMware VMs, the AWS Application Discovery Agentless Collector should be deployed as an OVA appliance in vCenter.
The Agentless Collector does not require any agent installation on individual virtual machines and retrieves VM configuration and performance history through the vCenter APIs.
2
Determine the discovery mechanism for the physical legacy servers.
Install the AWS Application Discovery Agent on the physical servers.
Process-level CPU and memory utilization analysis requires the Application Discovery Agent, as the Agentless Collector is only compatible with VMware vCenter and cannot fetch process-level details from physical bare-metal hardware.
3
Resolve the network connectivity constraints.
Configure both the Agentless Collector and the Discovery Agents to communicate with AWS Application Discovery Service via VPC endpoints (AWS PrivateLink).
Outbound internet access is blocked on-premises, but Direct Connect is available. Using VPC endpoints enables traffic to route privately into the AWS environment without accessing the public internet.
4
Select the unified migration tracking tool.
Use AWS Migration Hub to aggregate and track the discovery and migration replication status.
AWS Migration Hub provides a single dashboard to track the progress of discovery, grouping servers into applications, and monitoring replication from various AWS and partner migration services.

Key Concept

AWS Application Discovery Service supports both agent-based and agentless discovery models. Agent-based discovery provides detailed process-level information but requires OS installation, whereas agentless discovery collects configuration and performance metrics at the VM level via VMware vCenter. AWS Migration Hub acts as a centralized console for tracking the status of discovery and migration tools.
Estimated Time:2m 0s
Rate this question

Topics

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

More questions from this topic