Examkin

Soru

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

A digital media platform is planning a large-scale migration of its application portfolio to AWS. The current on-premises infrastructure consists of 150 VMware vSphere virtual machines (VMs) and 25 physical bare-metal servers running CentOS. Due to strict corporate security and compliance policies, installing any software agents on the VMware VMs is strictly prohibited. However, agents are permitted on the physical bare-metal servers. The Solutions Architect must collect CPU and memory utilization history for right-sizing calculations across all servers, determine network dependencies for the physical servers to plan migration groups, and consolidate all tracking data in AWS Migration Hub. Which TWO actions should the Solutions Architect take to perform this discovery and tracking? (Select TWO.)

  1. Deploy the AWS Application Discovery Agentless Collector as an OVA virtual appliance in the VMware environment to gather VM inventory, configuration, and performance history.Cevap
  2. Install the AWS Application Discovery Agent on the physical bare-metal servers to collect system performance, running processes, and inbound/outbound network dependencies.Cevap
  3. C
    Install the AWS Application Discovery Agent on the VMware vCenter Server to automatically push and run the agent within the guest operating systems of the VMs.
  4. D
    Install the AWS Application Discovery Agentless Collector directly on the physical bare-metal servers to discover network dependencies without installing guest agents.
  5. E
    Import a flat CSV file containing the network dependency mapping of the VMware VMs into AWS Migration Hub using the Migration Hub Import tool.

Cevap

Deploy the AWS Application Discovery Agentless Collector in the VMware environment and install the AWS Application Discovery Agent on the physical bare-metal servers.
To satisfy the requirements under strict compliance, the solutions architect must use the AWS Application Discovery Agentless Collector for the VMware VMs. The Agentless Collector runs as a virtual appliance in the vSphere environment and queries vCenter for inventory and performance metrics, avoiding any guest-level agent installations. For the physical bare-metal servers, where agents are permitted, installing the AWS Application Discovery Agent is required because agentless discovery cannot run on bare-metal systems, and only the agent-based method can capture the network dependency mapping necessary for migration group planning.

Adım Adım Çözüm

1
Address the VMware VM discovery while complying with the agent-less restriction.
Deploy the AWS Application Discovery Agentless Collector as an OVA appliance in vCenter.
This allows agentless discovery of VM inventory, configuration, and performance history without installing guest-level agents.
2
Address the physical bare-metal server discovery and dependency mapping.
Install the AWS Application Discovery Agent directly on the physical bare-metal servers.
Since agents are permitted on the physical servers, using the Agent is necessary because physical servers cannot be discovered agentlessly, and agents are required to collect network dependency mappings.
3
Verify integration with AWS Migration Hub for central tracking.
Configure both the Agentless Collector and the Discovery Agents to send data to the AWS Application Discovery Service, which automatically populates AWS Migration Hub.
This consolidates all discovery data in a single dashboard for tracking and planning.

Anahtar Kavram

Choosing between agent-based and agentless discovery mechanisms based on VM vs physical environments and compliance rules, and mapping dependencies.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru