A multinational retail corporation is migrating its supply chain management platform to AW… — AWS Certified Solutions Architect - Professional

A multinational retail corporation is migrating its supply chain management platform to AWS. The current on-premises environment consists of 300 VMware vSphere virtual machines (VMs) running Windows Server 2022 and Red Hat Enterprise Linux 8, and 50 bare-metal legacy servers running IBM AIX on POWER processors. Corporate compliance mandates that no software agents may be installed on any production server operating systems. The on-premises network has no direct internet connectivity, but an HTTP proxy is available for outbound HTTPS traffic (port 443) to AWS endpoints without SSL decryption. The company wants to use AWS Migration Hub to track the migration, utilizing both partner-integrated third-party tools and AWS migration tools. Which strategy should a solutions architect recommend to perform the discovery and track the migration progress?

Deploy the AWS Application Discovery Service Agentless Collector as a virtual appliance in the VMware environment. Configure the collector with the corporate HTTP proxy credentials to upload virtual machine configuration and performance metadata. For the IBM AIX bare-metal servers, collect server specifications and utilization metrics manually, and import them using the AWS Migration Hub import CSV template. Register the third-party migration tools with AWS Migration Hub and use their native integrations to publish migration status updates to the Migration Hub dashboard.Answer
B
Deploy the AWS Application Discovery Agent on all VMware VMs and IBM AIX bare-metal servers. Configure the agents to route discovery traffic through the corporate HTTP proxy to the AWS Application Discovery Service endpoints. Track the migration using the AWS Migration Hub dashboard.
C
Deploy the AWS Application Discovery Service Agentless Collector in the VMware environment. Configure it to discover both the VMware VMs and the IBM AIX bare-metal servers by providing the collector with SSH credentials for the AIX hosts. Import the discovery data into AWS Systems Manager, and use Systems Manager to update migration tracking in AWS Migration Hub.
D
Deploy AWS Systems Manager Quick Setup to configure host management on all on-premises VMs and bare-metal AIX servers to collect hardware inventory and performance metrics. Export the gathered data to Amazon S3, and use AWS Glue to import the inventory into AWS Migration Hub. Use AWS Step Functions to update the migration status in Migration Hub.

Answer

Deploy the AWS Application Discovery Service Agentless Collector as a virtual appliance in the VMware environment. Configure the collector with the corporate HTTP proxy credentials to upload virtual machine configuration and performance metadata. For the IBM AIX bare-metal servers, collect server specifications and utilization metrics manually, and import them using the AWS Migration Hub import CSV template. Register the third-party migration tools with AWS Migration Hub and use their native integrations to publish migration status updates to the Migration Hub dashboard.

The correct strategy uses the AWS Application Discovery Service Agentless Collector for the VMware VMs to comply with the agentless mandate. The collector is configured to use the corporate HTTP proxy for outbound communication. Since IBM AIX on POWER is unsupported by both the Agentless Collector and the Discovery Agent, the specifications for these servers must be imported manually using the Migration Hub CSV template. Finally, Migration Hub supports native integration with third-party tools, allowing them to report migration status updates via the API directly to the dashboard.

Step-by-Step Solution

Select the discovery tool for the virtualized VMware environment that complies with the security agent restriction.

Identify the AWS Application Discovery Service Agentless Collector as the appropriate tool because it is deployed as an OVA virtual appliance and collects metadata directly from vCenter without requiring OS-level agent installation.

Corporate compliance prohibits installing third-party software agents directly onto production server operating systems.

Determine the discovery mechanism for the non-virtualized IBM AIX on POWER legacy servers.

Choose manual discovery and import via the AWS Migration Hub import CSV template.

The AWS Application Discovery Agent does not support the IBM AIX operating system or POWER CPU architecture, and the Agentless Collector only queries VMware vCenter environments.

Address the network connectivity constraints for sending metadata to AWS.

Configure the Agentless Collector with proxy settings to use the corporate HTTP proxy for outbound HTTPS (port 443) communication to AWS.

The on-premises network lacks direct internet access but permits outbound HTTPS via an explicit forward proxy.

Configure tracking for the heterogeneous set of migration tools in AWS Migration Hub.

Register the partner-integrated migration tools in Migration Hub to allow them to publish migration status updates directly to the dashboard.

AWS Migration Hub integrates natively with various third-party migration tools via the Migration Hub API to provide a unified tracking dashboard.

Key Concept

Selecting and configuring AWS migration discovery mechanisms based on agent compatibility, operating system constraints, network proxy requirements, and tracking migration status using partner integrations in AWS Migration Hub.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic