Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam

Exam AZ-104 topic 1 question 16 discussion

Actual exam question from Microsoft's AZ-104

Question #: 16
Topic #: 1

Your company has three virtual machines (VMs) that are included in an availability set.
You try to resize one of the VMs, which returns an allocation failure message.
It is imperative that the VM is resized.
Which of the following actions should you take?

A. You should only stop one of the VMs.
B. You should stop two of the VMs.
C. You should stop all three VMs.
D. You should remove the necessary VM from the availability set.

Show Suggested Answer

Suggested Answer: C 🗳️

by CLagnuts at June 30, 2021, 5:39 p.m.

Comments

Submit Cancel

CLagnuts

Highly Voted 4 years ago

C. Looks Correct Stop all the VMs in the availability set. Click Resource groups > your resource group > Resources > your availability set > Virtual Machines > your virtual machine > Stop. After all the VMs stop, resize the desired VM to a larger size. Select the resized VM and click Start, and then start each of the stopped VMs.

upvoted 68 times

jackdryan

2 years, 4 months ago

C is correct

upvoted 4 times

Nathan12345

6 months, 1 week ago

C is corrrect https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/restart-resize-error-troubleshooting#issue-error-when-resizing-an-existing-vm

upvoted 4 times

...

MrJR

Highly Voted 3 years, 9 months ago

This question is deprecated. I tested and I was able to change the size of a VM, which is in an availability set with two other VMs, without stopping any other VM. With the three VMs up you can resize any of them.

upvoted 39 times

CommanderBigMac

2 years, 5 months ago

All this means is that the change in hardware was supported by whatever the availability set was running on, not that the question is depricated. If your VM(s) are deployed using the Resource Manager (ARM) deployment model and you need to change to a size which requires different hardware then you can resize VMs by first stopping your VM, selecting a new VM size and then restarting the VM. 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.

upvoted 35 times

...

vombat186

3 months, 3 weeks ago

This has nothing to do deprecation. Its an issue with the underlying cluster that hosts the VMs, it may not have capacity or doesn't support the VM size you want to change to. So just because it worked in your case, does not mean it will always work in the future.

upvoted 1 times

...

drainuzzo

3 years, 7 months ago

But the question reported: "You try to resize one of the VMs, which returns an allocation failure message." so you can only stop all the 3 vms

upvoted 28 times

...

nicolase

Most Recent 3 weeks, 5 days ago

Selected Answer: A

First stop vm

upvoted 1 times

...

Zcw001

4 weeks ago

Selected Answer: C

if you don't stop all three VMs in the availability set, you might encounter an allocation failure when trying to resize one of the VMs. This happens because the Azure infrastructure needs to ensure that the new VM size can be accommodated within the existing hardware constraints of the availability set.

upvoted 1 times

...

NicoVick

1 month, 2 weeks ago

Selected Answer: C

c is good answer

upvoted 1 times

...

tangocqui010

3 months ago

Selected Answer: A

To attach a data disk from one Azure VM to another with minimal downtime, the first action you should take is to Stop the VM that includes the data disk. This is necessary because you cannot detach a data disk from a running VM. Once the VM is stopped, you can then detach the data disk and attach it to the other VM.

upvoted 1 times

...

Nepton

4 months, 1 week ago

Selected Answer: C

In this case, to resolve the allocation failure when resizing a VM in an availability set, you would need to stop all the VMs in the availability set to ensure that there are no resource conflicts or issues that prevent the VM from being resized.

upvoted 1 times

...

emakid

4 months, 2 weeks ago

Selected Answer: C

Retry the request using a smaller VM size. If the size of the requested VM cannot be changed： Stop all the VMs in the availability set. Click Resource groups > your resource group > Resources > your availability set > Virtual Machines > your virtual machine > Stop. After all the VMs stop, resize the desired VM to a larger size. Select the resized VM and click Start, and then start each of the stopped VMs. Source: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/restart-resize-error-troubleshooting#issue-error-when-resizing-an-existing-vm

upvoted 2 times

...

Sama5100

6 months, 3 weeks ago

Selected Answer: C

In the event of an allocation failure, we should stop all three VMs in the availability set https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/restart-resize-error-troubleshooting#issue-error-when-resizing-an-existing-vm

upvoted 4 times

...

SHAHIN_STA

7 months, 1 week ago

