nerdexam
Cisco

400-007 · Question #112

Company XYZ is redesigning their QoS policy. Some of the applications used by the company are real- time applications. The QoS design must give these applications preference in terms of transmission.

The correct answer is C. low-latency queuing. Real-time applications require strict priority queuing to guarantee bounded latency and jitter. Low-Latency Queuing is the only listed mechanism that provides a dedicated strict-priority queue for time-sensitive traffic.

Designing Network Services

Question

Company XYZ is redesigning their QoS policy. Some of the applications used by the company are real- time applications. The QoS design must give these applications preference in terms of transmission. Which QoS strategy can be used to fulfill the requirement?

Options

  • Aweighted fair queuing
  • Bweighted random early detection
  • Clow-latency queuing
  • Dfirst-in first-out

How the community answered

(53 responses)
  • B
    2% (1)
  • C
    94% (50)
  • D
    4% (2)

Why each option

Real-time applications require strict priority queuing to guarantee bounded latency and jitter. Low-Latency Queuing is the only listed mechanism that provides a dedicated strict-priority queue for time-sensitive traffic.

Aweighted fair queuing

Weighted Fair Queuing distributes bandwidth proportionally among active flows but provides no strict priority queue, so real-time traffic still experiences variable and potentially high delay during congestion.

Bweighted random early detection

Weighted Random Early Detection is a congestion-avoidance tool that preemptively drops TCP segments to prevent queue saturation, but it does not prioritize or provide low-latency treatment for real-time traffic classes.

Clow-latency queuingCorrect

Low-Latency Queuing combines a strict Priority Queue with Class-Based Weighted Fair Queuing (CBWFQ), ensuring that packets placed in the priority class are always dequeued before any other class is served. This guarantees minimum delay and jitter for real-time traffic such as voice or video while still providing proportional bandwidth guarantees to all remaining traffic classes, making it the standard Cisco QoS strategy for latency-sensitive applications.

Dfirst-in first-out

First-In First-Out processes all packets in strict arrival order with no traffic classification or differentiation, offering no preferential treatment for delay-sensitive real-time applications.

Concept tested: Low-Latency Queuing priority for real-time traffic

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_plcshp/configuration/xe-16/qos-plcshp-xe-16-book/qos-plcshp-oview.html

Topics

#QoS#low-latency queuing#real-time traffic#LLQ

Community Discussion

No community discussion yet for this question.

Full 400-007 Practice