Examkin

Soru

Zorluk: OrtaMigration Discovery, Planning, and Tracking (Application Discovery Service, Migration Hub)

A multinational retail e-commerce company is planning to migrate its core inventory management system and order processing services to AWS. The on-premises infrastructure consists of 350 VMware vSphere virtual machines (VMs) running supported versions of Red Hat Enterprise Linux (RHEL) and Windows Server, and 20 bare-metal physical servers running IBM AIX for legacy transaction ledger processing. Security compliance policies strictly prohibit direct outbound internet access from database and application subnets, requiring all outbound traffic to traverse a centralized forward proxy. The migration team needs to gather detailed configuration, performance metrics (CPU, RAM, disk I/O), network connection dependencies, and process-level information for planning. Additionally, they must track the migration status dynamically in AWS Migration Hub using both AWS and partner migration tools. Which two actions should a solutions architect recommend to collect the discovery data and configure tracking?

  1. Deploy the AWS Application Discovery Agent on the VMware VMs, configure the agents to use the centralized forward proxy for outbound communication, and associate the discovered servers with applications in AWS Migration Hub.Cevap
  2. Use the Application Discovery Service import template to upload a CSV file with the configuration and performance details of the IBM AIX bare-metal servers, and integrate supported third-party migration tools with AWS Migration Hub to track the migration.Cevap
  3. C
    Deploy the Application Discovery Agentless Collector on the VMware vSphere environment to discover both the VMware VMs and the IBM AIX bare-metal servers, bypassing the need for any local agent installation or CSV import.
  4. D
    Deploy the AWS Application Discovery Agent on all VMware VMs and IBM AIX bare-metal servers, and configure on-premises firewalls to allow direct outbound traffic over TCP port 1500 to the AWS Application Migration Service endpoint.
  5. E
    Configure the Application Discovery Agentless Collector to collect network connection dependencies and process-level information for the VMware VMs, and establish an AWS Direct Connect gateway connection to route this metadata to AWS Migration Hub.

Cevap

Deploy the AWS Application Discovery Agent on the VMware VMs configured to use the forward proxy, and import the IBM AIX bare-metal server data via a CSV file using the import template, while integrating third-party tools with AWS Migration Hub.
The correct actions involve using the AWS Application Discovery Agent on supported VMware VMs because they require detailed process and network connection mapping, and routing their traffic via the centralized forward proxy. Since the IBM AIX bare-metal servers are not supported by the agent or the Agentless Collector, their data must be imported via a CSV file. AWS Migration Hub can then be configured to aggregate migration status updates from both AWS and supported third-party tools.

Adım Adım Çözüm

1
Evaluate the discovery requirements for the VMware virtual machines.
Since detailed performance metrics, network connection dependencies, and process-level information are needed, the agent-based AWS Application Discovery Agent must be selected (the Agentless Collector only collects basic VM-level metrics and does not map dependencies or processes). Configured the agents to use the proxy.
Meets security compliance guidelines prohibiting direct outbound internet access.
2
Evaluate the discovery requirements for the IBM AIX bare-metal servers.
The AWS Application Discovery Agent does not support IBM AIX, and the Agentless Collector only runs on VMware vSphere. Therefore, configuration and performance data for these servers must be imported using the CSV file template.
Allows capturing legacy bare-metal server inventory without unsupported agent installations.
3
Determine the tracking mechanism for both AWS and third-party tools.
Integrate supported third-party tools with AWS Migration Hub and associate the discovered servers with applications.
Provides a single console to track all migration progress.

Anahtar Kavram

Differentiating between AWS Application Discovery Service Agent-based and Agentless discovery mechanisms based on OS compatibility, virtualization environment, network connectivity requirements, and the depth of data (process and network dependencies) needed, and using Migration Hub to integrate and track migrations.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru