A public health clinic receives a 1 Gbps Ethernet handoff but buys only a 200 Mbps CIR from the carrier. How should hierarchical QoS typically be applied?
Select an answer to reveal the explanation.
Short Explanation
The fiber can sprint at a gig, but you only paid for a 200 Mbps jog. A parent shaper caps you at CIR, and child policies still sort voice from bulk underneath—that is hierarchical QoS. Without the parent, your classes race a track the carrier will police for you.
Full Explanation
Sub-rate Ethernet requires the customer edge to shape to CIR so class-based policies see congestion at the purchased rate, not only at full line rate. Hierarchical QoS uses a parent shaper with child class policies for LLQ/CBWFQ actions. Relying solely on the carrier PE, or assuming line rate equals CIR, leaves local queues mismodeling the true bottleneck.