Examkin

Question

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

A public sector transit authority is preparing to migrate its transport management and ticketing systems to AWS. The on-premises infrastructure consists of two environments:

1. A VMware vSphere cluster hosting 150 virtual machines (VMs) running x86-based CentOS and Windows Server.
2. A separate IBM Power Systems environment hosting 15 physical bare-metal servers running IBM AIX for legacy transaction processing.

The authority's security compliance policy strictly prohibits the installation of any third-party software agents on the CentOS and Windows VMs. However, the project team must perform an initial discovery phase to gather hardware specifications (CPU, RAM, and disk capacity) and utilization metrics for these VMs to size the AWS target environment. Additionally, they must inventory the physical AIX servers and consolidate all discovered resource details into AWS Migration Hub to track the migration.

Which of the following discovery strategies should the Solutions Architect implement to meet these requirements?

  1. Deploy the AWS Application Discovery Agentless Collector as an OVA in the VMware vCenter environment to discover the VMware VMs. For the physical AIX servers, use the AWS Migration Hub import template to manually upload a CSV file containing their inventory and configuration details.Answer
  2. B
    Install the AWS Application Discovery Agent on the physical AIX servers to collect their configuration. Deploy the AWS Application Discovery Agentless Collector in the VMware vCenter environment to discover the VMware VMs without installing software on them.
  3. C
    Deploy the AWS Application Discovery Agentless Collector in the VMware vCenter environment and configure it to scan the network subnet of the physical AIX servers using SSH credentials to discover the AIX servers agentlessly.
  4. D
    Install the AWS Systems Manager (SSM) Agent on both the VMware VMs and the physical AIX servers, enable SSM Inventory, and use the AWS Systems Manager integration to sync the discovered resource data directly to AWS Migration Hub.

Answer

Deploy the AWS Application Discovery Agentless Collector as an OVA in the VMware vCenter environment to discover the VMware VMs. For the physical AIX servers, use the AWS Migration Hub import template to manually upload a CSV file containing their inventory and configuration details.
The correct strategy uses the AWS Application Discovery Agentless Collector to query the VMware vCenter Server. This agentless approach gathers VM metadata and utilization metrics directly from vCenter, satisfying the security policy prohibiting software agent installation on the CentOS and Windows VMs. Since the physical AIX servers are on non-VMware hardware and run an operating system unsupported by the AWS Application Discovery Agent, they must be registered in AWS Migration Hub by manually importing their configurations using a CSV file template.

Step-by-Step Solution

1
Analyze the discovery requirements for the VMware vSphere environment.
Since agent installation is prohibited, the Agentless Collector is the appropriate tool. It runs as an OVA appliance in vCenter and collects VM specs and performance metrics without guest-level agents.
To comply with the security policy prohibiting agents on the CentOS and Windows VMs.
2
Analyze the discovery options for the physical IBM AIX servers.
AWS Application Discovery Agents do not support AIX operating systems (only Windows and x86/x64 Linux). The Agentless Collector only works inside VMware environments. Thus, native automatic discovery is not possible.
To identify constraints of native AWS Discovery tools on legacy non-x86 physical infrastructure.
3
Select a method to consolidate the AIX server inventory into AWS Migration Hub.
AWS Migration Hub allows importing server data manually via a formatted CSV file.
To ensure that all assets, including legacy servers, are tracked in a single pane of glass in AWS Migration Hub.

Key Concept

Discovery tool compatibility and tracking limits based on OS, virtualization, and agent deployment constraints.

Alternative Method

Utilize a Migration Hub-integrated third-party discovery and planning tool that natively supports agentless discovery of legacy UNIX operating systems and physical machines, automatically syncing the inventory to AWS Migration Hub.
Estimated Time:2m 30s
Rate this question

Topics

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

More questions from this topic