Based on queue usage, which of the following QoS-policies when combined will allow queue rates to be dynamically allocated? (Choose two)

Question

Options

• AThe slope-policy
• BThe SAP-ingress policy
• CThe network-queue policy
• DThe scheduler-policy
• EThe network-policy
• FThe WRED-policy
• GThe arbitrator-policy

• A
  3% (1)
• B
  45% (13)
• C
  7% (2)
• E
  14% (4)
• G
  31% (9)

Explanation

SAP-ingress (B) defines per-queue parameters - including committed information rate (CIR) and peak information rate (PIR) - at the service access point. Scheduler-policy (D) creates a virtual scheduler hierarchy that governs how unused bandwidth is redistributed among queues based on actual consumption. Together, they enable hierarchical QoS (H-QoS): when a queue isn't using its allocated rate, the scheduler dynamically reassigns that headroom to queues that need it - which is the definition of dynamic rate allocation.

The distractors fail because:

• A (slope-policy) and F (WRED-policy) control drop probability as queues fill - they manage congestion avoidance, not rate distribution.
• C (network-queue policy) applies to network-facing interfaces, not SAP/access queues, so it's the wrong scope.
• E (network-policy) is not a recognized standalone QoS policy type in this context.
• G (arbitrator-policy) exists in some H-QoS frameworks but does not itself drive dynamic rate allocation when paired with SAP-ingress.

Memory tip: Think "Service + Scheduler = Shared bandwidth." The SAP-ingress policy owns the queues; the scheduler-policy manages how they share the pipe dynamically. Both start with "S" and both must be present for dynamic allocation to work.

No community discussion yet for this question.