Question 372 of 2,015
QoS ArchitectureeasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is Weighted Random Early Detection (WRED), the correct QoS mechanism for preventing congestion by dropping packets before a queue becomes full. WRED achieves this by monitoring the average queue depth and randomly dropping packets with a probability that increases as the queue grows, which proactively signals TCP senders to slow down before tail drop occurs. This prevents the global synchronization problem that plagues traditional drop-at-full approaches. On the ENCOR 350-401 exam, this concept tests your ability to distinguish congestion avoidance (WRED) from congestion management (like CBWFQ or PQ), which only act after the queue is full. A common trap is confusing WRED with policing or shaping—remember, WRED drops early to avoid the queue filling, not to enforce a rate limit. Memory tip: think "WRED = Weighted Random Early Drop" to recall it drops before the queue is full, using randomness and weighting to avoid synchronized TCP backoffs.

CCNP QoS Architecture Practice Question

This 350-401 practice question tests your understanding of qos architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which QoS mechanism is used to prevent congestion by dropping packets before a queue becomes full?

Question 1easymultiple choice
Study the full QoS explanation →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Weighted Random Early Detection (WRED)

Weighted Random Early Detection (WRED) is a congestion avoidance mechanism that proactively drops packets before a queue becomes full. By monitoring the average queue depth and dropping packets with a probability that increases as the queue depth grows, WRED signals TCP senders to reduce their transmission rate, thereby preventing tail drop and global synchronization. This differs from congestion management mechanisms like PQ or CBWFQ, which only act on packets after the queue is full.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Weighted Random Early Detection (WRED)

    Why this is correct

    WRED proactively drops packets to avoid tail drop and global synchronization.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Priority Queuing (PQ)

    Why it's wrong here

    PQ is a scheduling mechanism, not a congestion avoidance mechanism.

  • Class-Based Weighted Fair Queuing (CBWFQ)

    Why it's wrong here

    CBWFQ is a scheduling mechanism that guarantees bandwidth.

  • Tail Drop

    Why it's wrong here

    Tail drop drops packets only when the queue is full, not before.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco often tests the distinction between congestion management (queuing/scheduling) and congestion avoidance (drop policy), so the trap here is that candidates confuse mechanisms like CBWFQ or PQ (which manage queues after they form) with WRED (which prevents queues from filling up in the first place).

Detailed technical explanation

How to think about this question

WRED uses an exponentially weighted moving average (EWMA) to calculate the average queue depth, comparing it against minimum and maximum thresholds. When the average queue depth is between these thresholds, packets are dropped with a probability that increases linearly from 0 to the configured mark probability denominator (e.g., 1/10). This probabilistic dropping allows WRED to selectively drop packets from lower-priority traffic or specific DSCP/CoS values, providing differentiated drop behavior per class. In real-world deployments, WRED is often configured on core routers to avoid the performance degradation caused by tail drop and to maintain consistent TCP throughput.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the 350-401 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related 350-401 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 350-401 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 350-401 question test?

QoS Architecture — This question tests QoS Architecture — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Weighted Random Early Detection (WRED) — Weighted Random Early Detection (WRED) is a congestion avoidance mechanism that proactively drops packets before a queue becomes full. By monitoring the average queue depth and dropping packets with a probability that increases as the queue depth grows, WRED signals TCP senders to reduce their transmission rate, thereby preventing tail drop and global synchronization. This differs from congestion management mechanisms like PQ or CBWFQ, which only act on packets after the queue is full.

What should I do if I get this 350-401 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More 350-401 practice questions

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This 350-401 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-401 exam.