A five-minute average CPU alarm misses brief, severe spikes. What is the relevant design tradeoff?

1. A longer average always detects every smaller spike more accurately.
2. Renaming the instance changes historical CPU values.
3. Aggregation interval and statistic affect sensitivity and noise.
4. CPU alarms use DNS TTL as their evaluation interval.