Does Moving VM1 to Another Subscription Move It to a New Host?
Short answer
B Moving VM1 to another subscription does not move it to a different host; you must redeploy the VM to satisfy the maintenance requirement.
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure virtual machine named VM1. VM1 was deployed by using a custom Azure Resource Manager template named ARM1.json. You receive a notification that VM1 will be affected by maintenance. You need to move VM1 to a different host immediately. Solution: From the resource group blade, move VM1 to another subscription. Does this meet the goal?
Key Takeaways
This question tests whether a subscription move relocates a VM to a different host; the common trap is confusing resource management moves with host-level redeployment.
Azure VM host maintenance requires a redeploy to move the VM to a new node; moving VM1 to another subscription does not change its host. This page explains why the proposed solution fails (B) and what action actually meets the goal.
Common mistake: Choosing Yes (A) because a subscription move sounds like a migration; in Azure, moving a resource between subscriptions preserves the existing host and does not perform a redeploy.
Expert Analysis
Why the Answer Is Correct
Moving VM1 to another subscription is an Azure resource move that changes its management scope (resource group, subscription, RBAC, policy) but not the underlying physical host. The VM continues running on the same Azure node, so it will still be affected by the maintenance event. To immediately move VM1 to a different host, you must use the Redeploy operation (VM > Help > Redeploy + Reapply, or az vm redeploy), which stops, moves, and restarts the VM on a new node. Therefore the solution does not meet the goal, so "No" (B) is correct.
Why the Other Options Are Wrong
Option A ("Yes") is wrong because it assumes any move operation changes the host. Subscription moves are purely administrative and do not trigger a host-level relocation. Even stop/deallocate followed by start does not guarantee a new host, as noted in the comments; only a redeploy explicitly instructs Azure to move the VM to a different node. Since the scenario demands an immediate host change, the subscription move leaves the maintenance impact unresolved.
Community Comment Notes
As kejo2 explained, the practical fix is to "Go to the virtual machine > scroll down to Help section and click Redeploy + Reapply". Dankho reinforced that "redeploy will do it" and warned that "stopping (deallocating) and then starting the VM does not perform a redeployment", so it keeps the VM on the same host. paula_ simply summed up the consensus with "You need to redeploy". Together these learner notes confirm that the proposed subscription move is not the right operation.
Official Reference
Exam Strategy
When a maintenance event requires moving a VM to a new host, look for Redeploy—not a subscription move. Resource moves only change management boundaries, so they never satisfy host-level relocation requirements on AZ-104.
Frequently Asked Questions
Why doesn't moving VM1 to another subscription change its host?
A subscription move only changes the resource's management boundary and ARM template scope; the VM keeps running on its current Azure host, so it does not trigger a redeployment.
What is the correct way to move VM1 to a different host?
Use the Redeploy option in the VM's Help section (or az vm redeploy), which stops, moves, and restarts the VM on a new Azure node.
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.
From public community threads 3
-
kejo2 👍 4Go to the virtual machine > scroll down to Help section and click Redeploy + Reapply
-
Dankho 👍 2 Answered BYup, redeploy will do it. Also, stopping (deallocating) and then starting the VM does not perform a redeployment. This action simply stops the VM and releases the resources associated with it, but the VM remains on the same host.
-
paula_ 👍 2 Answered BYou need to redeploy
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →