Question 690
The network architecture board discusses the following: During a predeployment review for a hospital regional backbone, the team discovers this design gap: bulk transactions and routine web data need minimum bandwidth shares during congestion but neither is real-time voice. An approval gate requires both a measurable acceptance check and a durable prevention control. Which technical principle BEST explains the design decision?
Explanation
Correct Answer
CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. The correct engineering response is: Use class-based weighted fair queuing with planned per-class bandwidth allocations. The observable check is: Congestion tests show each class receives at least its configured effective share where the scheduler applies. The hospital regional backbone acceptance record also captures this result.
Incorrect Answers
CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. The offered choice instead concerns a different principle: a priority queue reduces latency for a tightly controlled real-time class but must be bounded to avoid starving others. Those technical conditions are not interchangeable.
CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. The offered choice instead concerns a different principle: an untrusted endpoint can mark arbitrary DSCP values unless network policy validates and normalizes them. Those technical conditions are not interchangeable.
CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. The offered choice instead concerns a different principle: Weighted random early detection can drop selected packets before total queue exhaustion to help reduce synchronized TCP congestion. Those technical conditions are not interchangeable.