nerdexam
Cisco

352-001 · Question #484

You are asked to design a traffic policy to restrict traffic that leaves a customer site. Which technology should you recommend to enforce a bandwidth limit, inbound and outbound, on the service provi

The correct answer is A. traffic policing. Traffic policing is the correct SP-side mechanism to enforce bandwidth limits because it can be applied in both inbound and outbound directions on an interface, which traffic shaping cannot.

Designing Network Services

Question

You are asked to design a traffic policy to restrict traffic that leaves a customer site. Which technology should you recommend to enforce a bandwidth limit, inbound and outbound, on the service provider side?

Options

  • Atraffic policing
  • BWRED
  • CLLQ
  • Dtraffic shaping

How the community answered

(52 responses)
  • A
    88% (46)
  • B
    6% (3)
  • C
    4% (2)
  • D
    2% (1)

Why each option

Traffic policing is the correct SP-side mechanism to enforce bandwidth limits because it can be applied in both inbound and outbound directions on an interface, which traffic shaping cannot.

Atraffic policingCorrect

Traffic policing enforces a bandwidth limit by immediately dropping or re-marking packets that exceed the configured committed information rate or peak information rate, with no buffering. Critically, policing can be applied both inbound and outbound on a service provider interface, satisfying the requirement for bidirectional enforcement. This makes it the standard tool service providers use to enforce customer SLA bandwidth commitments on PE-facing ports.

BWRED

WRED is a congestion avoidance mechanism that probabilistically drops packets as queue depth increases but does not enforce a specific maximum bandwidth limit in either direction.

CLLQ

LLQ provides low-latency priority queuing for real-time traffic classes but is a scheduling mechanism, not a bandwidth cap, and does not enforce hard rate limits in both inbound and outbound directions.

Dtraffic shaping

Traffic shaping buffers excess packets to smooth output to a configured rate but can only be applied outbound on an interface, making it unable to enforce inbound bandwidth limits as required by the design.

Concept tested: Traffic policing for bidirectional SP bandwidth enforcement

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_plc/configuration/xe-16/qos-plc-xe-16-book/qos-plc-police-confrm.html

Topics

#traffic policing#QoS#bandwidth limiting#service provider

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice