The answer is that the Count threshold of 5 is the most likely cause, because the alert rule requires more than five data points exceeding 90% CPU within the evaluation window before it fires. This means even if CPU usage is sustained above 90%, the alert will not trigger unless the monitoring system collects at least six data points that meet the condition—if the sampling frequency is low or the high-usage period is brief, the count may never reach that threshold. On the Microsoft Azure Solutions Architect Expert AZ-305 exam, this scenario tests your understanding of how scheduled query alert logic differs from metric alerts, specifically that Count aggregation counts individual data points rather than measuring the overall trend. A common trap is assuming any sustained high value will fire the alert, but the threshold acts as a minimum occurrence requirement. Memory tip: think of it as a “bouncer” that only lets the alert through after five guests (data points) have already arrived.
AZ-305 Practice Question: Design identity, governance, and monitoring solutions
This AZ-305 practice question tests your understanding of design identity, governance, and monitoring solutions. 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.
Exhibit
Refer to the exhibit.
{
"type": "Microsoft.Insights/scheduledQueryRules",
"apiVersion": "2021-08-01",
"properties": {
"displayName": "High CPU Alert",
"severity": 2,
"enabled": true,
"scopes": ["/subscriptions/12345/resourceGroups/prod/providers/Microsoft.Compute/virtualMachines/vm1"],
"evaluationFrequency": "PT5M",
"windowSize": "PT15M",
"criteria": {
"allOf": [
{
"query": "Perf | where ObjectName == 'Processor' and CounterName == '% Processor Time' and InstanceName == '_Total' | where CounterValue > 90",
"timeAggregation": "Count",
"threshold": 5,
"operator": "GreaterThan"
}
]
},
"actions": {
"actionGroups": [
"/subscriptions/12345/resourceGroups/rg-alerts/providers/microsoft.insights/actionGroups/ag-email"
]
}
}
}
Refer to the exhibit. You deploy this Azure Monitor scheduled query rule to alert when CPU usage exceeds 90% for sustained periods. However, alerts are not firing even when the condition is met. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The threshold of 5 with 'Count' aggregation requires more than 5 data points above 90% in the window, which may not be happening.
Option D is correct because the alert rule uses a 'Count' aggregation with a threshold of 5, meaning the alert fires only when the number of data points exceeding 90% CPU within the evaluation window is greater than 5. If the sustained high CPU usage produces fewer than 5 such data points (e.g., due to a short burst or insufficient sampling), the condition is not met, and the alert will not fire. This is a common misconfiguration where the threshold value is set too high relative to the actual data point frequency.
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.
✗
The KQL query syntax is incorrect and returns no results.
Why it's wrong here
The query is syntactically correct.
✗
The action group is not configured with a valid email address.
Why it's wrong here
The action group may be valid; the issue is with the alert logic.
✗
The evaluation frequency is too short compared to the window size.
Why it's wrong here
This is a valid configuration.
✓
The threshold of 5 with 'Count' aggregation requires more than 5 data points above 90% in the window, which may not be happening.
Why this is correct
The alert condition is too strict; it requires >5 occurrences in 15 minutes.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Microsoft often tests the misconception that any sustained high metric value will trigger an alert, ignoring how the 'Count' aggregation and threshold value interact with the number of data points in the evaluation window.
Detailed technical explanation
How to think about this question
In Azure Monitor scheduled query rules, the 'Aggregation granularity' (window size) defines the time bucket over which data is aggregated, and the 'Frequency' defines how often the query runs. The 'Count' aggregation counts the number of samples within that window that exceed the threshold (90% CPU). For the alert to fire, the count must exceed the specified threshold (5). This is distinct from 'Average' or 'Maximum' aggregations, which compare a single computed value to the threshold. A real-world scenario is monitoring a VM that spikes to 95% CPU for 3 minutes but only generates 4 data points (e.g., with 1-minute sampling), so the alert with threshold 5 never fires, leading to missed incidents.
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
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-305 question in full detail.
Design identity, governance, and monitoring solutions — This question tests Design identity, governance, and monitoring solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The threshold of 5 with 'Count' aggregation requires more than 5 data points above 90% in the window, which may not be happening. — Option D is correct because the alert rule uses a 'Count' aggregation with a threshold of 5, meaning the alert fires only when the number of data points exceeding 90% CPU within the evaluation window is greater than 5. If the sustained high CPU usage produces fewer than 5 such data points (e.g., due to a short burst or insufficient sampling), the condition is not met, and the alert will not fire. This is a common misconfiguration where the threshold value is set too high relative to the actual data point frequency.
What should I do if I get this AZ-305 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
This AZ-305 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-305 exam.
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.
Sign in to join the discussion.