You have an on-premises SAP landscape that is hosted on VMware vSphere and contains 50 virtual machines. You need to perform a lift-and-shift migration to Azure by using Azure Migrate. The solution…

Question

Options

• Aan Azure Backup server
• Ban Azure VPN gateway
• Can Azure Migrate configuration server
• Dan Azure Migrate process server

• A
  2% (1)
• B
  6% (3)
• C
  90% (47)
• D
  2% (1)

Explanation

Deploying the Azure Migrate configuration server first is required because it acts as the on-premises coordination hub - it registers with your Azure Migrate project, discovers VMware VMs via vCenter, and orchestrates replication. Without it, no other migration components can function, as both the process server and mobility agents must register back to the configuration server.

Why the distractors are wrong:

• (A) Azure Backup server is a backup solution, not a migration tool - it plays no role in a lift-and-shift migration workflow.
• (B) Azure VPN gateway provides network connectivity between on-premises and Azure, but it is not Azure Migrate-specific and is not a prerequisite before discovery begins.
• (D) Azure Migrate process server handles data replication and caching, but it is a dependent component - it must register to an already-running configuration server, so it comes second, not first.

Memory tip: Think of the configuration server as the "mother ship" - every other Azure Migrate component (process servers, mobility agents on VMs) must phone home to it. You always launch the mother ship before sending out the smaller craft.

No community discussion yet for this question.