Question 360
At a branch router serving several application classes, a Junos specialist investigates this scenario: Users report poor application performance but staff rely solely on interface utilization and ignore per-queue drops. The team must validate packet drops by actual queue statistics. Which precaution should be checked before committing the change?
Explanation
Correct Answer
For a branch router serving several application classes, the relevant safeguard is: Do not infer an absence of congestion from a low five-minute average utilization value alone. It matters while implementing: Inspect Junos interface queue statistics and correlate drops with traffic class and times. The fault involves: Per-queue counters reveal forwarding class use, transmission and discard behavior during congestion. The required acceptance result remains: A representative load shows which class drops packets and the verified correction reduces them.
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: Do not infer an absence of congestion from a low five-minute average utilization value alone.
A scheduler can prioritize selected latency-sensitive queues over other queues when the interface is congested. Fixing that different mechanism would not address the current root cause: per-queue counters reveal forwarding class use, transmission and discard behavior during congestion.
Classification determines internal forwarding class while rewrite rules modify markings on outgoing packets. Its verification is distinct from the reported condition: Users report poor application performance but staff rely solely on interface utilization and ignore per-queue drops. The team must validate packet drops by actual queue statistics.