Question 480
At a campus switch team configuring Junos egress queues, a Junos specialist investigates this scenario: An enterprise shapes a WAN uplink but class scheduling behaves unpredictably within the aggregate cap. The improvement must not starve business traffic. What verification result should the engineer expect?
Explanation
Correct Answer
For a campus switch team configuring Junos egress queues, the decisive evidence is: Aggregate throughput stays under the circuit limit while class queues meet their intended bandwidth shares. This validates the action: Configure the supported shaper and subordinate scheduler policy according to the actual forwarding hierarchy. Because: Hierarchical CoS policies coordinate parent traffic shaping with child class queues or scheduler allocation where supported. An unrelated successful test would not prove this specific issue is resolved.
Incorrect Answers
Junos packet-loss priority provides an additional attribute for drop-profile selection under queue pressure. The appropriate correction for the reported case is: Configure the supported shaper and subordinate scheduler policy according to the actual forwarding hierarchy.
Classification determines internal forwarding class while rewrite rules modify markings on outgoing packets. Fixing that different mechanism would not address the current root cause: Hierarchical CoS policies coordinate parent traffic shaping with child class queues or scheduler allocation where supported.
The ingress trust boundary decides whether external markings should be accepted or reclassified. Its verification is distinct from the reported condition: An enterprise shapes a WAN uplink but class scheduling behaves unpredictably within the aggregate cap. The improvement must not starve business traffic.