Question 470
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A strict-priority queue carries sustained bulk traffic and starves a lower-priority control or business queue during peak hours. Which operational control would best prevent a recurrence of this exact failure mode?
- Test both trusted and untrusted DSCP patterns at every ingress boundary.
- Run worst-case saturation tests to reveal queue starvation.
- Validate control adjacency stability under full data-plane link utilization.
- Test aggregate oversubscription and isolated subscriber saturation scenarios.
Explanation
Correct Answer
B:Run worst-case saturation tests to reveal queue starvation. The control limits repetition of the described root condition: Unbounded strict-priority traffic can dominate an egress interface and deprive other classes of service. During audits, confirm: The lower class receives the planned service during high-priority saturation after limiting the dominant class.
Incorrect Answers
A:Test both trusted and untrusted DSCP patterns at every ingress boundary. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Untrusted DSCP markings. A behavior-aggregate classifier trusts header markings whereas an ingress multifield classifier can enforce policy based on additional packet fields. In this scenario, however, the distinguishing issue is Strict priority starvation and the confirming observation is: The lower class receives the planned service during high-priority saturation after limiting the dominant class.
C:Validate control adjacency stability under full data-plane link utilization. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Network control queue. Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. In this scenario, however, the distinguishing issue is Strict priority starvation and the confirming observation is: The lower class receives the planned service during high-priority saturation after limiting the dominant class.
D:Test aggregate oversubscription and isolated subscriber saturation scenarios. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Hierarchical subscriber QoS. Hierarchical CoS can apply scheduling and shaping at multiple levels to allocate shared physical capacity and logical service rates. In this scenario, however, the distinguishing issue is Strict priority starvation and the confirming observation is: The lower class receives the planned service during high-priority saturation after limiting the dominant class.
Question 471
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An interface starts discarding packets only after its queue fully fills, producing bursty loss even though a planned RED profile should drop earlier. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Separate output-queue drop counters from ingress policer exceed statistics and classify test flows.
- Correlate queue occupancy, peak burst size and scheduler buffer allocation.
- Inspect the scheduler's configured drop-profile map and packet-loss-priority thresholds.
- Inspect classifier results, forwarding-class-to-queue bindings and effective egress interface configuration.
Explanation
Correct Answer
C:Inspect the scheduler's configured drop-profile map and packet-loss-priority thresholds. This check examines the decisive condition for RED drop profile before any unrelated changes are made. The underlying mechanism is: Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion. The confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Incorrect Answers
A:Separate output-queue drop counters from ingress policer exceed statistics and classify test flows. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
B:Correlate queue occupancy, peak burst size and scheduler buffer allocation. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
D:Inspect classifier results, forwarding-class-to-queue bindings and effective egress interface configuration. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Question 472
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: An interface starts discarding packets only after its queue fully fills, producing bursty loss even though a planned RED profile should drop earlier. Which routing or service mechanism best explains the reported behavior?
- Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment.
- Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts.
- The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping.
- Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion.
Explanation
Correct Answer
D:Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts. The targeted correction is: Attach the intended RED drop profile to the scheduler and validate threshold values.
Incorrect Answers
A:Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
B:Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
C:The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Question 473
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: An interface starts discarding packets only after its queue fully fills, producing bursty loss even though a planned RED profile should drop earlier. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
- The relevant drop counter increments only for the mechanism causing the observed service problem.
- Burst tests show bounded occupancy and materially fewer drops without violating other class allocations.
- Per-queue counters increment on the intended queue for representative classified packets.
Explanation
Correct Answer
A:Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion.
Incorrect Answers
B:The relevant drop counter increments only for the mechanism causing the observed service problem. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
C:Burst tests show bounded occupancy and materially fewer drops without violating other class allocations. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
D:Per-queue counters increment on the intended queue for representative classified packets. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Question 474
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: An interface starts discarding packets only after its queue fully fills, producing bursty loss even though a planned RED profile should drop earlier. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Use per-stage CoS monitoring before adjusting queue or policer parameters.
- Attach the intended RED drop profile to the scheduler and validate threshold values.
- Tune the supported queue buffer allocation for measured burst characteristics.
- Correct the forwarding-class mapping to the supported target output queue.
Explanation
Correct Answer
B:Attach the intended RED drop profile to the scheduler and validate threshold values. The change addresses the root behavior described here: Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion. Verify success with: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Incorrect Answers
A:Use per-stage CoS monitoring before adjusting queue or policer parameters. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
C:Tune the supported queue buffer allocation for measured burst characteristics. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
D:Correct the forwarding-class mapping to the supported target output queue. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Question 475
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An interface starts discarding packets only after its queue fully fills, producing bursty loss even though a planned RED profile should drop earlier. Which operational control would best prevent a recurrence of this exact failure mode?
- Preserve labeled counter baselines during incident and post-change reviews.
- Test microbursts with buffer and latency metrics rather than only averaged Mbps.
- Review drop curves with a known traffic mix, including high and low loss-priority flows.
- Include classification-to-queue trace checks in CoS regression tests.
Explanation
Correct Answer
C:Review drop curves with a known traffic mix, including high and low loss-priority flows. The control limits repetition of the described root condition: Random early detection uses occupancy thresholds and packet loss priority to begin selective dropping before full buffer exhaustion. During audits, confirm: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Incorrect Answers
A:Preserve labeled counter baselines during incident and post-change reviews. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Queue telemetry misleading totals. Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
B:Test microbursts with buffer and latency metrics rather than only averaged Mbps. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Scheduler queue buffer exhaustion. Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
D:Include classification-to-queue trace checks in CoS regression tests. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is RED drop profile and the confirming observation is: Counters show controlled early drops for the chosen packet loss priority rather than only tail-drop bursts.
Question 476
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two packets map into the same forwarding class but one should be discarded sooner during congestion because it carries a higher packet loss priority. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare internal classification with the applied rewrite rules and on-wire DSCP markings.
- Inspect classifier results, forwarding-class-to-queue bindings and effective egress interface configuration.
- Inspect the egress DSCP rewrite map and the agreed interdomain QoS marking contract.
- Inspect PLP classification and egress queue drop behavior for both packet types.
Explanation
Correct Answer
D:Inspect PLP classification and egress queue drop behavior for both packet types. This check examines the decisive condition for Loss priority distinction before any unrelated changes are made. The underlying mechanism is: Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion. The confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Incorrect Answers
A:Compare internal classification with the applied rewrite rules and on-wire DSCP markings. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically DSCP rewrite at egress. A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
B:Inspect classifier results, forwarding-class-to-queue bindings and effective egress interface configuration. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
C:Inspect the egress DSCP rewrite map and the agreed interdomain QoS marking contract. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Rewrite rule untrusted downstream. Unconditional remarking can falsely elevate classes and violate trust-domain agreements. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Question 477
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two packets map into the same forwarding class but one should be discarded sooner during congestion because it carries a higher packet loss priority. Which routing or service mechanism best explains the reported behavior?
- Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion.
- Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion.
- A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain.
- The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping.
Explanation
Correct Answer
A:Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected. The targeted correction is: Configure consistent PLP classification and compatible drop-profile handling.
Incorrect Answers
B:Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Network control queue. Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
C:A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically DSCP rewrite at egress. A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
D:The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Question 478
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two packets map into the same forwarding class but one should be discarded sooner during congestion because it carries a higher packet loss priority. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Routing Hellos and control updates continue to be delivered during controlled bulk traffic load.
- High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
- Packet capture on the egress wire contains the intended DSCP marking for correctly classified traffic.
- Per-queue counters increment on the intended queue for representative classified packets.
Explanation
Correct Answer
B:High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion.
Incorrect Answers
A:Routing Hellos and control updates continue to be delivered during controlled bulk traffic load. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Network control queue. Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
C:Packet capture on the egress wire contains the intended DSCP marking for correctly classified traffic. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically DSCP rewrite at egress. A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
D:Per-queue counters increment on the intended queue for representative classified packets. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Question 479
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two packets map into the same forwarding class but one should be discarded sooner during congestion because it carries a higher packet loss priority. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore a protected network-control classification and scheduler policy without unbounded strict priority.
- Attach a suitable rewrite rule to the egress interface while respecting the agreed marking contract.
- Configure consistent PLP classification and compatible drop-profile handling.
- Correct the forwarding-class mapping to the supported target output queue.
Explanation
Correct Answer
C:Configure consistent PLP classification and compatible drop-profile handling. The change addresses the root behavior described here: Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion. Verify success with: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Incorrect Answers
A:Restore a protected network-control classification and scheduler policy without unbounded strict priority. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Network control queue. Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
B:Attach a suitable rewrite rule to the egress interface while respecting the agreed marking contract. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically DSCP rewrite at egress. A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
D:Correct the forwarding-class mapping to the supported target output queue. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Question 480
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two packets map into the same forwarding class but one should be discarded sooner during congestion because it carries a higher packet loss priority. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate control adjacency stability under full data-plane link utilization.
- Confirm on-wire markings rather than only local forwarding-class counters.
- Include classification-to-queue trace checks in CoS regression tests.
- Check loss-priority boundaries across trust domains and encapsulation changes.
Explanation
Correct Answer
D:Check loss-priority boundaries across trust domains and encapsulation changes. The control limits repetition of the described root condition: Forwarding class chooses a queue while packet loss priority influences the packet's discard preference under congestion. During audits, confirm: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Incorrect Answers
A:Validate control adjacency stability under full data-plane link utilization. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Network control queue. Routing control traffic often needs distinct forwarding treatment to remain stable during forwarding congestion. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
B:Confirm on-wire markings rather than only local forwarding-class counters. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically DSCP rewrite at egress. A rewrite rule maps internal forwarding treatment back to a packet header field for the downstream domain. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
C:Include classification-to-queue trace checks in CoS regression tests. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Forwarding class queue mapping. The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping. In this scenario, however, the distinguishing issue is Loss priority distinction and the confirming observation is: High-PLP packets experience the expected early-drop tendency while low-PLP packets are better protected.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests