Which of the following QoS functions does the slope-policy perform?

Question

Options

• AClassification
• BMarking
• CQueuing
• DCongestion management
• EScheduling

• C
  5% (1)
• D
  95% (20)

Explanation

Slope-policy defines WRED (Weighted Random Early Detection) drop-probability curves - specifically, how aggressively packets are dropped as queue depth rises toward a threshold. This is a congestion management (congestion avoidance) function: it reacts to queue buildup by probabilistically discarding packets before the queue overflows, signaling senders to slow down.

Why the distractors are wrong:

• A (Classification) - Classification identifies and categorizes traffic (e.g., by DSCP/CoS); slope-policy has no role in identifying traffic types.
• B (Marking) - Marking rewrites QoS bits on packets; slope-policy never touches packet headers.
• C (Queuing) - Queuing assigns packets to specific queues; slope-policy doesn't decide which queue a packet enters.
• E (Scheduling) - Scheduling determines the order queues are serviced (e.g., strict priority, WFQ); slope-policy operates within a queue on drop behavior, not service order.

Memory tip: Think of the word slope - it's the rising curve of drop probability vs. queue depth. Anything that controls "how likely is a packet to be dropped as the queue fills?" = congestion management. If it were scheduling, it would be called something like queue-policy; if classification, it would match on headers.

No community discussion yet for this question.