AZ-104 Deploy and Manage Azure Compute Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Resize

  Why it's wrong here

  Resize changes the VM's SKU (e.g., CPU, RAM, storage capacity) and may require the VM to be stopped and restarted, potentially on a different host if the target size is unavailable on the current node. However, resizing is primarily a scaling operation intended to adjust compute resources, not a troubleshooting step to move a VM away from an unhealthy host. The new host selection is based on capacity and SKU availability, not on health, so resizing does not guarantee a move to a healthy host and is inappropriate for host-level fault isolation.

  When this WOULD be correct

  When the question asks to increase or decrease the VM's performance specifications (e.g., from Standard_D2s_v3 to Standard_D4s_v3) without changing the underlying host or disks.

• ✓

  Redeploy

  Why this is correct

  Redeploy is the correct Azure VM troubleshooting action when the host itself is unhealthy or experiencing connectivity issues (e.g., RDP/SSH failures, intermittent hangs). The Azure fabric shuts down the VM, moves it to a new physical node within the same region, and then restarts it while preserving the OS disk, data disks, virtual networks, and public/internal IP addresses. This operation is specifically designed to resolve host-level problems without deleting or recreating the VM, making it the proper choice for relocating to a new host.

• ✗

  Capture

  Why it's wrong here

  Capture is used to create an image (generalized or specialized) from an existing virtual machine, which can later be used to provision new VMs. It does not relocate the running VM to a different host; instead, it copies or snapshots the disks and records VM configuration, often requiring the source VM to be stopped and, for generalized images, sysprep'd. Since the original VM remains on its current host (or may be deleted after capture), this process does not achieve the goal of moving that specific VM to a new host for troubleshooting.

  When this WOULD be correct

  When you need to create a reusable image from a generalized VM to deploy multiple identical VMs, such as for scaling out a web application, you would use Capture.

• ✗

  Reapply

  Why it's wrong here

  Reapply (az vm reapply) refreshes the VM's model on the underlying compute node by re-applying the configuration that was originally set, which can help repair issues such as stuck provisioning states or VM state corruption. It does not move the VM to a different physical host; rather, it operates on the same host, re-provisioning the VM's settings and potentially resolving some platform-level inconsistencies. Because the VM stays on the same node, reapply cannot address problems caused by a faulty or degraded host, so it is not an alternative to redeploy.

  When this WOULD be correct

  Reapply would be correct when a VM's extensions or configuration are in a failed state and you need to reapply the current configuration without redeploying or restarting the VM, such as after a failed extension installation.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question