A hospital campus link runs full at the same hour every week, and an alert already pages for that fullness. What should the next deliverable be?
Select an answer to reveal the explanation.
Short Explanation
When the same bridge is jammed every Friday, another horn does not add a lane. You recommend a capacity or topology change for the hospital link that fills at a known hour each week. Another alert on that same fullness, a renamed dashboard tile, or one more test of the same utilization leaves the link unchanged.
Full Explanation
The hospital already knows the link is full at the same hour every week, and an alert already pages for that condition. The next deliverable is a capacity recommendation: more capacity on that link, or a topology change that moves the weekly load off it. Another alert on the same fullness pages twice for pain the team already detects. Detection is not a remedy, and a second rule does not make the hour less full. Renaming the dashboard tile changes a label. The underlying series still shows a full link, and a new name does not alter topology, configuration, or the amount of traffic the hour carries. Adding another test that collects the same utilization produces a second copy of evidence without a topology change, a configuration change, or a quality-of-service change. More of the same chart does not empty the link. Keep the existing alert as the notification, and hand leadership a capacity or topology recommendation aimed at that weekly hour. Exam caveat: when the pattern is already alerted and already repeating, the work product is a change to the network, not another notification. Operational check: show the weekly full hour from the existing data and attach a capacity or topology proposal that would remove that saturation.