Examkin

Question

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

An online multiplayer gaming studio is planning to migrate its hybrid game engine and account management system to AWS. The on-premises environment consists of:

* 150 virtual machines (VMs) hosted on VMware vSphere running standard CentOS and Windows Server.
* 10 bare-metal physical servers running FreeBSD for legacy matchmaking lobbies.
* 5 bare-metal physical servers running IBM AIX for legacy transaction processing.

The studio's security policy strictly prohibits installing third-party agents on any database virtual machines running on VMware. However, the studio requires deep network connection dependency mapping and process-level details for the non-database VMs on VMware to optimize the target cloud architecture. Additionally, they want to track the overall migration progress in a single dashboard, including servers migrated using a custom third-party migration tool.

Which combination of actions should the solutions architect recommend to discover this inventory and track the migration? (Select TWO.)

  1. Deploy the AWS Application Discovery Agent on the non-database VMware VMs to collect process-level and network connection details, and use the Application Discovery Service import process with a CSV template to import data for the bare-metal servers and database VMs.Answer
  2. Integrate the third-party migration tool with AWS Migration Hub by configuring the tool to call the Migration Hub APIs to publish migration status, and monitor the overall progress from the Migration Hub console.Answer
  3. C
    Deploy the AWS Application Discovery Agentless Collector on the VMware vCenter Server to collect network dependency mappings for all VMs, and configure a single non-redundant NAT Gateway in one Availability Zone to route the discovery data back to AWS.
  4. D
    Install the AWS Systems Manager Agent (SSM Agent) and CloudWatch Agent on all VMware VMs and bare-metal servers, and use a custom CloudWatch log path pattern to scrape process dependencies and publish them to Migration Hub.
  5. E
    Install the AWS Application Migration Service (MGN) replication agent on the bare-metal FreeBSD and IBM AIX servers to discover their configurations, and ensure TCP port 1500 is open in the on-premises firewall for the discovery traffic.

Answer

The correct actions are: deploying the AWS Application Discovery Agent on the non-database VMware VMs while importing bare-metal and database server details using a CSV template, and integrating the third-party migration tool with AWS Migration Hub via APIs to track progress.
Deploying the AWS Application Discovery Agent on the non-database VMware VMs satisfies the requirement for process-level and network dependency mapping. Because database VMs are prohibited from having agents and the bare-metal FreeBSD and IBM AIX servers run operating systems that are unsupported by the discovery agent and collector, importing their specifications via the Application Discovery Service CSV template is the only valid discovery method. Integrating the third-party tool with Migration Hub using API calls allows status updates to be published and monitored from the Migration Hub console, providing a single tracking dashboard.

Step-by-Step Solution

1
Analyze on-premises OS compatibility and security restrictions for discovery.
Identify that the database VMs cannot have agents, and that the FreeBSD and IBM AIX bare-metal servers run operating systems unsupported by standard AWS discovery tools.
This determines that these servers must be cataloged using the Application Discovery Service CSV import template.
2
Select the correct discovery mechanism for the remaining VMware VMs.
Recommend the AWS Application Discovery Agent (agent-based) for the non-database CentOS and Windows VMs.
The studio requires deep process-level details and network connection dependency mapping, which can only be gathered by the agent, not the Agentless Collector.
3
Establish migration tracking integration for the third-party tool.
Configure the third-party migration tool to publish status updates using the AWS Migration Hub APIs.
This allows all migrated servers to be visualized in the single Migration Hub dashboard alongside native migrations.

Key Concept

AWS Application Discovery Service supports agent-based discovery, agentless discovery, and CSV imports. The agent-based approach is required for process-level and network dependency mapping. Unsupported operating systems (such as FreeBSD and AIX) and systems with agent installation restrictions must be cataloged using CSV imports. AWS Migration Hub provides a central console to track migration progress using AWS tools and integrated third-party tools via API.
Rate this question

Topics

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

More questions from this topic