An aerospace defense systems provider is planning to migrate its mission-critical flight m… — AWS Certified Solutions Architect - Professional

An aerospace defense systems provider is planning to migrate its mission-critical flight monitoring and logistics workloads to AWS. The on-premises environment consists of:

* $150$ VMware vSphere virtual machines (VMs) running a mix of Linux and Windows.
* $40$ physical bare-metal servers running IBM AIX $7.2$ .
* $15$ physical bare-metal servers running CentOS $7.9$ .

The company's security compliance policy strictly forbids installing any third-party agents or software directly inside the guest operating systems of the virtualized VMware environment. Outbound internet access from the bare-metal network segment is prohibited, except through an authenticated on-premises forward proxy. The provider wants to gather configuration and performance utilization data for all workloads, along with process-level network dependency details for the CentOS servers. Finally, they require a centralized dashboard to track the migration status using both AWS Migration Service tools and their existing third-party migration tracking tool.

Which migration discovery and tracking strategy should a solutions architect recommend?

A
Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware environment. Install the AWS Application Discovery Agent on all physical servers, including the CentOS and AIX systems, configuring them to route outbound traffic through the forward proxy. Use AWS Systems Manager Inventory to collect network dependency details. Register all discoveries in AWS Migration Hub, and use AWS Systems Manager to track third-party migration tool activities.
B
Install the AWS Application Discovery Agent on the VMware VMs and the CentOS physical servers. Configure the CentOS agents to use the on-premises forward proxy for outbound communication. Use the AWS Application Discovery Agentless Collector to discover the AIX servers by connecting directly to their management interfaces. Perform all tracking using the AWS Application Discovery Service console, and configure a webhook to sync the data to AWS Migration Hub.
Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware environment. Install the AWS Application Discovery Agent on the $15$ CentOS physical servers, configured to route outbound traffic through the on-premises forward proxy. Manually import the configuration data of the $40$ AIX physical servers using the Application Discovery Service CSV template. Configure AWS Migration Hub to aggregate the discovery data and integrate the third-party migration tracking tool.Answer
D
Deploy the AWS Application Discovery Agentless Collector to discover the VMware VMs and the CentOS physical servers. Perform a manual import using the Application Discovery Service CSV template for the $40$ AIX physical servers. Use AWS Systems Manager Distributor to deploy the third-party migration tracking tool across all environments, and utilize Amazon CloudWatch dashboards to track migration progress.

Answer

Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware environment. Install the AWS Application Discovery Agent on the CentOS physical servers, configured to route outbound traffic through the on-premises forward proxy. Manually import the configuration data of the AIX physical servers using the Application Discovery Service CSV template. Configure AWS Migration Hub to aggregate the discovery data and integrate the third-party migration tracking tool.

Deploying the AWS Application Discovery Agentless Collector in the VMware environment respects the restriction against guest-level agent installations. The CentOS physical servers, which require process-level and dependency tracking, are supported by the Application Discovery Agent, which can be configured to communicate via the on-premises forward proxy. Since IBM AIX is not supported by the discovery agent, manually importing configuration details via a CSV template is the correct method. AWS Migration Hub serves as the central hub to aggregate discovery data and supports tracking integration with third-party tools.

Step-by-Step Solution

Determine the discovery mechanism for the VMware vSphere VMs.

The AWS Application Discovery Agentless Collector must be deployed as an OVA virtual appliance.

Installing agents inside guest VMs is prohibited by the customer's compliance policy.

Determine the discovery and networking approach for CentOS physical servers.

The AWS Application Discovery Agent is installed on CentOS servers and configured with proxy variables.

CentOS physical servers need process-level dependencies, and the agent supports proxy settings to route outbound traffic through the on-premises forward proxy.

Evaluate the discovery mechanism for the bare-metal AIX servers.

A CSV import template must be populated and imported manually into AWS Application Discovery Service.

IBM AIX is not supported by either the Application Discovery Agent or the Agentless Collector.

Determine the tracking and third-party integration platform.

AWS Migration Hub must be used to track the migration and aggregate discovery data.

AWS Migration Hub natively supports tracking migration status from both AWS tools and integrated third-party migration tools.

Key Concept

Selecting and configuring AWS Application Discovery Service agents, agentless collectors, and CSV import mechanisms based on operating system, hypervisor, security, and networking requirements, and consolidating discovery and migration tracking in AWS Migration Hub.

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic