Question 1,069 of 1,170
Monitor and Maintain Azure ResourcesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is Autoscale rules in Azure Monitor. This is the correct feature because it enables you to define metric-based conditions that automatically adjust the number of VMSS instances, such as adding instances when average CPU usage exceeds 75% and removing them when it drops below 30%, with a cool-down period to prevent flapping. On the AZ-104 exam, this scenario tests your understanding of native Azure scaling mechanisms versus alternatives like manual scaling or Azure Automation runbooks; a common trap is confusing autoscale rules with VMSS manual scaling or Azure Logic Apps. Remember that Azure Monitor is the centralized service for metrics and alerts, and autoscale rules are configured directly on the VMSS resource under the “Scaling” blade. Memory tip: think “CPU triggers, Monitor rules” — Azure Monitor is the brain that reads the CPU metric and tells the scale set to grow or shrink.

AZ-104 Monitor and Maintain Azure Resources Practice Question

This AZ-104 practice question tests your understanding of monitor and maintain azure resources. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A Virtual Machine Scale Set must add instances automatically when average CPU usage is above 75 percent and remove instances when CPU drops below 30 percent. Which feature should you configure?

Question 1mediummultiple choice
Full question →

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 rules in Azure Monitor

Autoscale rules in Azure Monitor allow you to define conditions for automatically scaling a Virtual Machine Scale Set (VMSS) based on metrics like average CPU usage. You can set a scale-out rule to add instances when CPU exceeds 75% and a scale-in rule to remove instances when CPU drops below 30%, with a cool-down period to prevent flapping. This is the native Azure feature designed for such metric-based auto-scaling scenarios.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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

    This directly implements metric-based scaling logic for the VM Scale Set.

    Related concept

    Read the scenario before looking for a memorised answer.

  • A Recovery Services vault policy

    Why it's wrong here

    Backup policy does not change instance count.

  • Boot diagnostics

    Why it's wrong here

    Boot diagnostics helps troubleshoot startup issues only.

  • Azure Advisor only

    Why it's wrong here

    Advisor may recommend changes but does not perform autoscaling.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse Azure Advisor (which gives recommendations) with the actual implementation of autoscale rules, or mistakenly think Recovery Services vault policies or boot diagnostics are involved in scaling decisions.

Detailed technical explanation

How to think about this question

Autoscale rules in Azure Monitor use a 'scale condition' that includes a metric source (e.g., Percentage CPU), operator (greater than or less than), threshold (75% or 30%), duration (e.g., 10 minutes), and a scaling action (increase or decrease instance count by a specific number or percentage). The cool-down period (default 5 minutes) prevents rapid oscillation by waiting before another scaling operation can occur. Under the hood, Azure Monitor's autoscale engine evaluates metrics every minute and triggers actions based on the aggregated data over the specified duration.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-104 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-104 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Monitor and Maintain Azure Resources — This question tests Monitor and Maintain Azure Resources — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Autoscale rules in Azure Monitor — Autoscale rules in Azure Monitor allow you to define conditions for automatically scaling a Virtual Machine Scale Set (VMSS) based on metrics like average CPU usage. You can set a scale-out rule to add instances when CPU exceeds 75% and a scale-in rule to remove instances when CPU drops below 30%, with a cool-down period to prevent flapping. This is the native Azure feature designed for such metric-based auto-scaling scenarios.

What should I do if I get this AZ-104 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-104 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.