-
Hi Everyone,
Thank you for raising this and for sharing the detailed calculation. Destine, the understanding outlined in the post is correct.
For Azure VM vCPU quotas, a VM in the Stopped (Deallocated) state still counts toward the subscription’s vCPU quota. Deallocating the VM stops compute billing, but it does not release the vCPU quota assigned to that VM. Microsoft specifically notes that quota is calculated using the total number of cores in use from both allocated and deallocated VMs.
In this scenario, North Central US already has:
-
VM1: 4 vCPUs
-
VM2: 8 vCPUs, including its deallocated state
This means the existing regional usage is 12 of 15 vCPUs.
Since the new VMs are evaluated in the order listed, VM4 requires 2 vCPUs, increasing regional usage to 14 of 15 vCPUs. Therefore, VM4 can be created.
When VM5 is evaluated next, its additional 2 vCPUs would increase usage to 16 of 15, exceeding the Total Regional vCPU quota. Therefore, VM5 cannot be created.
Because VM5 is not successfully deployed, usage remains at 14 vCPUs. VM6 requires another 8 vCPUs, which would also exceed the 15-vCPU regional limit, so it cannot be created either.
Therefore, the correct answers are:
VM4 in North Central US: Yes
VM5 in North Central US: No
VM6 in North Central US: NoAzure enforces vCPU quotas at both the Total Regional vCPU level and the VM-family vCPU level. A new VM must stay within both limits for the deployment to succeed.
We appreciate the careful review and apologize for the confusion caused by the earlier version of the question. The question and explanation have been updated to make the quota calculation and the treatment of deallocated VMs clearer.
Thank you again for helping us improve our practice exams!
Regards,
Nikee @ Tutorials Dojo -
