Which Quality of Service (QoS) mechanism allows for the creation of multiple levels of QoS policy, providing a more granular degree of traffic management?

Question

Options

• APolicing
• BH-QoS
• CCongestion avoidance
• DDual Policy

• A
  3% (1)
• B
  89% (31)
• C
  6% (2)
• D
  3% (1)

Explanation

H-QoS (Hierarchical QoS) is correct because it enables the creation of multiple, nested levels of QoS policies - typically a parent policy and one or more child policies - allowing administrators to apply traffic management rules at both an aggregate level and a more granular, per-service or per-user level simultaneously.

Policing (A) is incorrect because it only enforces bandwidth limits by dropping or marking traffic that exceeds a defined rate; it does not provide a hierarchical or multi-level policy structure. Congestion avoidance (C) is incorrect because mechanisms like WRED (Weighted Random Early Detection) are designed to proactively drop packets before a queue fills up, not to create layered policy structures. Dual Policy (D) is a distractor and not a standard, recognized QoS mechanism in the context of hierarchical traffic management.

Memory Tip: Think of the "H" in H-QoS as standing for "Hierarchical" = "Layers," just like a company org chart with a manager (parent policy) overseeing employees (child policies) - multiple levels working together for finer control.

No community discussion yet for this question.