Question 490
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Voice traffic leaves an MPLS ingress as a correctly prioritized internal class but transit LSRs see an unexpected MPLS traffic class marking. Which operational control would best prevent a recurrence of this exact failure mode?
- Trace classification and scheduling at every congested hop during service acceptance.
- Test CoS treatment on both labeled and unlabeled segments.
- Test microbursts with buffer and latency metrics rather than only averaged Mbps.
- Audit class mappings at inter-POP boundaries and after line-card replacements.
Explanation
Correct Answer
B:Test CoS treatment on both labeled and unlabeled segments. The control limits repetition of the described root condition: MPLS-classified transport forwarding can depend on the label TC bits rather than the IP payload DSCP inside the tunnel. During audits, confirm: On-wire MPLS packets carry the intended TC and transit queues respond according to the contract.
Incorrect Answers
A:Trace classification and scheduling at every congested hop during service acceptance. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Traffic priority at egress bottleneck. CoS decisions that influence transmission occur at the real bottleneck; accurate classification upstream cannot reserve service at a differently configured output. In this scenario, however, the distinguishing issue is MPLS traffic class rewrite and the confirming observation is: On-wire MPLS packets carry the intended TC and transit queues respond according to the contract.
C: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 MPLS traffic class rewrite and the confirming observation is: On-wire MPLS packets carry the intended TC and transit queues respond according to the contract.
D:Audit class mappings at inter-POP boundaries and after line-card replacements. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically BA mapping inconsistent across core. Each hop's classifier interprets the markings it receives, and inconsistent BA maps can break end-to-end class treatment. In this scenario, however, the distinguishing issue is MPLS traffic class rewrite and the confirming observation is: On-wire MPLS packets carry the intended TC and transit queues respond according to the contract.
Question 491
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A provider needs to classify one customer's TCP application independently of the DSCP field because the customer does not use consistent markings. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare policer bandwidth and burst settings against measured traffic and the committed service profile.
- Inspect classifier results, forwarding-class-to-queue bindings and effective egress interface configuration.
- Inspect firewall-filter classification matches for the customer's source and port fields.
- Compare internal classification with the applied rewrite rules and on-wire DSCP markings.
Explanation
Correct Answer
C:Inspect firewall-filter classification matches for the customer's source and port fields. This check examines the decisive condition for Multifield ingress match before any unrelated changes are made. The underlying mechanism is: Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. The confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Incorrect Answers
A:Compare policer bandwidth and burst settings against measured traffic and the committed service profile. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
D: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Question 492
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A provider needs to classify one customer's TCP application independently of the DSCP field because the customer does not use consistent markings. Which routing or service mechanism best explains the reported behavior?
- A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation.
- The forwarding class connects classification results to an output queue; correct DSCP alone does not guarantee that queue mapping.
- Unconditional remarking can falsely elevate classes and violate trust-domain agreements.
- Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment.
Explanation
Correct Answer
D:Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Test flows matching approved application fields enter the intended forwarding class while other flows do not. The targeted correction is: Deploy a bounded multifield classifier on the correct ingress interface.
Incorrect Answers
A:A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
B: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
C:Unconditional remarking can falsely elevate classes and violate trust-domain agreements. This is a plausible protocol explanation 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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Question 493
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A provider needs to classify one customer's TCP application independently of the DSCP field because the customer does not use consistent markings. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Test flows matching approved application fields enter the intended forwarding class while other flows do not.
- Policer exceed counters and throughput tests align with the corrected contracted profile.
- Per-queue counters increment on the intended queue for representative classified packets.
- Packet capture on the egress wire contains the intended DSCP marking for correctly classified traffic.
Explanation
Correct Answer
A:Test flows matching approved application fields enter the intended forwarding class while other flows do not. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment.
Incorrect Answers
B:Policer exceed counters and throughput tests align with the corrected contracted profile. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
C: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
D: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Question 494
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A provider needs to classify one customer's TCP application independently of the DSCP field because the customer does not use consistent markings. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Adjust the policer to the validated service limit and burst allowance instead of removing all control.
- Deploy a bounded multifield classifier on the correct ingress interface.
- Correct the forwarding-class mapping to the supported target output queue.
- Attach a suitable rewrite rule to the egress interface while respecting the agreed marking contract.
Explanation
Correct Answer
B:Deploy a bounded multifield classifier on the correct ingress interface. The change addresses the root behavior described here: Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. Verify success with: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Incorrect Answers
A:Adjust the policer to the validated service limit and burst allowance instead of removing all control. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
C: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
D: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Question 495
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A provider needs to classify one customer's TCP application independently of the DSCP field because the customer does not use consistent markings. Which operational control would best prevent a recurrence of this exact failure mode?
- Track sustained and burst traffic separately when changing service policers.
- Include classification-to-queue trace checks in CoS regression tests.
- Maintain a test matrix for application ports and source ranges during changes.
- Confirm on-wire markings rather than only local forwarding-class counters.
Explanation
Correct Answer
C:Maintain a test matrix for application ports and source ranges during changes. The control limits repetition of the described root condition: Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. During audits, confirm: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Incorrect Answers
A:Track sustained and burst traffic separately when changing service policers. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Policer threshold drop. A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. In this scenario, however, the distinguishing issue is Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
B: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
D: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 Multifield ingress match and the confirming observation is: Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Question 496
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. 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.
- Inspect firewall-filter classification matches for the customer's source and port fields.
- Correlate queue occupancy, peak burst size and scheduler buffer allocation.
- Compare policer bandwidth and burst settings against measured traffic and the committed service profile.
Explanation
Correct Answer
D:Compare policer bandwidth and burst settings against measured traffic and the committed service profile. This check examines the decisive condition for Policer threshold drop before any unrelated changes are made. The underlying mechanism is: A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. The confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
B:Inspect firewall-filter classification matches for the customer's source and port fields. This is a plausible diagnostic check for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
C: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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Question 497
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. Which routing or service mechanism best explains the reported behavior?
- A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation.
- Interface total drops conflate multiple mechanisms, while queue and policer counters identify different stages of treatment.
- Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment.
- Scheduler settings govern buffer as well as bandwidth and priority, so transmit rate alone does not absorb short bursts.
Explanation
Correct Answer
A:A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Policer exceed counters and throughput tests align with the corrected contracted profile. The targeted correction is: Adjust the policer to the validated service limit and burst allowance instead of removing all control.
Incorrect Answers
B: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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
C:Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. This is a plausible protocol explanation for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
D: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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Question 498
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The relevant drop counter increments only for the mechanism causing the observed service problem.
- Policer exceed counters and throughput tests align with the corrected contracted profile.
- Burst tests show bounded occupancy and materially fewer drops without violating other class allocations.
- Test flows matching approved application fields enter the intended forwarding class while other flows do not.
Explanation
Correct Answer
B:Policer exceed counters and throughput tests align with the corrected contracted profile. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation.
Incorrect Answers
A: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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
D:Test flows matching approved application fields enter the intended forwarding class while other flows do not. This is a plausible observed evidence for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Question 499
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. 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.
- Tune the supported queue buffer allocation for measured burst characteristics.
- Adjust the policer to the validated service limit and burst allowance instead of removing all control.
- Deploy a bounded multifield classifier on the correct ingress interface.
Explanation
Correct Answer
C:Adjust the policer to the validated service limit and burst allowance instead of removing all control. The change addresses the root behavior described here: A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. Verify success with: Policer exceed counters and throughput tests align with the corrected contracted profile.
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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
B: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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
D:Deploy a bounded multifield classifier on the correct ingress interface. This is a plausible configuration or operational fix for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Question 500
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A bursty telemetry application sees sudden packet loss because an ingress policer enforces a smaller committed rate than the service contract. 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.
- Maintain a test matrix for application ports and source ranges during changes.
- Track sustained and burst traffic separately when changing service policers.
Explanation
Correct Answer
D:Track sustained and burst traffic separately when changing service policers. The control limits repetition of the described root condition: A policer meters a flow and may discard or reclassify out-of-profile traffic; it is not a capacity reservation. During audits, confirm: Policer exceed counters and throughput tests align with the corrected contracted profile.
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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
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 Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
C:Maintain a test matrix for application ports and source ranges during changes. This is a plausible preventive practice for a different Class of Service (CoS) condition, specifically Multifield ingress match. Multifield classification can use more packet-header fields than DSCP-only BA classification to assign forwarding treatment. In this scenario, however, the distinguishing issue is Policer threshold drop and the confirming observation is: Policer exceed counters and throughput tests align with the corrected contracted profile.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests