Juniper JN0-664 Practice Test 27
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.
Question 261
A Junos service-provider routing engineer investigates the following routing and service incident: A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
- 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.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
Explanation
Correct Answer
C: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. Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
Incorrect Answers
A:This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
B: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 policers traffic-shaping and committed-rate contracts.
D: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 policers traffic-shaping and committed-rate contracts.
Question 262
A provider routing design review considers this situation. A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission. A colleague proposes: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. 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.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
- 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.
- ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission.), it supports the planned action: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
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 policers traffic-shaping and committed-rate contracts.
B: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 policers traffic-shaping and committed-rate contracts.
D:This alternative proposes: ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
Question 263
A Juniper service-provider engineer needs decisive verification evidence for this situation. A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect VPN route label, resolved tunnel in inet.3, label-switched path, control-plane next hop, penultimate-hop behavior and egress VRF lookup.
- Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
Explanation
Correct Answer
C:The direct discriminating observation is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. In the stated situation (A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission.), the intended acceptance outcome is: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
Incorrect Answers
A:This alternative proposes: Inspect VPN route label, resolved tunnel in inet.3, label-switched path, control-plane next hop, penultimate-hop behavior and egress VRF lookup. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
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 policers traffic-shaping and committed-rate contracts.
D:This alternative proposes: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
Question 264
A service-provider acceptance team reviews the result of a provider-service change. A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission. The intended verification is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. Which outcome BEST demonstrates success? Select ONE best answer.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
- The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
- Multicast subscribers continue receiving approved sources when one RP fails, with no duplicate or missing source registration state.
- Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
Explanation
Correct Answer
B:The verified success outcome is: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops. Confirm this by: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
Incorrect Answers
A: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 policers traffic-shaping and committed-rate contracts.
C:That option concerns Anycast RP resilient multicast service and routing policy. The related controlled intervention is: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
D:This alternative proposes: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion. 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 policers traffic-shaping and committed-rate contracts.
Question 265
A Junos service-provider routing engineer investigates this service-provider network scenario. A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Inspect DSCP or EXP bits, classifier mapping, interface ingress association, show class-of-service interface and relevant forwarding-class counters.
- Diagnose unknown unicast flooding and Layer 2 loops by distinguishing learned customer MAC paths, BUM handling and VPLS split-horizon behavior.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
- Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
- Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
Explanation
Correct Answers
C:The direct discriminating observation is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
E:The case-specific routing and services action is: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. The governing Junos routing/service principle is: 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.
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 policers traffic-shaping and committed-rate contracts in the stated situation (A 100-Mb/s subscriber sends 200-Mb/s short bursts and the carrier wants to distinguish policer drops from a shaper's queued transmission.). A better case-specific check is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
B:This alternative proposes: Diagnose unknown unicast flooding and Layer 2 loops by distinguishing learned customer MAC paths, BUM handling and VPLS split-horizon behavior. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
D:This alternative proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
Question 266
A Junos service-provider routing engineer investigates the following routing and service incident: A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile. 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.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
- Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Explanation
Correct Answer
C:The case-specific routing and services action is: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. The governing Junos routing/service principle is: 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. Verify the decision through: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
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 policers traffic-shaping and committed-rate contracts.
B: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 policers traffic-shaping and committed-rate contracts.
D: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 policers traffic-shaping and committed-rate contracts.
Question 267
A provider routing design review considers this situation. A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile. A colleague proposes: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. 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.
- Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.
- 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.
- An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile.), it supports the planned action: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
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 policers traffic-shaping and committed-rate contracts.
B: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 policers traffic-shaping and committed-rate contracts.
D:This alternative proposes: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
Question 268
A Juniper service-provider engineer needs decisive verification evidence for this situation. A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
- Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
Explanation
Correct Answer
B:The direct discriminating observation is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. In the stated situation (A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile.), the intended acceptance outcome is: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops.
Incorrect Answers
A:This alternative proposes: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.
C:This alternative proposes: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices. 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 policers traffic-shaping and committed-rate contracts.
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 policers traffic-shaping and committed-rate contracts.
Question 269
A service-provider acceptance team reviews the result of a provider-service change. A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile. The intended verification is: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. 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.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
Explanation
Correct Answer
A:The verified success outcome is: The customer contract rate is enforced with predictable handling of permitted bursts and no unintended control-plane traffic drops. Confirm this by: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. The related controlled intervention is: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
Incorrect Answers
B: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 policers traffic-shaping and committed-rate contracts.
C:That option concerns Multiprotocol BGP family negotiations and VPN routes. The related controlled intervention is: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
D:This alternative proposes: Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion. 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 policers traffic-shaping and committed-rate contracts.
Question 270
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A service is billed at a committed data rate, but a technician mistakes an interface's port speed for its active configured policing profile. 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.
- Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
- 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
D:Apply instead: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
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 policers traffic-shaping and committed-rate contracts.
B: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 policers traffic-shaping and committed-rate contracts.
C:This alternative proposes: Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue CoS policers traffic-shaping and committed-rate contracts.