Examkin

Question

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

An energy utility company plans to migrate its legacy billing and operations platform to AWS. The on-premises environment is hosted on Microsoft Hyper-V. Due to strict energy sector compliance regulations, the security team prohibits installing any third-party software agents on the database virtual machines (VMs) containing customer billing data. However, the migration team requires deep network dependency mapping and process-level details for the web and application tier VMs to identify system boundaries and map network connections. Additionally, the company wants to track the overall migration status from a single dashboard using both AWS Application Discovery Service and third-party migration tools. Which combination of discovery mechanisms and tracking setup will meet these requirements while complying with the security policy?

  1. Deploy the AWS Application Discovery Agentless Collector on the Hyper-V hosts to gather configuration and performance data for the database virtual machines. Install the AWS Application Discovery Agent on the web and application virtual machines to collect network connections and process details. Register both the AWS discovery tools and the third-party migration tools with AWS Migration Hub in a single home Region to track the migration.Answer
  2. B
    Install the AWS Application Discovery Agent on all virtual machines, configuring the agents on the database virtual machines to run in read-only mode to satisfy the security policy. Use AWS Application Migration Service (MGN) to import the server inventory and track the migration status of both AWS and third-party tools from the replication console.
  3. C
    Deploy the AWS Application Discovery Agentless Collector on the Hyper-V hosts for all virtual machines, as the collector can perform guest OS process-level analysis and map TCP/UDP network connections without agent installation. Set up Service Control Policies (SCPs) in AWS Organizations to restrict AWS Migration Hub tracking access to compliance administrators.
  4. D
    Use AWS DataSync to scan the Hyper-V datastores to identify VM configurations and map network dependencies. Deploy the AWS Application Discovery Agentless Collector to monitor performance, and configure AWS Migration Hub in multiple target Regions to track the migration process for each application tier.

Answer

Deploy the AWS Application Discovery Agentless Collector on the Hyper-V hosts to gather configuration and performance data for the database virtual machines. Install the AWS Application Discovery Agent on the web and application virtual machines to collect network connections and process details. Register both the AWS discovery tools and the third-party migration tools with AWS Migration Hub in a single home Region to track the migration.
The correct answer correctly satisfies both constraints: the database VMs use the Agentless Collector at the Hyper-V host level, preventing guest OS modification, while the web and application VMs use the Agent-based collector to gather the process and network dependency mappings. In addition, it properly designates AWS Migration Hub in a single home Region to aggregate tracking details from both AWS and partner/third-party migration tools.

Step-by-Step Solution

1
Analyze on-premises VM types and constraints.
The database VMs cannot have agents installed, meaning agentless discovery must be used. Web and application tier VMs require network dependency mapping and process-level details, meaning agent-based discovery must be used.
Choosing the correct discovery tool is governed by the OS-level access constraints and the depth of telemetry required.
2
Select the appropriate AWS Application Discovery tools.
Deploy the AWS Application Discovery Agentless Collector on Hyper-V for the databases, and install the AWS Application Discovery Agent on the web and application VMs.
Agentless Collector gathers VM metadata and performance specs at the hypervisor layer without OS agents, whereas the Agent gathers process and dependency maps from inside the guest OS.
3
Determine tracking dashboard configuration.
Configure AWS Migration Hub in a single home Region and register the discovery results along with any supported third-party migration tools.
AWS Migration Hub integrates both AWS and partner migration tools to track migration progress from a centralized dashboard in a designated home Region.

Key Concept

AWS Application Discovery Service Agent vs. Agentless Collector trade-offs and AWS Migration Hub tracking integration.
Estimated Time:2m 0s
Rate this question

Topics

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

More questions from this topic