Examkin

Question

Difficulty: MediumMigration Assessment and Strategy

An organization is planning to migrate a legacy enterprise resource planning (ERP) application from on-premises physical servers to Azure Virtual Machines. The application's components communicate over several undocumented TCP ports, and the network communication dependencies between the servers must be fully mapped to prevent application downtime during the transition. Which configuration should you recommend to identify the server dependencies?

  1. Deploy the Azure Migrate appliance and install the Dependency agent and the Log Analytics agent on each physical server.Answer
  2. B
    Deploy the Azure Migrate appliance and configure agentless dependency mapping using server credentials.
  3. C
    Deploy an Azure SQL Database and use Azure Data Studio with the Azure SQL Migration extension to map server network connections.
  4. D
    Set up Microsoft Entra Connect with Cloud Sync to log and inventory the network connection paths between the servers.

Answer

Deploy the Azure Migrate appliance and install the Dependency agent and the Log Analytics agent on each physical server.
The correct configuration is to deploy the Azure Migrate appliance and install the Dependency agent and the Log Analytics agent on each physical server. Because agentless dependency analysis is not supported for physical servers, agent-based discovery using these agents is required to identify network dependencies and open ports.

Step-by-Step Solution

1
Identify the source environment and requirements.
The workloads are hosted on physical servers, and we need to map network communication dependencies.
Physical servers have different dependency mapping support compared to virtualized environments like VMware or Hyper-V.
2
Determine the supported dependency mapping mechanism.
Azure Migrate supports agentless dependency mapping only for VMware and Hyper-V virtual machines. For physical servers, agent-based dependency mapping is required.
Agent-based dependency mapping requires installing the Dependency agent and the Log Analytics agent on each server to capture network dependencies.
3
Select the correct migration assessment configuration.
Deploy the Azure Migrate appliance and install the required agents on the physical servers.
This configuration correctly maps the network dependencies of physical servers.

Key Concept

Azure Migrate dependency mapping for physical servers

Alternative Method

Instead of agent-based dependency mapping, if the workloads were running on VMware vSphere rather than physical servers, you could perform agentless dependency mapping via the Azure Migrate appliance using VM credentials.
Estimated Time:2m 0s
Rate this question

Topics

Migration Assessment and Strategy

More questions from this topic