Juniper JN0-664 Practice Test 25
Question 240
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A business circuit needs a source subnet classified differently from the customer's preexisting DSCP markings, requiring suitable MF rules. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed.
- Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path.
- Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map.
- Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload.
Explanation
Correct Answer
C:That conflicts with the edge-to-cloud principle: Behavior-aggregate classification examines existing packet markings whereas multifield classification can evaluate packet header fields; a configured classifier must be applied to the correct interface.
Incorrect Answers
A:This alternative proposes: Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed. It concerns a different Junos engineering issue CoS forwarding classes packet-loss priority and egress queue binding, not the directly tested provider-network issue Junos CoS behavior aggregate versus multifield classifiers.
B:This alternative proposes: Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue Junos CoS behavior aggregate versus multifield classifiers.
D:This alternative proposes: Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue Junos CoS behavior aggregate versus multifield classifiers.
Question 241
A Junos service-provider routing engineer investigates the following routing and service incident: An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
- Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Explanation
Correct Answer
D:The case-specific routing and services action is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. The governing Junos routing/service principle is: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
Incorrect Answers
A:This alternative proposes: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
B:This alternative proposes: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
C:This alternative proposes: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 242
A provider routing design review considers this situation. An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion. A colleague proposes: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. Which technical principle BEST supports that action? Select ONE best answer.
- Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
- Behavior-aggregate classification examines existing packet markings whereas multifield classification can evaluate packet header fields; a configured classifier must be applied to the correct interface.
- Weighted random early detection can probabilistically drop or mark traffic as buffers fill, and rewrite rules must reflect the egress contract rather than blindly copy internal priorities.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth. In the described provider-network case (An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion.), it supports the planned action: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Incorrect Answers
B:This alternative proposes: Behavior-aggregate classification examines existing packet markings whereas multifield classification can evaluate packet header fields; a configured classifier must be applied to the correct interface. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
C:This alternative proposes: Weighted random early detection can probabilistically drop or mark traffic as buffers fill, and rewrite rules must reflect the egress contract rather than blindly copy internal priorities. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 243
A Juniper service-provider engineer needs decisive verification evidence for this situation. An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
- Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs.
- Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
- Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters.
Explanation
Correct Answer
C:The direct discriminating observation is: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. In the stated situation (An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion.), the intended acceptance outcome is: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
Incorrect Answers
A:This alternative proposes: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
B:This alternative proposes: Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 244
A service-provider acceptance team reviews the result of a provider-service change. An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion. The intended verification is: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. Which outcome BEST demonstrates success? Select ONE best answer.
- Premium voice packets enter their intended forwarding class while unmarked best-effort traffic remains appropriately classified.
- The multihomed site avoids reaccepting its own redistributed routes, and intended OSPF traffic uses the validated primary or backup route.
- Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
- The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
Explanation
Correct Answer
C:The verified success outcome is: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion. Confirm this by: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
Incorrect Answers
A:That option concerns Junos CoS behavior aggregate versus multifield classifiers. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
B:That option concerns Site of Origin and OSPF sham-link loop control. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
D:That option concerns CoS policers traffic-shaping and committed-rate contracts. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Question 245
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An MPLS network maps customer interactive sessions into a class with unexpected high drop precedence and they disappear during congestion. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload.
- Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed.
- Configure an ingress policer to discard every packet above a tiny burst threshold and claim it is equivalent to lossless queuing under egress shaping.
- Leak the entire provider table into every small Level 1 access area and assert this cannot affect memory, scale or path choices.
Explanation
Correct Answer
B:That conflicts with the edge-to-cloud principle: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
Incorrect Answers
A:This alternative proposes: Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
C:This alternative proposes: Configure an ingress policer to discard every packet above a tiny burst threshold and claim it is equivalent to lossless queuing under egress shaping. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: Leak the entire provider table into every small Level 1 access area and assert this cannot affect memory, scale or path choices. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 246
A Junos service-provider routing engineer investigates the following routing and service incident: A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Explanation
Correct Answer
A:The case-specific routing and services action is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. The governing Junos routing/service principle is: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth. Verify the decision through: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
Incorrect Answers
B:This alternative proposes: Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
C:This alternative proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 247
A provider routing design review considers this situation. A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping. A colleague proposes: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. Which technical principle BEST supports that action? Select ONE best answer.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
- Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
- EVPN commonly conveys MAC reachability through BGP route type 2; optional IP binding and policies support host learning and next-hop selection, while label or encapsulation rules depend on the deployment.
- A policer can discard or remark excess traffic according to a configured rate and burst; shaping usually buffers and schedules departure under a bandwidth constraint, with different latency effects.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth. In the described provider-network case (A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping.), it supports the planned action: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Incorrect Answers
A:This alternative proposes: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
C:This alternative proposes: EVPN commonly conveys MAC reachability through BGP route type 2; optional IP binding and policies support host learning and next-hop selection, while label or encapsulation rules depend on the deployment. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: A policer can discard or remark excess traffic according to a configured rate and burst; shaping usually buffers and schedules departure under a bandwidth constraint, with different latency effects. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 248
A Juniper service-provider engineer needs decisive verification evidence for this situation. A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
- Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
- Review show isis interface detail, LAN priority, circuit level, elected DIS, neighbor states and pseudonode LSP records.
Explanation
Correct Answer
C:The direct discriminating observation is: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. In the stated situation (A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping.), the intended acceptance outcome is: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
Incorrect Answers
A:This alternative proposes: Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
B:This alternative proposes: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: Review show isis interface detail, LAN priority, circuit level, elected DIS, neighbor states and pseudonode LSP records. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
Question 249
A service-provider acceptance team reviews the result of a provider-service change. A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping. The intended verification is: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. Which outcome BEST demonstrates success? Select ONE best answer.
- The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided.
- Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
- The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
Explanation
Correct Answer
B:The verified success outcome is: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion. Confirm this by: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Incorrect Answers
A:That option concerns CoS schedulers scheduler-maps and bandwidth sharing. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
C:That option concerns LDP signaled Layer 2 circuit pseudowire status and VC identifiers. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
D:That option concerns CoS RED drop profiles and rewrite-marking validation. The related controlled intervention is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Question 250
A Junos service-provider routing engineer investigates this service-provider network scenario. A PE identifies six configured forwarding classes but the outgoing port has fewer supported hardware queues, requiring validation of the actual class-to-queue mapping. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
- Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
- Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
Explanation
Correct Answers
C:The case-specific routing and services action is: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
E:The direct discriminating observation is: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters.
Incorrect Answers
A:This alternative proposes: Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
B:This alternative proposes: Use Site of Origin controls and supported OSPF sham-link design where required to prevent multihomed customer loops or preserve intended intra-area OSPF path selection. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.
D:This alternative proposes: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS forwarding classes packet-loss priority and egress queue binding.