On event days at a stadium, WAN throughput falls below the level the operations team treats as normal, and they want a page when that drop returns. Which alert fits?
Select an answer to reveal the explanation.
Short Explanation
When the fuel gauge drops under the mark you treat as normal, the gauge is what should call you. You want a throughput alert so event-day volume pages you when it falls off that level. A tablet CPU alert, a wall chart with no rule, or next week's capacity notes will not page you during the event.
Full Explanation
WAN throughput on event days is falling below the level the operations team treats as normal, so the fitting page is a throughput alert on that drop. The team asked to be notified when the low-throughput condition returns, and throughput is the network condition they are watching. An end-user CPU alert on point-of-sale tablets in the concourse measures devices in the stands and the shops. A busy or idle tablet does not tell you that WAN throughput left its normal level, and it can page on a day when throughput is fine. A throughput chart on the operations wall can show the same drop, but with no alert rule attached to it the chart does not page anyone when the line falls. A capacity project that studies the drop next week may lead to a design change later, yet it does not page anyone during the event, so it misses the live operational need. On the exam, a throughput problem gets a throughput alert; a picture of throughput without a rule is not yet that alert. In production, confirm the throughput alert pages while event-day volume is below the level the team calls normal and clears when throughput recovers, without waiting for a capacity review.