mediummultiple choiceObjective-mapped

Exhibit

Alert rule name: CPUSpikeAlert
Scope: /subscriptions/11111111-1111-1111-1111-111111111111/resourceGroups/RG-App/providers/Microsoft.Compute/virtualMachines/VM1
Condition: Average Percentage CPU > 80
Window size: 5 minutes
Evaluation frequency: 1 minute
Action group: Ops-Email
Recent alert history: 6 alerts between 23:10 and 23:25 during patching

Based on the exhibit, the operations team says the alert is too noisy because short CPU spikes after nightly maintenance trigger notifications. They want an alert only when VM1's average CPU stays above 80% for at least 10 minutes. What should you change?

Question 1mediummultiple choice
Full question →

Based on the exhibit, the operations team says the alert is too noisy because short CPU spikes after nightly maintenance trigger notifications. They want an alert only when VM1's average CPU stays above 80% for at least 10 minutes. What should you change?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Lower the threshold to 70% so the alert becomes less sensitive.

Reducing the threshold makes the alert fire sooner, not later. It does not prevent brief spikes from triggering notifications, so it does not solve the noise problem.

B

Best answer

Increase the window size to 10 minutes and keep the evaluation frequency at 1 minute.

A longer evaluation window requires CPU to remain elevated over a longer period before the rule triggers. That directly addresses short maintenance spikes while still checking frequently enough to detect sustained pressure.

C

Distractor review

Replace the metric alert with a Log Analytics query alert against the activity log.

CPU usage is a platform metric, so a metric alert is the simplest and most direct choice. An activity log query would not be the normal way to evaluate VM CPU behavior.

D

Distractor review

Move the alert scope from the VM to the resource group.

Changing scope broadens what resources are watched, but it does not change how long CPU must stay high. The issue is threshold duration, not target scope.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Increase the window size to 10 minutes and keep the evaluation frequency at 1 minute. — The problem is caused by short-lived spikes, so the alert needs a longer time window before it evaluates the condition as true. Increasing the window to 10 minutes means the average CPU must remain above 80% across that longer interval, which filters out temporary maintenance activity. Keeping the evaluation frequency at 1 minute still provides timely checks without making the rule noisy. Why others are wrong: Lowering the threshold would make the alert more sensitive, not less. Switching to an activity log alert is the wrong signal type because CPU is a metric, not a control-plane event. Expanding the scope to the resource group only changes what is monitored; it does not change the alert timing behavior that is causing the false notifications.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.