AZ-104 Deploy and Manage Azure Compute Practice Question
VM-App01 is responding slowly and appears to be on a degraded Azure host. You must keep the VM resource, keep its disks and NIC, and move it to fresh infrastructure before further troubleshooting. Which two actions can achieve that goal? Select two.
⚠ Common exam trap
It's easy for candidates to confuse 'Redeploy' with 'Delete and recreate' or think that stopping the VM is insufficient, but in Azure, stop/deallocate is the standard way to force a host migration while keeping the VM resource intact.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Redeploy the VM.
Redeploying the VM (Option A) moves the VM to a new Azure host node while preserving the VM resource, its disks, and NIC. This is the correct action because it resolves host-level degradation without deleting or recreating the VM. Stopping/deallocating the VM (Option D) releases the underlying hardware lease, which forces the VM to be placed on a new host when started again, also preserving the VM resource, disks, and NIC.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Redeploy the VM.
Why this is correct
Redeploying a VM is an Azure-specific recovery operation that releases the current host node and re-provisions the VM onto a new healthy node, while preserving the VM object, managed disks, NIC, and IP addresses. This is the most direct remediation when the underlying physical host is suspected of causing performance degradation, because a simple restart keeps you on the same problematic host. Azure's redeploy API performs a controlled shutdown, migrates the VM's state, and boots it on fresh infrastructure, so it is the correct first step for host-related health issues.
- ✗
Delete the VM and recreate it from the OS disk.
Why it's wrong here
Deleting a VM and attempting to recreate it from its OS disk is a destructive manual process that removes the VM resource, its NIC, public IP, and availability/extensions configuration; during the delete, the attached managed OS disk is typically retained only if explicitly kept, and reassociating it to a new VM requires re-creating all network and role settings from scratch. This is far more risky and time-consuming than redeploy or deallocate, and it unnecessarily exposes your workload to misconfiguration or accidental data loss. It does not address the underlying host health concern in a controlled way and should be avoided for a simple host-level performance issue.
When this WOULD be correct
When the goal is to recover a VM from a failed OS disk by creating a new VM using the existing OS disk (e.g., after accidental deletion or disk corruption), and you are allowed to lose the original VM resource and NIC.
- ✗
Capture the VM into a generalized image.
Why it's wrong here
Capturing a generalized image is a template-creation operation: it runs a generalization process (such as Sysprep for Windows or `waagent -deprovision` for Linux) that strips the VM of unique identifiers and user-specific configuration, then saves the disks as an image. This is inappropriate for troubleshooting a degraded VM because it converts the running system into a reusable template rather than restoring it to a healthy state, and the original VM cannot continue operation after generalization. It is a heavy, irreversible step that changes the VM's identity and requires creating new VMs from the image, so it does not address an unhealthy host.
When this WOULD be correct
When you need to create a reusable, standardized image from a VM to deploy multiple identical VMs, and you are willing to lose the original VM's identity and specific configurations.
- ✓
Stop/deallocate the VM.
Why this is correct
Stopping and deallocating a VM powers off the instance and explicitly releases the compute lease on the current host, causing Azure to return the VM's resources to the pool while keeping the VM record, OS/managed disks, and NIC intact. When you start the VM again, Azure places it on a new host (potentially after a delay), which can resolve host-level performance issues. However, this requires an explicit start action and may result in losing dynamic public IP reassignment if not using a static IP, making redeploy a more efficient one-step recovery.
- ✗
Convert the VM to an availability set.
Why it's wrong here
Converting a VM to an availability set is not an operational recovery action and is not even directly supported for an existing VM—you must create the availability set separately and then add the VM to it, which physically moves the VM into a different fault/update domain but does not necessarily trigger a new host placement or resolve current degradation. An availability set is a deployment topology that ensures VMs are placed on different physical infrastructure for high availability, not a troubleshooting tool for a single unhealthy VM. Attempting this would require a full recreate or a complex reconfiguration with downtime, making it completely unsuitable for immediate performance triage.
When this WOULD be correct
You need to ensure high availability for a critical VM by grouping it with other VMs in an availability set to protect against rack-level failures within an Azure datacenter.
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.
✓Redeploy the VM.Correct answer▾
Why this is correct
Redeploying a VM is an Azure-specific recovery operation that releases the current host node and re-provisions the VM onto a new healthy node, while preserving the VM object, managed disks, NIC, and IP addresses. This is the most direct remediation when the underlying physical host is suspected of causing performance degradation, because a simple restart keeps you on the same problematic host. Azure's redeploy API performs a controlled shutdown, migrates the VM's state, and boots it on fresh infrastructure, so it is the correct first step for host-related health issues.
✗Delete the VM and recreate it from the OS disk.Wrong answer — click to see why▾
Why this is wrong here
Deleting the VM and recreating it from the OS disk does not preserve the original VM resource, disks, and NIC as a single unit; it creates a new VM with a new resource ID, potentially losing the original VM's configuration and NIC association.
★ When this WOULD be the correct answer
When the goal is to recover a VM from a failed OS disk by creating a new VM using the existing OS disk (e.g., after accidental deletion or disk corruption), and you are allowed to lose the original VM resource and NIC.
Why candidates choose this
Candidates may think recreating from the OS disk is a way to move the VM to new infrastructure while keeping the disk, but they overlook that the original VM resource and NIC are not preserved, and the process is more disruptive than redeploying.
✗Capture the VM into a generalized image.Wrong answer — click to see why▾
Why this is wrong here
Capturing the VM into a generalized image removes machine-specific configurations (like SID and hostname) and is intended for creating reusable images, not for moving a degraded VM to fresh infrastructure while keeping its disks and NIC intact.
★ When this WOULD be the correct answer
When you need to create a reusable, standardized image from a VM to deploy multiple identical VMs, and you are willing to lose the original VM's identity and specific configurations.
Why candidates choose this
Candidates may confuse 'capture' with 'move' or think that creating an image is a way to preserve the VM state, not realizing that generalization resets the VM and does not retain the original disks and NIC for direct reuse.
✗Convert the VM to an availability set.Wrong answer — click to see why▾
Why this is wrong here
Converting a VM to an availability set does not move it to fresh infrastructure; it only adds high availability by grouping VMs, but the VM remains on the same degraded host until redeployed or stopped/deallocated.
★ When this WOULD be the correct answer
You need to ensure high availability for a critical VM by grouping it with other VMs in an availability set to protect against rack-level failures within an Azure datacenter.
Why candidates choose this
Candidates may think that adding the VM to an availability set forces Azure to move it to a different physical host, but availability sets only affect placement for future VMs, not existing ones.
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?”
Visual reference
Go deeper
Related to this question
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.