-
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
