AZ-104 Monitor and Maintain Azure Resources 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.

• ✓

  Autoscale rules in Azure Monitor

  Why this is correct

  Autoscale rules in Azure Monitor are the native mechanism for automatically adding or removing VM Scale Set instances based on metric thresholds such as CPU percentage, memory pressure, or a custom application metric. A rule defines a metric source, an operator (e.g., greater than), a threshold, and a duration, and when the condition holds, the scale action increments the instance count by a specified value. These rules can also include a cool-down period to prevent flapping, and schedule-based profiles allow time-window scaling. Because the autoscale engine is part of Azure Monitor, it is the correct component to implement metric-driven auto-instance provisioning for a scale set.

• ✗

  A Recovery Services vault policy

  Why it's wrong here

  A Recovery Services vault policy governs backup and restore operations, not compute capacity. It defines retention ranges, backup frequency, and point-in-time recovery settings for Azure VMs or other protected workloads. While it might indirectly help recover a failed instance, it has no relationship to the VM Scale Set's instance count or scaling logic. Therefore, configuring a Recovery Services vault policy would never cause instances to be added automatically in response to load.

  When this WOULD be correct

  When the question asks about configuring backup schedules or retention policies for Azure VMs, such as 'You need to ensure daily backups of a VM are retained for 30 days. Which feature should you configure?'

• ✗

  Boot diagnostics

  Why it's wrong here

  Boot diagnostics captures serial console output and screenshots of a VM's startup process to assist with troubleshooting boot failures. It stores those logs in a managed storage account and can be viewed via the Azure portal or Azure CLI. Although boot diagnostics are often enabled on VM Scale Set instances for operational visibility, they are a telemetry and debugging tool only. They contain no logic to evaluate metrics, trigger scale events, or alter the number of running instances, so they cannot satisfy the requirement to add instances automatically.

  When this WOULD be correct

  A question asks: 'You need to troubleshoot why a VM in a scale set fails to start. Which feature should you enable to capture boot errors?' Boot diagnostics would be the correct answer.

• ✗

  Azure Advisor only

  Why it's wrong here

  Azure Advisor is a recommendation service that analyzes resource configurations and usage patterns to suggest best practices for cost, performance, reliability, and security. For example, it might recommend enabling autoscale on a VM Scale Set or changing instance sizes, but it does not perform any actions on your behalf unless you manually accept and implement the recommendation. Advisory recommendations, even if followed, only lead to the creation or modification of an actual autoscale rule; Advisor alone never adds or removes instances. Thus, Azure Advisor cannot directly provide automatic instance scaling without the underlying Azure Monitor autoscale configuration.

  When this WOULD be correct

  A question asks: 'Which service provides cost optimization, security, and reliability recommendations for Azure resources?' In that case, Azure Advisor would be the correct answer.

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