Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure virtual machine named VM1. VM1 was deployed by using a custom Azure Resource Manager template named ARM1.json.
You receive a notification that VM1 will be affected by maintenance.
You need to move VM1 to a different host immediately.
Solution: From the Overview blade, you move the virtual machine to a different resource group.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
You should redeploy the VM.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/redeploy-to-new-nodeNo, the solution of moving the virtual machine to a different resource group from the Overview blade does not meet the goal of moving VM1 to a different host immediately.
The reason is that moving the virtual machine to a different resource group will not cause it to move to a different host. A resource group is simply a logical container for managing and organizing Azure resources. Moving a virtual machine to a different resource group will not change the underlying physical infrastructure on which it is running.
To move a virtual machine to a different host, you need to use the Azure platform's Maintenance control feature, which can be accessed via the Azure portal or through Azure PowerShell. Maintenance control allows you to evacuate a virtual machine from its current host to another host, either manually or automatically.
To evacuate a virtual machine manually using Maintenance control in the Azure portal, follow these steps: