Question 780
An Azure Monitor metric alert for VM `vm-ops` evaluates every one minute (`Check every = 1 minute`) but uses a 15-minute `Lookback period` and Average aggregation of Percentage CPU. CPU briefly drops from 92% to 5% for one minute. An operator incorrectly expects the alert's next evaluation to use only the 5% CPU reading. Which configuration detail explains why the alert can remain above its threshold?
Explanation
Correct Answer
Metric alert evaluation frequency controls how often the service evaluates the condition. The lookback period independently defines the preceding interval and Average combines its samples, so a one-minute dip might not move the 15-minute result below threshold.
Incorrect Answers
Severity is notification and prioritization metadata. Altering it changes neither the time window over which CPU values are aggregated nor the numerical average used to determine threshold crossings.
Action groups govern what happens after an alert condition fires, such as emailing an on-call address. They do not change CPU measurement, the lookback interval or the aggregation calculation.
An Activity Log alert evaluates resource management events, not a time series of VM platform CPU metrics. Switching alert type discards the requested CPU condition instead of explaining the existing average.