Exam AZ-103 topic 3 question 18 discussion

Correct : Try redeploying your virtual machine, which will migrate it to a new Azure host. If you continue, the virtual machine will be restarted and you will lose any data on the temporary drive. While the redeployment is in progress, the virtual machine will be unavailable.

Where is the 'Redeploy Blade'? That's a weird question! It should be to go to the VM, on the left blade choose Redeploy + Reapply.

In the documentation about maintenance notifications, they say the following: https://docs.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications "Self-service maintenance might not be available for all of your VMs. To determine if proactive redeploy is available for your VM, look for the Start now in the maintenance status. Self-service maintenance is currently not available for Cloud Services (Web/Worker Role) and Service Fabric." This makes me wonder if they are actually trying to ask about immediately doing the maintenance and redeploying your VM, rather than waiting. Just redeploying it using the manner in the question will not avoid the maintenance problem, since it will redeploy in the same region that is scheduled for maintenance. It might very well still be scheduled for maintenance after redeploying this way. Instead, by using the "Start now" in the maintenance status will do the maintenance now and redeploy the VM, and thus avoid the problem. Thus, the correct answer is no.

The answer is correct. we need to redeploy.

I presume that host is the same as node: If you have been facing difficulties troubleshooting Remote Desktop (RDP) connection or application access to Windows-based Azure virtual machine (VM), redeploying the VM may help. When you redeploy a VM, Azure will shut down the VM, move the VM to a new node within the Azure infrastructure, and then power it back on, retaining all your configuration options and associated resources. This article shows you how to redeploy a VM using Azure PowerShell or the Azure portal. REDEPLOY will get the job done: https://docs.microsoft.com//en-us/azure/virtual-machines/windows/move-vm

No - although it will move the VM there will be downtime - and although the question doesn't explicitly state you should move the VM to avoid downtime, it is an implied requirement because of the word 'immediately'.

The Answer is No. I'm testing right now, when you go to Redeploy it's clealy stating that the VM will be unavailable. And this is for when you can't connect to the VM. "Can't connect to your virtual machine? Try redeploying your virtual machine, which will migrate it to a new Azure host. If you continue, the virtual machine will be restarted and you will lose any data on the temporary drive. While the redeployment is in progress, the virtual machine will be unavailable"

Redeploying the VM is not the solutions as redeployment is meant for instances where you cant access via RDP or other means. in this instance you have full access to your VM but need to move it to avoid downtime that will be created by maintenance so it wont make any sense to crate down time in order to avoid downtime. Moving the VM does not stop the VM and does not create down time so IMO the answer is B, the solution does not meet the requirement Move: https://docs.microsoft.com//en-us/azure/virtual-machines/windows/move-vm

answer is correct. hart232 answer is from the azure portal.

Try redeploying your virtual machine, which will migrate it to a new Azure host. If you continue, the virtual machine will be restarted and you will lose any data on the temporary drive. While the redeployment is in progress, the virtual machine will be unavailable.

This will cause some downtime however. But it's better than waiting for maintenance to be completed on the host.