Examkin

Question

Difficulty: HardMigration Discovery, Planning, and Tracking (Application Discovery Service, Migration Hub)

A global retail banking corporation is planning to migrate its hybrid on-premises application portfolio to AWS. The environment consists of 300 VMware vSphere virtual machines (VMs) running supported Linux and Windows Server operating systems, 50 physical servers running Oracle Solaris, and 20 bare-metal servers running CentOS. Security policies mandate that database servers have no direct internet access and must route outbound traffic through a central corporate HTTP proxy. The security team also prohibits installing any software agents on the VMware ESXi hypervisors. The corporation requires detailed host performance data, running process lists, and network dependency mappings to plan the migration, and wants to track the discovery progress centrally using AWS Migration Hub. Which two actions should a solutions architect recommend to perform the discovery? (Select two.)

  1. Deploy the AWS Application Discovery Agent on the bare-metal CentOS servers and VMware VMs, configuring the agents to route outbound traffic through the central corporate HTTP proxy.Answer
  2. Collect the configuration and utilization details for the Oracle Solaris physical servers, format the data using the standard AWS Application Discovery Service CSV template, and import it into AWS Migration Hub.Answer
  3. C
    Deploy the AWS Application Discovery Agentless Collector in the VMware vCenter Server environment to capture the running process lists and active network connections of the VMs.
  4. D
    Install the AWS Application Migration Service (MGN) replication agent on all bare-metal servers and VMware VMs to discover running processes and automatically map network dependencies.
  5. E
    Use the AWS Application Discovery Agent on the Oracle Solaris physical servers by routing the metrics transitively over a physical AWS Snowball Edge device deployed on-premises.

Answer

Deploy the AWS Application Discovery Agent on the bare-metal CentOS servers and VMware VMs, configuring the agents to route outbound traffic through the central corporate HTTP proxy. Additionally, collect the configuration and utilization details for the Oracle Solaris physical servers, format the data using the standard AWS Application Discovery Service CSV template, and import it into AWS Migration Hub.
The correct options are deploying the AWS Application Discovery Agent on the bare-metal CentOS servers and VMware VMs, and importing Solaris server data via CSV. The Application Discovery Agent is required because the scenario specifies a need for network dependency mapping and running process lists, which the Agentless Collector does not support. The agents can be configured to communicate via the corporate proxy, satisfying the security requirements. Since Oracle Solaris is not supported by the Application Discovery Agent, importing the configuration data via a CSV template is the correct method to track those servers.

Step-by-Step Solution

1
Analyze the requirements for data collection types (process lists, network dependency mapping) and match them to the discovery tool capabilities.
The agent-based AWS Application Discovery Service is selected for CentOS and supported VMware VMs because the Agentless Collector cannot gather OS-level details such as active network connections and process lists.
Agentless collector only gathers VM configuration and CPU/RAM utilization from VMware vCenter, not deep network dependency mapping or running process lists.
2
Assess operating system compatibility and network constraints for the discovery agents.
The Application Discovery Agent is deployed on the CentOS servers and VMware VMs with proxy settings configured. However, Oracle Solaris is not supported by the agent.
Solaris is a Unix OS not supported by the Application Discovery Agent. The agent can route outbound HTTPS (port 443) traffic through a web proxy to handle the corporate security policy.
3
Determine the discovery mechanism for the unsupported Oracle Solaris servers.
Manual collection of Solaris configuration data is performed, and the results are formatted and imported using the standard CSV template in AWS Migration Hub.
CSV import allows the inclusion of unsupported operating systems and servers in Migration Hub for tracking.

Key Concept

Selecting the correct discovery mechanism (agent-based vs. agentless vs. CSV import) in AWS Application Discovery Service based on operating system compatibility, security/proxy requirements, and the need for network dependency mapping.
Rate this question

Topics

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

More questions from this topic