The answer is to deallocate the VM first, then retry the resize. This works because a running VM is pinned to a specific cluster of physical hosts in an Azure datacenter, and if that cluster lacks capacity for the target size, the resize fails. Deallocating the VM releases its underlying hardware lease, removing it from that cluster entirely; when you then attempt the resize, Azure can place the VM onto any cluster with available capacity for the desired size. On the AZ-104 exam, this scenario tests your understanding of VM lifecycle states and the difference between stopping (which retains the cluster assignment) and deallocating (which frees it). A common trap is thinking a simple stop or restart will help, but only deallocation breaks the cluster pinning. Remember the memory tip: “Stop keeps the spot, deallocate drops the dock.”
AZ-104 Deploy and Manage Azure Compute Practice Question
This AZ-104 practice question tests your understanding of deploy and manage azure compute. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You need to resize a VM to a larger size, but Azure says the target size is not available while the VM is running. What should you do first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Deallocate the VM, then retry the resize.
When a VM is running, Azure may not have the target VM size available in the cluster hosting the VM. Deallocating the VM releases the underlying hardware resources and removes the VM from its current cluster, allowing Azure to select a new cluster that supports the desired size. After deallocation, the resize operation can succeed because the VM is no longer pinned to a specific host or cluster.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Delete the VM and recreate it from the image.
Why it's wrong here
Recreating the VM is unnecessary when a simple deallocation and resize can solve the issue.
✓
Deallocate the VM, then retry the resize.
Why this is correct
Deallocating releases the VM from the current host cluster and often allows Azure to place it on hardware that supports the new size.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Attach a new data disk first.
Why it's wrong here
Adding a disk does not affect whether the target compute size is available.
✗
Create an availability set for the VM.
Why it's wrong here
An availability set changes placement resilience, but it does not make a running size resize succeed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think they must delete and recreate the VM or perform complex workarounds, when the simple and correct first step is to deallocate the VM to free it from its current cluster constraint.
Detailed technical explanation
How to think about this question
Under the hood, each Azure VM is hosted on a specific cluster of physical servers that support a set of VM sizes. When you resize a running VM, Azure attempts to keep the VM on the same cluster, but if the target size is not available there, the operation fails. Deallocating the VM (stopping it with 'Stop-Deallocate' or via the portal) releases the lease on the underlying hardware, allowing the VM to be placed on a different cluster that supports the desired size during the next start or resize. This behavior is tied to Azure Resource Manager's orchestration and the physical constraints of host clusters.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Deploy and Manage Azure Compute — This question tests Deploy and Manage Azure Compute — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Deallocate the VM, then retry the resize. — When a VM is running, Azure may not have the target VM size available in the cluster hosting the VM. Deallocating the VM releases the underlying hardware resources and removes the VM from its current cluster, allowing Azure to select a new cluster that supports the desired size. After deallocation, the resize operation can succeed because the VM is no longer pinned to a specific host or cluster.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.