Juniper JN0-664 Practice Test 26
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.
Question 251
A Junos service-provider routing engineer investigates the following routing and service incident: A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Explanation
Correct Answer
B:The case-specific routing and services action is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. The governing Junos routing/service principle is: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
Incorrect Answers
A:This alternative proposes: Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
C:This alternative proposes: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. It concerns a different Junos engineering issue CoS forwarding classes packet-loss priority and egress queue binding, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
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 schedulers scheduler-maps and bandwidth sharing.
Question 252
A provider routing design review considers this situation. A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved. A colleague proposes: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. 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.
- 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.
- On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
Explanation
Correct Answer
D:The relevant Junos service-provider networking principle is: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. In the described provider-network case (A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved.), it supports the planned action: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Incorrect Answers
A:This alternative proposes: Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth. It concerns a different Junos engineering issue CoS forwarding classes packet-loss priority and egress queue binding, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
B: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 schedulers scheduler-maps and bandwidth sharing.
C:This alternative proposes: On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
Question 253
A Juniper service-provider engineer needs decisive verification evidence for this situation. A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved. 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 DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
Explanation
Correct Answer
D:The direct discriminating observation is: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. In the stated situation (A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved.), the intended acceptance outcome is: The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided.
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 schedulers scheduler-maps and bandwidth sharing.
B: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 schedulers scheduler-maps and bandwidth sharing.
C:This alternative proposes: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
Question 254
A service-provider acceptance team reviews the result of a provider-service change. A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved. The intended verification is: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. Which outcome BEST demonstrates success? Select ONE best answer.
- The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
- The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided.
- The expected DIS represents the shared LAN in the LSDB and routes converge when a controlled election change takes place.
- 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: The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided. Confirm this by: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
Incorrect Answers
A:This alternative proposes: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
C:That option concerns IS-IS DIS pseudonode and broadcast circuit election. The related controlled intervention is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
D:This alternative proposes: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
Question 255
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A shared core uplink carries VoIP and backups; the new strict-priority class consumes capacity continuously and leaves other queues starved. 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.
- Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map.
- Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured.
- Configure an ingress policer to discard every packet above a tiny burst threshold and claim it is equivalent to lossless queuing under egress shaping.
Explanation
Correct Answer
A:The directly relevant unsafe assumption is: Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload. That conflicts with the edge-to-cloud principle: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
Incorrect Answers
B:This alternative proposes: Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
C:This alternative proposes: Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
D: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 schedulers scheduler-maps and bandwidth sharing.
Question 256
A Junos service-provider routing engineer investigates the following routing and service incident: A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Explanation
Correct Answer
C:The case-specific routing and services action is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. The governing Junos routing/service principle is: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. Verify the decision through: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
Incorrect Answers
A: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 schedulers scheduler-maps and bandwidth sharing.
B:This alternative proposes: Examine external route Type 1 versus Type 2 cost behavior and the forwarding cost toward the ASBR when determining why routers choose different exits. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
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 schedulers scheduler-maps and bandwidth sharing.
Question 257
A provider routing design review considers this situation. A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments. A colleague proposes: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection.
- 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.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
Explanation
Correct Answer
D:The relevant Junos service-provider networking principle is: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. In the described provider-network case (A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments.), it supports the planned action: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Incorrect Answers
A: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 schedulers scheduler-maps and bandwidth sharing.
B:This alternative proposes: PIM SSM builds a source-rooted tree without an RP and uses IGMPv3 source inclusion on IPv4 receiver links for explicit source selection. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
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 schedulers scheduler-maps and bandwidth sharing.
Question 258
A Juniper service-provider engineer needs decisive verification evidence for this situation. A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments. 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.
- Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
Explanation
Correct Answer
C:The direct discriminating observation is: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. In the stated situation (A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments.), the intended acceptance outcome is: The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided.
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 schedulers scheduler-maps and bandwidth sharing.
B:This alternative proposes: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing in the stated situation (A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments.). A better case-specific check is: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. The more targeted action is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
D: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 schedulers scheduler-maps and bandwidth sharing.
Question 259
A service-provider acceptance team reviews the result of a provider-service change. A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments. The intended verification is: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. Which outcome BEST demonstrates success? Select ONE best answer.
- The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
- The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
- Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop.
Explanation
Correct Answer
B:The verified success outcome is: The control and real-time classes meet latency needs while ordinary traffic retains justified minimum service and queue starvation is avoided. Confirm this by: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. The related controlled intervention is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Incorrect Answers
A:This alternative proposes: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
C:This alternative proposes: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret. It concerns a different Junos engineering issue CoS RED drop profiles and rewrite-marking validation, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.
D:That option concerns VPLS MAC learning flooding and split-horizon safeguards. The related controlled intervention is: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Question 260
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A transport upgrade changes link speed but the static scheduler allocation no longer reflects the operator's service-level commitments. 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.
- Configure an ingress policer to discard every packet above a tiny burst threshold and claim it is equivalent to lossless queuing under egress shaping.
- Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed.
- Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes.
Explanation
Correct Answer
A:The directly relevant unsafe assumption is: Give an unlimited strict-priority class most of the link and guarantee all other queues will receive their intended bandwidth during sustained overload. That conflicts with the edge-to-cloud principle: Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations. Apply instead: Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Incorrect Answers
B: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 schedulers scheduler-maps and bandwidth sharing.
C: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 CoS schedulers scheduler-maps and bandwidth sharing.
D:This alternative proposes: Declare that a Type 2 external metric always equals the sum of backbone hop costs and must be changed whenever an IGP link cost changes. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue CoS schedulers scheduler-maps and bandwidth sharing.