Option C is false. Traditional QoS can classify traffic and provide differentiated treatment for service categories such as voice, video, and ordinary data. It normally performs classification, marking, policing, shaping, congestion avoidance, and queue scheduling on an interface. This provides service-level differentiation but does not deliver sufficiently refined simultaneous management across multiple users and multiple applications.
Huawei’s material explicitly states that traditional QoS schedules traffic based on port bandwidth and can differentiate traffic according to service levels, but it is difficult to distinguish traffic by user. It also states that traditional QoS cannot manage and schedule traffic from multiple services and multiple users simultaneously.
HQoS addresses this limitation through hierarchical, multi-level queues. For example, a parent level can allocate bandwidth to departments, VPNs, sites, or users, while child queues prioritize applications such as voice, video, email, and best-effort traffic. Huawei describes HQoS as hierarchical scheduling that differentiates both services and users. Therefore, statements A, B, and D are correct, while statement C incorrectly attributes an HQoS capability to traditional QoS.
==================
