Examkin

Question

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

A regional media broadcasting corporation is planning to migrate its on-premises broadcasting and media asset management (MAM) system to AWS. The environment consists of 120 VMware vSphere VMs hosting web servers, transcoding engines, and database systems. Strict corporate security policies prohibit the installation of any software agents on the database virtual machines. Additionally, there are 15 physical bare-metal media servers running an unsupported legacy Unix-like operating system. The on-premises network restricts direct outbound internet access, but a centralized proxy server is available for outbound HTTPS traffic. The corporation wants to perform a discovery phase to determine dependencies, estimate AWS sizing, and track the migration progress in AWS Migration Hub using both AWS and integrated third-party migration tools.

Which two actions should the Solutions Architect recommend to perform the discovery and track the migration progress in AWS Migration Hub? (Select TWO.)

  1. Deploy the AWS Agentless Collector in the VMware environment, configure it to route outbound traffic through the centralized HTTPS proxy server to perform discovery for the virtualized workloads, and manually import the metadata for the physical legacy servers using the AWS Application Discovery Service CSV template.Answer
  2. B
    Install the AWS Application Discovery Agent on all VMware VMs and bare-metal servers, and configure the on-premises firewall to allow direct outbound connections to the AWS Application Discovery Service endpoint over TCP port 1500.
  3. Register the third-party migration tools with AWS Migration Hub to automatically track the migration progress of the virtualized workloads, and use the AWS Migration Hub API or CLI to publish migration status updates for the manually migrated physical legacy servers.Answer
  4. D
    Perform a replatforming migration of the legacy Unix-like bare-metal servers by running the AWS Application Discovery Agent on them to capture the OS disk volume and automatically convert it into an Amazon Machine Image (AMI) registered in AWS Migration Hub.
  5. E
    Set up AWS Database Migration Service (DMS) for continuous replication (CDC) of the database systems without configuring binary logging or supplemental logging on the source database systems, allowing AWS Migration Hub to dynamically detect and track the replication task progress.

Answer

Deploy the AWS Agentless Collector in the VMware environment to perform discovery for the virtualized workloads while routing traffic through the proxy, import the bare-metal servers' metadata using a CSV template, integrate third-party tools with AWS Migration Hub, and use the Migration Hub API/CLI for manual tracking.
The correct answer recommends using the AWS Agentless Collector to discover virtualized workloads, which is agentless and meets the constraint of not placing agents on the database VMs. It also supports configuration of proxy settings for outbound communications. For the physical bare-metal legacy systems running an unsupported OS, manual metadata import using the CSV template is the appropriate discovery strategy. Tracking is achieved by integrating third-party tools directly with AWS Migration Hub for automatically tracked workloads, and using the Migration Hub API/CLI for manual migrations.

Step-by-Step Solution

1
Determine the appropriate discovery mechanism based on server types, operating systems, and agent constraints.
Since database VMs cannot have agents and physical bare-metal servers run an unsupported OS, agent-based discovery is ruled out. Deploying the AWS Agentless Collector as a virtual appliance in VMware solves the VM discovery, and importing configuration details via a CSV template solves the legacy bare-metal server discovery.
This respects security policies prohibiting database VM agents and handles unsupported OS environments that cannot run the discovery agent.
2
Configure proxy settings for the discovery tools.
Configure the Agentless Collector to communicate with the AWS endpoint using the centralized proxy server over port 443.
The on-premises network restricts direct outbound internet access, necessitating proxy configuration.
3
Align tracking and migration tools in AWS Migration Hub.
Enable third-party migration tool integration with Migration Hub to track the VM migrations automatically, and use the Migration Hub API/CLI to manually publish status updates for the legacy bare-metal migrations.
This allows centralizing migration tracking in one dashboard across multiple migration tools and manual processes.

Key Concept

AWS Migration Discovery and Hub Integration
Rate this question

Topics

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

More questions from this topic