nerdexam
Cisco

352-001 · Question #759

Refer to the exhibit. You are designing this network to support voice communication between software and hardware endpoints. To ensure quality, the decision is to implement a DiffServ QoS model with…

The correct answer is C. Implement a LLQ on routers. LLQ on routers is the correct DiffServ priority queuing mechanism for voice because WAN router egress interfaces are the primary congestion points where voice delay and jitter must be controlled.

Design Considerations

Question

Refer to the exhibit. You are designing this network to support voice communication between software and hardware endpoints. To ensure quality, the decision is to implement a DiffServ QoS model with priority queuing. Which admission criteria option do you recommend?

Exhibit

352-001 question #759 exhibit

Options

  • APolice voice traffic on the switches
  • BImplement a LLQ on switches
  • CImplement a LLQ on routers
  • DImplement active queue management on the routers only
  • EMonitor packet drops on the router to identify possible oversubscription

How the community answered

(37 responses)
  • A
    3% (1)
  • B
    8% (3)
  • C
    81% (30)
  • D
    5% (2)
  • E
    3% (1)

Why each option

LLQ on routers is the correct DiffServ priority queuing mechanism for voice because WAN router egress interfaces are the primary congestion points where voice delay and jitter must be controlled.

APolice voice traffic on the switches

Policing voice on switches enforces a rate limit and drops or re-marks excess traffic but provides no priority queuing guarantee, so voice packets still compete with data during congestion.

BImplement a LLQ on switches

LLQ is a router IOS queuing feature specific to WAN interfaces; Layer 2 switches implement QoS through CoS-based or DSCP-based scheduling mechanisms and do not support LLQ.

CImplement a LLQ on routersCorrect

LLQ (Low Latency Queuing) combines a strict priority queue with CBWFQ on router WAN interfaces, ensuring voice traffic marked EF DSCP is always dequeued first and never delayed behind data traffic, meeting the sub-150ms one-way delay and sub-30ms jitter requirements of VoIP.

DImplement active queue management on the routers only

Active queue management such as WRED manages congestion by probabilistically dropping data traffic early but does not create a strict priority queue and is not appropriate for delay-sensitive voice traffic.

EMonitor packet drops on the router to identify possible oversubscription

Monitoring packet drops is a reactive diagnostic activity, not an admission control mechanism, and does not prevent voice quality degradation from occurring in the first place.

Concept tested: DiffServ LLQ priority queuing for VoIP on WAN routers

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

Topics

#DiffServ#LLQ#voice QoS#priority queuing

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice