Examkin

Soru

Zorluk: Çok zorMigration Discovery, Planning, and Tracking (Application Discovery Service, Migration Hub)

A telecommunications service provider is planning to migrate its primary billing and network analytics platform to AWS. The on-premises infrastructure is distributed across different network zones and virtualization technologies:

1. Analytics Tier: 300 VMware vSphere VMs running Rocky Linux. The internal security policy strictly prohibits the installation of any third-party agents or software inside the operating systems of these VMs, and does not allow sharing or configuring OS-level administrative credentials.
2. Billing Core: 40 physical bare-metal servers running Red Hat Enterprise Linux (RHEL) 8. These servers reside in a secured, air-gapped network zone with no direct route to the internet, but outbound traffic to an on-premises HTTPS forward proxy is permitted.
3. Legacy Processing: 10 physical bare-metal servers running FreeBSD 12.

The provider needs to perform discovery to analyze server dependencies, collect server utilization data to size target EC2 instances, and continuously track the migration progress of these workloads inside AWS Migration Hub. Which combination of discovery and tracking mechanisms should a Solutions Architect recommend?

  1. A
    Install the AWS Application Discovery Agent on all 300 VMware VMs and the 40 RHEL bare-metal servers, configuring the agents to route traffic through the on-premises HTTPS proxy. For the 10 FreeBSD servers, deploy the Agentless Collector in the VMware environment and configure it to scan the bare-metal subnet using SNMP to discover their hardware configuration. Group all discovered systems into applications within AWS Migration Hub.
  2. Deploy the AWS Application Discovery Agentless Collector as a virtual appliance in the VMware vSphere environment to discover VM configurations and utilization data. Install the AWS Application Discovery Agent on the 40 RHEL bare-metal servers, configured to route outbound traffic through the on-premises HTTPS proxy. Manually collect configuration details for the 10 FreeBSD servers and import them using the AWS Migration Hub import template. Group all discovered and imported servers into applications within AWS Migration Hub.Cevap
  3. C
    Deploy the AWS Application Discovery Agentless Collector in the VMware vSphere environment. Configure it to discover the 300 VMware VMs, and enable the Agentless Collector's network-based host discovery feature using OS-level credentials to discover the 40 RHEL and 10 FreeBSD bare-metal servers on the network. Import the resulting configurations directly into AWS Migration Hub, and use AWS Systems Manager Inventory to collect performance metrics.
  4. D
    Deploy the AWS Application Discovery Agentless Collector to discover the 300 VMware VMs by configuring it with read-only vCenter credentials. Install the AWS Application Discovery Agent on the 40 RHEL bare-metal servers and the 10 FreeBSD bare-metal servers, establishing an AWS Site-to-Site VPN to route their discovery traffic directly to AWS, bypassing the local proxy. Import all server metrics into AWS Migration Hub using the import API.

Cevap

The correct answer is the option that deploys the Agentless Collector for the VMware VMs, installs the Discovery Agent on the RHEL bare-metal servers configured with a proxy, manually imports the FreeBSD servers using the Migration Hub CSV import template, and groups the servers into applications in AWS Migration Hub.
The correct option correctly maps each environment to its technically viable and policy-compliant discovery mechanism. The VMware VMs are discovered agentlessly via the vCenter API using the Agentless Collector, which requires no guest OS modifications or credentials. The RHEL bare-metal servers use the Discovery Agent configured with an HTTPS proxy, which is natively supported. The FreeBSD bare-metal servers, which run an unsupported OS and cannot be discovered agentlessly, are handled via manual CSV import. Finally, grouping the systems into applications in AWS Migration Hub enables tracking.

Adım Adım Çözüm

1
Evaluate the discovery options for the 300 VMware VMs under the constraint of no OS agents and no OS credentials.
Determine that the AWS Application Discovery Agentless Collector is the only suitable choice because it gathers configuration and utilization data agentlessly via the vCenter API.
It respects the security policy prohibiting guest OS agents or credential sharing.
2
Evaluate the discovery options for the 40 RHEL 8 bare-metal servers in the air-gapped zone.
Choose the AWS Application Discovery Agent and configure it to route traffic through the allowed on-premises HTTPS proxy.
Agentless Collector cannot discover physical bare-metal servers. RHEL 8 is a supported OS for the Discovery Agent, and the agent supports proxy settings to overcome the lack of direct internet access.
3
Evaluate the discovery options for the 10 FreeBSD 12 bare-metal servers.
Collect their details manually and use the Migration Hub Import template (CSV format).
FreeBSD is not supported by the Discovery Agent, and Agentless Collector cannot discover bare-metal systems, making manual import the only viable method.
4
Determine how to track the overall migration progress.
Group the discovered and imported servers into applications within the AWS Migration Hub console.
Migration Hub requires servers to be associated with applications to track migration progress dynamically.

Anahtar Kavram

Selecting the correct AWS Application Discovery mechanisms based on operating system support, hypervisor integration, and network proxy constraints.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru