On event days a stadium uplink sits full, ticket sales slow, and the charts already show the circuit is saturated. More synthetic tests will not widen that circuit. What should the team recommend?
Select an answer to reveal the explanation.
Short Explanation
You do not buy a second thermometer when the one in your hand already says the pot is boiling over. The stadium charts already show a full circuit on event days, so the useful recommendation is more capacity. The trap is another alert, a renamed dashboard, or more synthetic tests that leave the circuit the same width.
Full Explanation
The saturation is already visible on event days, and ticket sales slow while that uplink is full. A capacity recommendation uses that evidence and asks for more circuit capacity. Adding another alert that fires on the same full circuit only pages people about a condition they can already see. Renaming the event-day dashboard so the full uplink stands out changes a label and leaves the pipe the same size. Adding synthetic tests that gather more of the same saturation data, without a topology, configuration, or QoS change, produces another copy of the chart that already says the circuit is full. Extra probes do not add bandwidth. Exam caveat: when the question says the data already show the constraint, the deliverable is the change that relieves it, not another detector for the same pain. Operational check: pair the event-day utilization chart with a written capacity action, and confirm the proposal adds circuit capacity rather than only another alert, a dashboard rename, or more synthetic tests.