AZ-104 Monitor and Maintain Azure Resources Practice Question
A Windows VM fails shortly after startup when a custom extension runs, and the administrator cannot use RDP to inspect the machine. The goal is to see what happened during boot and confirm whether the failure occurred before the guest OS finished loading. Which two features should be used first? Select two.
⚠ Common exam trap
A common mix-up: candidates choose managed disk snapshots or availability sets, thinking they can restore or inspect the VM state, but these do not provide the real-time, pre-OS boot logs needed to diagnose a startup failure before the guest OS finishes loading.
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
✓
Boot diagnostics
Boot diagnostics captures serial console output and screenshots of the VM during the boot process, allowing you to see if the OS failed to load before the guest OS finished. Azure Serial Console provides text-based, keyboard-focused access to the VM even when RDP is unavailable, enabling you to inspect boot logs and interact with the OS during startup. Together, they let you determine whether the custom extension failure occurred before or after the OS fully loaded.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Boot diagnostics
Why this is correct
Boot diagnostics captures the VM's serial console output and screenshots during the boot process, storing them in an Azure storage account for later review. For a VM that fails shortly after startup when a custom extension runs, these artifacts can reveal kernel panics, missing drivers, or a stuck boot sequence that prevents the extension from executing. By viewing the serial log, you can pinpoint the exact stage of boot failure, making it the first-line diagnostic tool for such scenarios.
- ✓
Azure Serial Console
Why this is correct
Azure Serial Console provides an interactive, text-based connection to the VM's serial port through the Azure portal, functioning even when RDP or SSH is unavailable. It lets you see the full boot log in real time and run administrative commands (e.g., `dmesg`, `systemctl`) to inspect why a custom extension is failing or hanging during startup. This live access is more powerful than static screenshots because you can test diagnostics and remediate issues directly from within the boot environment.
- ✗
Availability set
Why it's wrong here
An availability set is a placement configuration that spreads VMs across fault domains and update domains to maximize availability during hardware failures and planned maintenance. It does not produce logs, capture screenshots, or provide any visibility into a VM's boot sequence or extension execution. Therefore, adding a failing VM to an availability set (or checking its existing availability set membership) would not help diagnose or resolve the startup failure.
When this WOULD be correct
A question asks: 'You need to ensure that two VMs hosting a critical application remain available during planned maintenance. Which feature should you use?' In that scenario, an availability set is the correct answer to guarantee uptime by placing VMs in separate update and fault domains.
- ✗
Managed disk snapshots
Why it's wrong here
A managed disk snapshot is a read-only, point-in-time copy of a VM's OS or data disk that can be used to restore the VM or create a new one for disaster recovery. While a snapshot taken after the failure might capture the on-disk state, it cannot show you the boot-time interaction between the hypervisor, the OS kernel, and the custom extension—the very sequence that failed. Diagnostics requires runtime logs and console output, not a static disk image, so snapshots are not a valid troubleshooting tool here.
When this WOULD be correct
A managed disk snapshot would be correct if the question asked for a point-in-time backup of a VM's OS disk before applying a critical update, or to create a new VM from a known good state for recovery purposes.
- ✗
Azure Monitor autoscale
Why it's wrong here
Azure Monitor autoscale automatically adjusts the number of instances in a virtual machine scale set based on metric thresholds like CPU utilization or queue length. It is a scaling control that affects instance count, not a monitoring or diagnostic feature, and it has no access to boot logs, serial consoles, or extension logs for a specific VM. For a single VM that fails after startup, autoscale configuration is irrelevant because it neither captures boot failures nor influences how extensions run.
When this WOULD be correct
A web application experiences intermittent performance degradation during peak hours. You need to automatically increase the number of VM instances when CPU usage exceeds 80% and decrease when it drops below 30% to maintain performance and optimize cost. Azure Monitor autoscale would be the correct feature to configure.
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.
✓Boot diagnosticsCorrect answer▾
Why this is correct
Boot diagnostics captures the VM's serial console output and screenshots during the boot process, storing them in an Azure storage account for later review. For a VM that fails shortly after startup when a custom extension runs, these artifacts can reveal kernel panics, missing drivers, or a stuck boot sequence that prevents the extension from executing. By viewing the serial log, you can pinpoint the exact stage of boot failure, making it the first-line diagnostic tool for such scenarios.
✗Availability setWrong answer — click to see why▾
Why this is wrong here
An availability set provides high availability for VMs by distributing them across fault domains, but it does not help diagnose boot failures or inspect boot logs. The question requires features to see what happened during boot, which availability set cannot provide.
★ When this WOULD be the correct answer
A question asks: 'You need to ensure that two VMs hosting a critical application remain available during planned maintenance. Which feature should you use?' In that scenario, an availability set is the correct answer to guarantee uptime by placing VMs in separate update and fault domains.
Why candidates choose this
Candidates may confuse high availability features with diagnostic tools, thinking that an availability set can help recover or inspect a failed VM, but it only ensures redundancy, not troubleshooting capability.
✗Managed disk snapshotsWrong answer — click to see why▾
Why this is wrong here
Managed disk snapshots are used for backup or creating new disks, not for real-time boot troubleshooting. They cannot show boot logs or allow interactive access to diagnose a VM that fails before the OS loads.
★ When this WOULD be the correct answer
A managed disk snapshot would be correct if the question asked for a point-in-time backup of a VM's OS disk before applying a critical update, or to create a new VM from a known good state for recovery purposes.
Why candidates choose this
Candidates may think snapshots can be used to analyze the disk contents offline to find boot errors, but this is inefficient and not the intended first step; boot diagnostics and serial console are designed for this exact scenario.
✗Azure Monitor autoscaleWrong answer — click to see why▾
Why this is wrong here
Azure Monitor autoscale is used to automatically scale resources (like VMSS) based on demand, not to diagnose boot failures or inspect OS-level issues. It cannot help see what happened during boot or confirm failure timing.
★ When this WOULD be the correct answer
A web application experiences intermittent performance degradation during peak hours. You need to automatically increase the number of VM instances when CPU usage exceeds 80% and decrease when it drops below 30% to maintain performance and optimize cost. Azure Monitor autoscale would be the correct feature to configure.
Why candidates choose this
Candidates may think 'Azure Monitor' implies monitoring and diagnostics, and assume autoscale can help with boot issues, confusing scaling with troubleshooting.
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
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.