AZ-801 · Question #183
You have an on-premises Hyper-V deployment that hosts multiple virtual machines. You have an Azure subscription that contains an Azure Migrate project named Project1. You plan to migrate the virtual m
The correct answer is C. Generate a project key.. To discover Hyper-V hosts and virtual machines for migration to Azure using an Azure Migrate project, the first step is to generate a project key.
Question
Options
- ARegister an appliance.
- BCreate a private endpoint.
- CGenerate a project key.
- DDeploy an Azure Network Adapter.
How the community answered
(34 responses)- A15% (5)
- B6% (2)
- C71% (24)
- D9% (3)
Why each option
To discover Hyper-V hosts and virtual machines for migration to Azure using an Azure Migrate project, the first step is to generate a project key.
Registering an appliance is done after deploying the appliance on-premises and requires the project key generated in Azure Migrate.
Creating a private endpoint is an optional network configuration for secure connectivity, not the first step for discovering on-premises Hyper-V environments with Azure Migrate.
Generating a project key within the Azure Migrate project is the initial step required to securely register the Azure Migrate appliance. This appliance, deployed on-premises, uses the project key to establish communication with the Azure Migrate project and begin the discovery of Hyper-V hosts and virtual machines.
Deploying an Azure Network Adapter is not a component used for the discovery of on-premises Hyper-V virtual machines by Azure Migrate.
Concept tested: Azure Migrate Hyper-V discovery prerequisites
Source: https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-hyper-v
Topics
Community Discussion
No community discussion yet for this question.