DRAG DROP -
You have an availability set named AS1 that contains three virtual machines named VM1, VM2, and VM3.
You attempt to reconfigure VM1 to use a larger size. The operation fails and you receive an allocation failure message.
You need to ensure that the resize operation succeeds.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Step 1: Stop VM1, VM, and VM3.
If the VM you wish to resize is part of an availability set, then you must stop all VMs in the availability set before changing the size of any VM in the availability set.
The reason all VMs in the availability set must be stopped before performing the resize operation to a size that requires different hardware is that all running VMs in the availability set must be using the same physical hardware cluster. Therefore, if a change of physical hardware cluster is required to change the VM size then all VMs must be first stopped and then restarted one-by-one to a different physical hardware clusters.
Step 2: Resize VM1.
Step 3: Start VM1, VM2, and VM3.
References:
https://azure.microsoft.com/es-es/blog/resize-virtual-machines/
It's a correct answer
Yes, I agree
Yes, answer is correct. https://docs.microsoft.com/en-us/azure/virtual-machines/windows/resize-vm#use-powershell-to-resize-a-vm-in-an-availability-set
Yes, answer is correct. https://docs.microsoft.com/en-us/azure/virtual-machines/windows/resize-vm#use-powershell-to-resize-a-vm-in-an-availability-set
Stop Vm1,Vm2,vm3 Resize Vm1 Start Vm1 check link: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure The cluster need to be updated to support new vm size. So only Vm1 should be started after resize. then vm2 and vm3
guys this is the correct answer please check link https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure
resizing VM1 will reboot it so step 3 should be Start VM2 and VM3. VM1 is already in running state after resizing.
you are right. it seems this certificate makes the people very confused.
I just tried it. Resizing the Stopped VM doesn't make it start. Don't spread false information.
wrong, machine wont restart unless you start after resizing
The anwser is wrong - re-read the question: "You need to ensure that the resize operation succeeds." => So the last step is to start VM1 (only!), because of two reasons: 1. It addresses the requirement. No need for VM2 or VM3, you must ENSURE resizing. 2. It is officially MS's solution: "After all VMs stop, select the first VM, and then click Start. This step makes sure that a new allocation attempt is run and that a new cluster can be selected that has sufficient capacity." Source: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure Ofcourse after VM1 has been resized and started, later you will also startup VM2 and VM3, but not in the same time as VM1 as the psyical/cluster allocation must be done before that.
If the VM can be part of a different availability set, create a VM in a different availability set (in the same region). This new VM can then be added to the same virtual network. Stop (deallocate) all VMs in the same availability set, then restart each one. To stop: Click Resource groups > [your resource group] > Resources > [your availability set] > Virtual Machines > [your virtual machine] > Stop. After all VMs stop, select the first VM, and then click Start. This step makes sure that a new allocation attempt is run and that a new cluster can be selected that has sufficient capacity. 1st 2 options are correct and 3rd Option "Start VM1". https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure
Then Start VM2, VM3. So the given answer is right. :)
The last answer should be "start VM 1" Stop (deallocate) all VMs in the same availability set, then restart each one. To stop: Click Resource groups > [your resource group] > Resources > [your availability set] > Virtual Machines > [your virtual machine] > Stop. After all VMs stop, select the first VM, and then click Start. This step makes sure that a new allocation attempt is run and that a new cluster can be selected that has sufficient capacity https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure
The main answer is correct. You have to stop all VMs in the availability set. Then, resize the VM and then start all of the VMs. Here is a link showing the way to do it using Powershell. Specifically states these steps if you scroll down to Use PowerShell to resize a VM in an availability set https://docs.microsoft.com/en-us/azure/virtual-machines/windows/resize-vm
Given answer appears correct. https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/allocation-failure "then restart each one"
Given answer is correct. https://docs.microsoft.com/en-us/azure/virtual-machines/windows/resize-vm
Lot's of blogs etc. Best Azure Docs reference is the reference to Allocation Failure here: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/restart-resize-error-troubleshooting#issue-error-when-starting-a-stopped-vm
It's a correct answer
last step should be start VM1 even I thought we have to restart all the VMs at once but no we have to first start the resized VM and then we can start the other two. https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/restart-resize-error-troubleshooting#issue-error-when-resizing-an-existing-vm
Given answer is correct