nerdexam
Microsoft

AZ-801 · Question #101

You have three servers named Server1, Server2, and Server3 that run Windows Server and have the Hyper-V server role installed. Server1 hosts an Azure Migrate appliance named Migrate1. You plan to migr

The correct answer is A. On Migrate1, add a discovery source.. To ensure new virtual machines on all three Hyper-V servers are discovered by Azure Migrate, you must explicitly add each Hyper-V host as a discovery source to the Migrate appliance.

Migrate servers and workloads

Question

You have three servers named Server1, Server2, and Server3 that run Windows Server and have the Hyper-V server role installed. Server1 hosts an Azure Migrate appliance named Migrate1. You plan to migrate virtual machines to Azure. You need to ensure that any new virtual machines created on Server1, Server2, and Server3 are available in Azure Migrate. What should you do?

Options

  • AOn Migrate1, add a discovery source.
  • BOn the DNS server used by Migrate 1, create a GlobalName zone.
  • COn Migrate1, set the Startup Type of the Computer Browser service to Automatic
  • DOn the network that has Migrate1 deployed, deploy a WINS server.

How the community answered

(21 responses)
  • A
    81% (17)
  • B
    5% (1)
  • C
    10% (2)
  • D
    5% (1)

Why each option

To ensure new virtual machines on all three Hyper-V servers are discovered by Azure Migrate, you must explicitly add each Hyper-V host as a discovery source to the Migrate appliance.

AOn Migrate1, add a discovery source.Correct

The Azure Migrate appliance, by default, only discovers VMs on the host it resides on unless additional hosts are specified. To discover virtual machines on Server2 and Server3, you must configure them as discovery sources within the Migrate1 appliance's settings, providing necessary credentials for access. This action allows the appliance to connect to these hosts and enumerate their virtual machines for migration.

BOn the DNS server used by Migrate 1, create a GlobalName zone.

Creating a GlobalName zone on the DNS server is used for single-label name resolution and is unrelated to Azure Migrate's VM discovery process.

COn Migrate1, set the Startup Type of the Computer Browser service to Automatic

The Computer Browser service is a legacy Windows service for network discovery and has no bearing on Azure Migrate's ability to discover Hyper-V virtual machines.

DOn the network that has Migrate1 deployed, deploy a WINS server.

Deploying a WINS server is for NetBIOS name resolution in older networks and is not relevant for Azure Migrate's discovery of Hyper-V VMs.

Concept tested: Azure Migrate Hyper-V VM discovery

Source: https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-hyper-v

Topics

#Azure Migrate#Hyper-V#VM Discovery#Migration Planning

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-801 Practice