nerdexam
Microsoft

AZ-104 · Question #74

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…

The correct answer is B. No. B (No) is correct because moving a VM to a different resource group is purely a metadata/organizational operation - it does not change the physical host or underlying infrastructure where the VM runs, so it does nothing to escape scheduled maintenance. Why A is wrong: Changing…

Submitted by hans_de· Mar 4, 2026Deploy and manage Azure compute resources

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 Overview blade, you move the virtual machine to a different resource group. Does this meet the goal?

Options

  • AYes
  • BNo

How the community answered

(41 responses)
  • A
    24% (10)
  • B
    76% (31)

Explanation

B (No) is correct because moving a VM to a different resource group is purely a metadata/organizational operation - it does not change the physical host or underlying infrastructure where the VM runs, so it does nothing to escape scheduled maintenance.

Why A is wrong: Changing the resource group has zero effect on where the VM is physically hosted in Azure's datacenter. The VM stays on the same host hardware regardless of which resource group it belongs to.

What you should do instead: To immediately move a VM to a different physical host, you use Redeploy from the VM's blade (which migrates the VM to new infrastructure within Azure), or use Availability Zone migration if applicable. For planned maintenance, you can also use the Maintenance Control feature or simply deallocate and reallocate the VM, which typically lands it on different hardware.

Memory tip: Think of resource groups as folders on your computer - moving a file between folders doesn't move it to a different hard drive. "Move = metadata only; Redeploy = actual host change."

Topics

#Virtual Machines#VM Operations#Azure Maintenance#Resource Groups

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-104 Practice