Examkin

Soru

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

A healthcare software provider is planning to migrate its legacy patient portal and clinical analytics platform to AWS. The on-premises infrastructure consists of 80 VMware vSphere VMs running supported Linux and Windows operating systems, and 10 physical bare-metal servers running legacy AIX. The security team prohibits installing any software agents on the virtualized database VMs due to compliance requirements, but requires identifying system configurations and CPU/memory utilization. For the remaining VMs, the migration team must identify active network connections, running processes, and inbound/outbound traffic destinations to map dependencies. The migration progress must be tracked centrally alongside a third-party migration tool. Which combination of discovery mechanisms and tracking tools should the solutions architect recommend?

  1. Deploy the AWS Application Discovery Agent on the non-database VMware VMs. Deploy the AWS Application Discovery Agentless Collector in the VMware environment to collect database VM configuration and performance metrics. Import details for the physical AIX servers using a CSV template, and track migration status centrally via AWS Migration Hub.Cevap
  2. B
    Deploy the AWS Application Discovery Agent on all VMware VMs and physical AIX servers. Use AWS Application Discovery Agentless Collector to monitor network traffic at the hypervisor level for the database VMs, and track the progress in AWS Systems Manager.
  3. C
    Deploy the AWS Application Discovery Agentless Collector in the VMware environment to discover the database VMs and non-database VMs. Use the AWS Schema Conversion Tool (SCT) to scan the legacy AIX servers, and track the migration progress using AWS Resource Access Manager.
  4. D
    Deploy the AWS Application Discovery Agent on the database VMs, and deploy the AWS Application Discovery Agentless Collector in the VMware environment for the non-database VMs. Install the AWS Application Migration Service (MGN) agent on the physical AIX servers, and track migration progress using AWS Systems Manager OpsCenter.

Cevap

Deploy the AWS Application Discovery Agent on the non-database VMware VMs. Deploy the AWS Application Discovery Agentless Collector in the VMware environment to collect database VM configuration and performance metrics. Import details for the physical AIX servers using a CSV template, and track migration status centrally via AWS Migration Hub.
The correct option addresses all server categories and tracking needs: the AWS Application Discovery Agent is used where process-level network dependencies are needed and permitted; the AWS Application Discovery Agentless Collector is deployed in the VMware environment to gather metadata for the database VMs without agent installation; the unsupported physical AIX servers are imported using a CSV template; and AWS Migration Hub is used to aggregate the data and track progress alongside third-party tools.

Adım Adım Çözüm

1
Analyze the requirements for the VMware vSphere database virtual machines.
Since software agents are prohibited on database VMs, but basic configuration and utilization metrics are required, the AWS Application Discovery Agentless Collector is chosen because it runs as a VM inside VMware vCenter and does not install agents on individual guest OSs.
Ensures compliance with the security team's restriction while obtaining the necessary utilization and configuration details.
2
Analyze the requirements for the remaining VMware virtual machines.
The remaining VMs require process-level network connections and inbound/outbound mappings. The AWS Application Discovery Agent must be installed on these VMs since the Agentless Collector cannot collect network dependency mapping details.
Provides deep discovery details including network and process relationships needed for migration grouping.
3
Determine the discovery mechanism for the physical bare-metal AIX servers.
Neither the AWS Application Discovery Agent nor the Agentless Collector supports physical AIX servers. The configuration details of these servers must be imported into AWS Application Discovery Service using a formatted CSV file.
Allows capturing and listing unsupported legacy architectures in the migration inventory.
4
Determine the tracking dashboard and tool integration requirements.
AWS Migration Hub must be utilized because it centralizes migration tracking across both AWS discovery tools and supported third-party migration tools.
Fulfills the requirement to centrally track migration progress alongside third-party tools.

Anahtar Kavram

Selecting the correct discovery mechanisms (Agent, Agentless, and Import) based on operating system support and security compliance, and tracking migration progress centrally with AWS Migration Hub.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru