Question 670
For this Cisco ENSLD design case: A guest Internet service must never exceed a fixed traffic ceiling and excess packets may be dropped or remarked. Which technical principle BEST explains the design decision?
Explanation
Correct Answer
Policing measures traffic against a rate profile and can drop or remark excess traffic rather than delaying it in a shaping queue. The correct engineering response is: Use an appropriate traffic policer at the guest policy boundary. The observable check is: Measured guest traffic stays within the configured policer allowance under sustained load.
Incorrect Answers
Policing measures traffic against a rate profile and can drop or remark excess traffic rather than delaying it in a shaping queue. The offered choice instead concerns a different principle: End-to-end QoS behavior depends on consistent class mapping across each administrative transport domain. Those technical conditions are not interchangeable.
Policing measures traffic against a rate profile and can drop or remark excess traffic rather than delaying it in a shaping queue. The offered choice instead concerns a different principle: Traffic shaping buffers and schedules excess packets to smooth bursts instead of immediately discarding all excess. Those technical conditions are not interchangeable.
Policing measures traffic against a rate profile and can drop or remark excess traffic rather than delaying it in a shaping queue. The offered choice instead concerns a different principle: CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. Those technical conditions are not interchangeable.