Your on-premises datacenter contains physical servers and Hyper-V virtual machines. You have an Azure subscription. You plan to use Azure Migrate to perform the following tasks: Migrate the physical s

Question

Explanation

This question tests knowledge of Azure Migrate's distinct migration mechanisms for physical servers versus Hyper-V virtual machines. Each source type requires a different tool or replication approach within the Azure Migrate: Server Migration service.

Approach. For migrating physical servers to Azure VMs, you must use agent-based replication - this requires deploying a replication appliance on-premises and installing the Azure Site Recovery Mobility Service agent on each physical server, since there is no hypervisor layer to leverage for agentless replication. For migrating Hyper-V virtual machines, you use agentless migration - you deploy the Azure Migrate appliance on the Hyper-V host and install the Microsoft Azure Site Recovery Provider on each Hyper-V host, which replicates VMs at the hypervisor level without touching individual guest VMs. The core distinction is that agentless Hyper-V migration uses Hyper-V Replica technology under the hood, while physical server migration has no equivalent hypervisor-level hook and must fall back to per-machine agents.

Concept tested. Azure Migrate: Server Migration - understanding the difference between agent-based migration (required for physical servers and VMware agent-based) versus agentless migration (available for Hyper-V and VMware agentless), and which on-premises components (replication appliance + Mobility Service vs. Azure Migrate appliance + ASR Provider) are deployed for each scenario.

Reference. https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix-hyper-v-migration and https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix-physical

No community discussion yet for this question.