A hospital campus circuit stays full through the day, and QoS already marks clinical traffic ahead of bulk transfers. What should the capacity recommendation be?
Select an answer to reveal the explanation.
Short Explanation
You already have QoS correctly prioritizing clinical traffic, but the hospital circuit stays full through the day, so you need more capacity. Another alert, a renamed dashboard, or more tests collecting the same fullness data would leave the circuit unchanged.
Full Explanation
QoS is already placing clinical traffic ahead of bulk transfers, and the campus circuit stays full through the day. Scheduling cannot create capacity that the link does not have, so recommend more circuit capacity. Adding another alert that fires whenever this same circuit is full only notifies people of a condition the current view already shows. Renaming the campus dashboard so the full circuit is easier to spot changes the title, not the link. Deploying more tests that collect the same fullness data, without a topology, configuration, or QoS change, repeats the measurement and does not widen the circuit. Exam caveat: when the stem says the marking policy is already correct, recommend more circuit capacity rather than another alert, a renamed dashboard, or more tests of the same fullness. Practical check: review the class markings and interface utilization together, confirm clinical traffic is already preferred, and write the action as additional circuit capacity.