Review Set 1, question 20

[Marco De Simone]

Hello, i think the answer is wrong because the count of vcpus has no sense. Also, i think answer is based on the order and if you do test more times, answer order will change (example first question is about VM6 but in answer it says that you first created VM4 and then you have no more space). Thank you!

[Irene-TutorialsDojo]

Hello Marco De Simone,

Thank you for raising this concern and for carefully reviewing the vCPU calculations.

We’ve reviewed the scenario based on Azure’s current virtual machine quota rules, and the evaluation follows how Azure enforces vCPU quotas, which consider only allocated (running) virtual machines when calculating vCPU usage; stopped (deallocated) VMs do not consume vCPU quota.

Azure enforces two limits during VM creation: the total regional vCPU quota and the VM size family quota, and each VM request is evaluated sequentially in the order specified in the question. In this case, VM4 and VM5 both fit within the remaining regional and family quotas in North Central US, while VM6 cannot be created because its 8 vCPUs would exceed the remaining regional quota after the earlier deployments.

This behavior is consistent and deterministic and does not change across test runs.

We appreciate your feedback, as it helps ensure our practice questions remain accurate and aligned with real Azure behavior.

Cheers,

Irene @ Tutorials Dojo

[toxic]

The Microsoft documentation on VM Quota states that “Quota is calculated based on the total number of cores in use both allocated and deallocated.” https://learn.microsoft.com/en-us/azure/virtual-machines/quotas?tabs=cli

[Irene-TutorialsDojo]

Hello toxic,

Thank you for pointing this out.

To clarify, Azure enforces vCPU quotas during VM creation by validating that the requested VM does not exceed either the Total Regional vCPU quota or the VM size family quota. While the documentation notes that quota usage reporting can include both allocated and deallocated cores, stopped (deallocated) virtual machines do not block new VM deployments, as they do not consume vCPUs required for VM creation.

Each VM request is evaluated sequentially in the order defined in the scenario. In this case, VM4 and VM5 fit within the remaining quotas in the North Central US region, while VM6 cannot be created because its vCPU requirement would exceed the remaining regional quota after the earlier deployments. This behavior aligns with Azure’s documented VM quota enforcement model.

Cheers,

Irene @ Tutorials Dojo

[toxic]

Thank you for your reply. But I’m still a bit perplexed.

Can you please direct me to the documentation that clarifies this? I can still read this on the ms learn docs link I posted above: “Anytime a new VM is deployed the vCPUs for the VM must not exceed the vCPU quota for the VM size family or the total regional vCPU quota. If you exceed either of those quotas, the VM deployment won’t be allowed.” and then, again “Quota is calculated based on the total number of cores in use both allocated and deallocated”.

I’m currently unable to test this myself in the portal.

[Irene-TutorialsDojo]

Hello toxic,

Thank you for your patience and for citing the documentation. After further review, you are correct. The Microsoft documentation states that “Quota is calculated based on the total number of cores in use both allocated and deallocated.” This means VM2, despite being stopped (deallocated), still counts toward the quota.

With VM1 (4 vCPUs) and VM2 (8 vCPUs) both counted, the current usage in North Central US is 12 vCPUs, leaving 3 available. Following the sequential order: VM4 (2 vCPUs) succeeds, bringing the total to 14. VM5 (2 vCPUs) would push the total to 16, exceeding the 15 vCPU limit, so it would fail.

My previous responses contained an error regarding how deallocated VMs are handled. We will update this question, and the changes will reflect on the portal soon.

Best regards,

Irene @ Tutorials Dojo

[toxic]

Hello,

Thank you for reviewing!