Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

🚀 43% OFF AZ-104 & AWS CloudOps Reviewers

Find answers, ask questions, and connect with our
community around the world.

Home Forums Azure Clarification on AZ-104 vCPU Quota Question

  • Clarification on AZ-104 vCPU Quota Question

     Destine Pinkney updated 6 days, 23 hours ago 1 Member · 2 Posts
  • Destine Pinkney

    Member
    July 24, 2026 at 11:14 pm

    Hello Tutorials Dojo Team,

    I am reviewing one of the AZ-104 practice questions related to Azure VM vCPU quotas and wanted to confirm my understanding of the explanation.

    In the question, the existing North Central US VMs are:

    VM1: A4_v2, 4 vCPUs, North Central US, Running<br data-start=”329″ data-end=”332″> VM2: D8s_v3, 8 vCPUs, North Central US, Stopped (Deallocated)

    Based on Azure quota behavior, stopped/deallocated VMs can still count against vCPU quota, even though they do not incur compute charges while deallocated.

    So the current North Central US regional vCPU usage would be:

    4 + 8 = 12 of 15 vCPUs used

    The planned VMs are created in this order:

    VM4: A2m_v2, 2 vCPUs<br data-start=”710″ data-end=”713″> VM5: D2s_v3, 2 vCPUs<br data-start=”733″ data-end=”736″> VM6: A8_v2, 8 vCPUs

    After creating VM4:

    12 + 2 = 14 of 15 vCPUs used

    That leaves only 1 vCPU available.

    Therefore, the expected answers would be:

    VM4 in North Central US: Yes<br data-start=”917″ data-end=”920″> VM5 in North Central US: No<br data-start=”947″ data-end=”950″> VM6 in North Central US: No

    I wanted to confirm that this is the intended reasoning behind the answer explanation, specifically that stopped/deallocated VMs are still included when calculating vCPU quota.

    Thank you.

  • Destine Pinkney

    Member
    August 3, 2026 at 1:29 pm

    W for the team updating the question

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content