nerdexam
Cisco

400-007 · Question #87

Which two application requirements are mandatory tor traffic to receive proper treatment when placed in the priority queue? (Choose two.)

The correct answer is A. small transactions (HTTP-like behavior) D. intolerance to jitter. Traffic placed in the LLQ priority queue must consist of small, predictable transactions to avoid queue monopolization, and must be intolerant to jitter since strict priority scheduling is specifically designed to eliminate queuing delay variation.

Designing Network Services

Question

Which two application requirements are mandatory tor traffic to receive proper treatment when placed in the priority queue? (Choose two.)

Options

  • Asmall transactions (HTTP-like behavior)
  • BWRED drop treatment
  • Ctolerance to packet loss
  • Dintolerance to jitter
  • ETCP-based application

How the community answered

(52 responses)
  • A
    87% (45)
  • B
    4% (2)
  • C
    8% (4)
  • E
    2% (1)

Why each option

Traffic placed in the LLQ priority queue must consist of small, predictable transactions to avoid queue monopolization, and must be intolerant to jitter since strict priority scheduling is specifically designed to eliminate queuing delay variation.

Asmall transactions (HTTP-like behavior)Correct

Small, consistent transactions (similar to fixed-size voice packets) are required so that the priority queue does not starve other queues by monopolizing bandwidth - the policer on the priority queue depends on predictable, low-volume bursts to function correctly.

BWRED drop treatment

WRED (Weighted Random Early Detection) is a congestion avoidance mechanism applied to non-priority queues; traffic in the strict priority queue is never subject to WRED drops.

Ctolerance to packet loss

Traffic in the priority queue should be intolerant to packet loss, not tolerant - loss-tolerant traffic does not require the special treatment of strict priority scheduling and should be placed in lower queues.

Dintolerance to jitterCorrect

Intolerance to jitter is the defining requirement for priority queue placement, because LLQ provides strict priority scheduling that services the PQ before all other queues, minimizing queuing delay and delay variation for real-time applications such as VoIP.

ETCP-based application

TCP-based applications are poor candidates for the priority queue because TCP retransmission, windowing, and slow-start mechanisms interact poorly with strict priority scheduling; UDP real-time traffic such as VoIP is the intended use case.

Concept tested: LLQ priority queue traffic suitability requirements

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

Topics

#QoS#priority queue#jitter tolerance#traffic classification

Community Discussion

No community discussion yet for this question.

Full 400-007 Practice