CompTIA Cloud+ (CV0-004)OperationsEasy
A cloud engineer needs to configure proactive alerting for a critical application's web server fleet. The goal is to be notified if the average CPU utilization of the fleet exceeds 80% for more than 5 consecutive minutes, to allow time to scale out before performance degrades significantly. Which alerting configuration parameter is crucial for preventing 'alert fatigue' from transient spikes while ensuring timely notification of sustained issues?
- AEvaluation period (or duration)
- BMetric name
- CNotification channel
- DComparison operator
Show answer & explanationAnswer & explanation
Correct answer: A. Evaluation period (or duration)
The evaluation period (or duration) parameter specifies how long a condition must persist before an alert is triggered. Setting it to '5 consecutive minutes' ensures that only sustained high CPU, not transient spikes, generates an alert, thereby preventing alert fatigue and focusing on actual problems.
Why the other options are wrong
- B. Metric name (e.g., CPU Utilization) defines what is monitored, not how long the condition must persist.
- C. Notification channel (e.g., email, PagerDuty) defines where the alert goes, not when it triggers.
- D. Comparison operator (e.g., exceeds, less than) defines the threshold condition, not its duration.
Alerting Thresholds
Configurable values that define when a monitored metric's state is considered abnormal and should trigger an alert.
- Includes a metric, operator, value, and evaluation period.
- Proper configuration prevents alert fatigue.
- Should be set to be actionable and indicative of real issues.
Memory trick: An alert is triggered by a 'Metric' that 'Exceeds' a 'Value' for a 'Duration'.