Selected Answer: D

**Answer: D. You should remove the necessary VM from the availability set.** **Explanation:** When a VM is part of an **availability set**, resizing the VM can sometimes fail if there aren't sufficient resources available in the underlying hardware for the requested VM size. In this case, the correct action would be to **remove the VM from the availability set**, which allows resizing without being constrained by the availability set's resource allocation. After resizing, you can add the VM back into the availability set. Simply stopping the VMs (Options A, B, and C) doesn't resolve the allocation failure, as the issue lies with the available resources in the set, not with whether the VMs are running or stopped.

upvoted 2 times

58b2872

6 months, 3 weeks ago

GPT hhahahahahah

upvoted 1 times

...

RajeshwaranM

6 months, 3 weeks ago

Can I replicate the issue on my end? I really wanna test this scenario

upvoted 1 times

...

MaDota

7 months, 1 week ago

Selected Answer: C

most important part of the question is: ".....which returns an allocation failure message" In this situation Stopping all the VMs in the availability set helps free up enough resources to allow the resizing operation to succeed

upvoted 1 times

...

FritsB

7 months, 3 weeks ago

Selected Answer: A

Just tested it in my lab. I created an availability set, added 3 VM's. Stopped VM1 and resized it and started it again. No issues.

upvoted 5 times

58b2872

6 months, 3 weeks ago

Because you have enough hardware resources, bro, no allocation failure message...

upvoted 1 times

...

RajeshwaranM

6 months, 3 weeks ago

Did you get the allocation failure while you increased space for the VM?

upvoted 1 times

...

JPA210

8 months, 2 weeks ago

Selected Answer: A

Check down Mr JR answer.

upvoted 1 times

JPA210

8 months, 2 weeks ago

Commanderbigmac and drainuzzo gave a very good reply to him, so I change my vote to C.

upvoted 1 times

...

Ayb_FNZ

8 months, 3 weeks ago

Answer is C. We have to understand the allocation failure error. When we create an availability set, all the mVMs are created within the same data center in specific racks (depends on the fault and update domains). When we resize, ARM looks for enough capacity to allocate 3 times the new size. If there is no enough compute capacity, it send s back an error. We have to stop all the VMs (aka deallocate) so they can be allocated on another rack where capacity is available for the 3 VMs (aka 3 times the new desired size)

upvoted 4 times

...

3c5adce

1 year, 2 months ago

C. You should stop all three VMs. Stopping all VMs in the availability set can help with the reallocation of resources, making it possible to resize the VM by potentially moving it to a different hardware cluster where the desired VM size is available.

upvoted 1 times

...

18c2076

1 year, 3 months ago

C is correct. Key context here is the allocation failure “When you try to start a stopped Azure Virtual Machine (VM), or resize an existing Azure VM, the common error you encounter is an allocation failure. This error results when the cluster or region either does not have resources available or cannot support the requested VM size” https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/restart-resize-error-troubleshooting

upvoted 1 times

...

abhikeshu

1 year, 4 months ago

Selected Answer: D

Option 3 suggests stopping all three VMs. While stopping all VMs might temporarily free up resources within the availability set, it is not the most targeted or efficient solution to address the allocation failure during VM resizing. Additionally, stopping all VMs would disrupt the availability of services running on those VMs, which may not be acceptable in a production environment. Removing only the necessary VM from the availability set, as suggested in option D, allows for a more surgical approach. It addresses the allocation failure specifically for the VM that needs resizing while minimizing disruption to other VMs in the availability set. Once the necessary VM is resized, it can be added back to the availability set to restore its high availability and redundancy features. This approach is more targeted and focused on resolving the specific issue at hand without unnecessary disruption to other resources.

upvoted 2 times

TheFivePips

11 months, 3 weeks ago

I was wondering this too. Chat GPT said this: If you want to add the VM back into the availability set after resizing, this is not directly supported. You would need to delete the VM (keeping its disks) and recreate it within the availability set, which involves downtime and additional configuration.

upvoted 1 times

TheFivePips

11 months, 3 weeks ago

Further explanation: Virtual machines (VMs) must be created within an availability set from the beginning; you cannot add an existing VM to an availability set. This is because the placement of VMs within an availability set is determined at the time of their creation to ensure they are distributed across multiple fault and update domains to provide high availability.

upvoted 1 times

...

Load full discussion...