Question 110
At a financial services network enforcing trusted DSCP markings, a Junos specialist investigates this scenario: A downstream user workstation marks backup traffic as high priority and competes with voice in the protected queue. Classification and downstream remarking must not be confused. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For a financial services network enforcing trusted DSCP markings, the governing mechanism is: The ingress trust boundary decides whether external markings should be accepted or reclassified. It explains the reported symptom: A downstream user workstation marks backup traffic as high priority and competes with voice in the protected queue. The intended response is: Apply a controlled classifier or policer for untrusted ports while trusting only authorized phone or uplink markings. Verification: The workstation's spoofed expedited marking is reset and voice retains the intended priority.
Incorrect Answers
Shaping buffers excess eligible traffic to pace transmission whereas policing marks or drops traffic that exceeds a limit. This alternative mechanism does not match the current fault.
Junos rewrite rules map internal forwarding class and loss-priority information to outgoing packet codepoints. Fixing that different mechanism would not address the current root cause: the ingress trust boundary decides whether external markings should be accepted or reclassified.
Hierarchical CoS policies coordinate parent traffic shaping with child class queues or scheduler allocation where supported. Its verification is distinct from the reported condition: A downstream user workstation marks backup traffic as high priority and competes with voice in the protected queue. Classification and downstream remarking must not be confused.