AZ-104 Deploy and Manage Azure Compute Practice Question
A virtual machine scale set must increase instance count when average CPU exceeds 75 percent and decrease when it stays below 30 percent. What Azure feature should you configure?
⚠ Common exam trap
Many candidates confuse Autoscale with Availability zones, thinking that distributing instances across zones automatically handles scaling, but zones only provide redundancy, not dynamic capacity adjustment based on load.
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
✓
Autoscale settings
Autoscale settings are the correct feature because they allow you to define scale-out and scale-in rules based on performance metrics like average CPU percentage. In this scenario, you would configure a scale-out rule to increase the instance count when average CPU exceeds 75% and a scale-in rule to decrease it when CPU stays below 30%.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Availability zones
Why it's wrong here
Availability zones partition a region into physically separate locations with independent power, cooling, and networking, primarily to protect applications from data center failures. While deploying a VM scale set across availability zones improves resiliency and can continue running during a zone outage, availability zones themselves contain no logic to monitor CPU load or other performance counters, and they never modify the instance count in response to changing demand.
When this WOULD be correct
A question asks: 'You need to ensure that your virtual machine scale set remains available during a regional outage. Which feature should you configure?'
- ✓
Autoscale settings
Why this is correct
Autoscale settings are the built-in Azure Monitor feature that directly controls the instance count of a Virtual Machine Scale Set by evaluating performance metrics such as average CPU utilization, memory pressure, or custom application metrics. When a metric breach occurs (for example, sustained CPU above a threshold for a defined duration), Autoscale logically triggers a scale-out action to add instances, or a scale-in action when demand drops, making it the only mechanism among these options that performs runtime workload-based capacity adjustments.
- ✗
Azure Policy
Why it's wrong here
Azure Policy is a governance service that enforces organizational standards and compliance rules across resources, such as restricting VM sizes, requiring specific tags, or ensuring encryption is enabled. Policy evaluation occurs during resource creation, update, and compliance scans, but Azure Policy cannot attach to a virtual machine scale set's metrics stream or trigger an autoscale operation based on workload conditions, so it is irrelevant to increasing instance count dynamically.
When this WOULD be correct
An exam question asks: 'You need to ensure that all virtual machines in a subscription are deployed only in approved regions. Which Azure feature should you use?' In that case, Azure Policy would be correct to enforce location compliance.
- ✗
Update management
Why it's wrong here
Update management (part of Azure Automation) is designed to assess and install operating system and software updates on VMs according to a configured schedule or on-demand, ensuring patches are applied consistently across instances. It does not monitor performance metrics like CPU or memory, and it has no capability to launch new instances or reduce them based on load; its purpose is patching lifecycle management, not capacity scaling.
When this WOULD be correct
A question asks: 'You need to ensure all VMs in a scale set are automatically patched with the latest security updates. Which Azure feature should you configure?' In that case, Update Management would be correct.
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.
✓Autoscale settingsCorrect answer▾
Why this is correct
Autoscale settings are the built-in Azure Monitor feature that directly controls the instance count of a Virtual Machine Scale Set by evaluating performance metrics such as average CPU utilization, memory pressure, or custom application metrics. When a metric breach occurs (for example, sustained CPU above a threshold for a defined duration), Autoscale logically triggers a scale-out action to add instances, or a scale-in action when demand drops, making it the only mechanism among these options that performs runtime workload-based capacity adjustments.
✗Availability zonesWrong answer — click to see why▾
Why this is wrong here
Availability zones are used to protect applications and data from datacenter failures by distributing resources across multiple zones, not for scaling based on CPU metrics.
★ When this WOULD be the correct answer
A question asks: 'You need to ensure that your virtual machine scale set remains available during a regional outage. Which feature should you configure?'
Why candidates choose this
Candidates may confuse high availability features with autoscaling, thinking that distributing instances across zones also handles performance-based scaling.
✗Azure PolicyWrong answer — click to see why▾
Why this is wrong here
Azure Policy is used to enforce organizational standards and assess compliance, not to automatically scale resources based on performance metrics like CPU usage.
★ When this WOULD be the correct answer
An exam question asks: 'You need to ensure that all virtual machines in a subscription are deployed only in approved regions. Which Azure feature should you use?' In that case, Azure Policy would be correct to enforce location compliance.
Why candidates choose this
Candidates may confuse Azure Policy with autoscaling because both involve rules and conditions, but Policy focuses on governance, not dynamic scaling.
✗Update managementWrong answer — click to see why▾
Why this is wrong here
Update management in Azure (e.g., Azure Automation Update Management) is used to manage OS updates and patches for VMs, not to scale instances based on CPU metrics. Autoscale settings are required for scaling rules.
★ When this WOULD be the correct answer
A question asks: 'You need to ensure all VMs in a scale set are automatically patched with the latest security updates. Which Azure feature should you configure?' In that case, Update Management would be correct.
Why candidates choose this
Candidates may confuse 'update management' with scaling updates or think it can adjust instance counts, but it is solely for patching and compliance.
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.