Juniper JN0-664 Practice Test 28
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.
Question 271
A Junos service-provider routing engineer investigates the following routing and service incident: An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort. 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.
- Diagnose unknown unicast flooding and Layer 2 loops by distinguishing learned customer MAC paths, BUM handling and VPLS split-horizon behavior.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
Explanation
Correct Answer
C:The case-specific routing and services action is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces. The governing Junos routing/service principle is: 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.
Incorrect Answers
A: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 RED drop profiles and rewrite-marking validation.
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 RED drop profiles and rewrite-marking validation.
D: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 RED drop profiles and rewrite-marking validation.
Question 272
A provider routing design review considers this situation. An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort. A colleague proposes: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- Level 1 routers know their local IS-IS area, Level 2 routers maintain interarea connectivity, and L1/L2 systems can provide area exits with suitable reachability and attached signaling.
- 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.
- Forwarding class selects an appropriate queue and packet-loss priority influences treatment such as drop precedence, but priority marking cannot create unavailable physical bandwidth.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort.), it supports the planned action: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Incorrect Answers
A: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 RED drop profiles and rewrite-marking validation.
B:This alternative proposes: Level 1 routers know their local IS-IS area, Level 2 routers maintain interarea connectivity, and L1/L2 systems can provide area exits with suitable reachability and attached signaling. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.
D: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 RED drop profiles and rewrite-marking validation.
Question 273
A Juniper service-provider engineer needs decisive verification evidence for this situation. An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
- Review show isis interface detail, LAN priority, circuit level, elected DIS, neighbor states and pseudonode LSP records.
- 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.
Explanation
Correct Answer
A:The direct discriminating observation is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. In the stated situation (An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort.), the intended acceptance outcome is: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
Incorrect Answers
B: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 RED drop profiles and rewrite-marking validation.
C: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 RED drop profiles and rewrite-marking validation.
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 RED drop profiles and rewrite-marking validation.
Question 274
A service-provider acceptance team reviews the result of a provider-service change. An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort. The intended verification is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. Which outcome BEST demonstrates success? Select ONE best answer.
- Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
- 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
B:The verified success outcome is: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret. Confirm this by: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
Incorrect Answers
A:That option concerns BGP export import policy and prefix controls. The related controlled intervention is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
C: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 RED drop profiles and rewrite-marking validation.
D:That option concerns CoS policers traffic-shaping and committed-rate contracts. The related controlled intervention is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Question 275
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An ISP notices that voice packets lose their DSCP marking after a PE egress hop and the next provider treats them as best effort. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Create a custom classifier in configuration but omit the interface association and assume all access ports will automatically use the new map.
- Configure an ingress policer to discard every packet above a tiny burst threshold and claim it is equivalent to lossless queuing under egress shaping.
- Rewrite every customer's packet to the highest-priority DSCP and set all drop-profile thresholds to zero to eliminate congestion entirely.
- Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
Explanation
Correct Answer
C:That conflicts with the edge-to-cloud principle: 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.
Incorrect Answers
A: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 RED drop profiles and rewrite-marking validation.
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 RED drop profiles and rewrite-marking validation.
D:This alternative proposes: Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.
Question 276
A Junos service-provider routing engineer investigates the following routing and service incident: A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Configure a scheduler map for the intended egress forwarding classes and verify bandwidth, buffer and priority behavior during real congestion.
Explanation
Correct Answer
B:The case-specific routing and services action is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces. The governing Junos routing/service principle is: 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. Verify the decision through: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
Incorrect Answers
A:This alternative proposes: Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.
C: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 RED drop profiles and rewrite-marking validation.
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 RED drop profiles and rewrite-marking validation.
Question 277
A provider routing design review considers this situation. A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned. A colleague proposes: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs.
- 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.
- 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.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned.), it supports the planned action: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Incorrect Answers
B:This alternative proposes: IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.
C: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 RED drop profiles and rewrite-marking validation.
D: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 RED drop profiles and rewrite-marking validation.
Question 278
A Juniper service-provider engineer needs decisive verification evidence for this situation. A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned. 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 service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
- Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
Explanation
Correct Answer
C:The direct discriminating observation is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. In the stated situation (A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned.), the intended acceptance outcome is: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
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 RED drop profiles and rewrite-marking validation.
B:This alternative proposes: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.
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 RED drop profiles and rewrite-marking validation.
Question 279
A service-provider acceptance team reviews the result of a provider-service change. A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned. The intended verification is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. 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.
- Latency-sensitive traffic uses the correct supported queue while lower-priority flows experience controlled loss under congestion.
- Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret.
- Participating customer sites exchange permitted Ethernet frames through a correctly signaled multipoint service without bridging unrelated tenants.
Explanation
Correct Answer
C:The verified success outcome is: Congestion handling protects critical traffic without uncontrolled buffer delay, and packets leave with markings the next domain can interpret. Confirm this by: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values. The related controlled intervention is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Incorrect Answers
A:That option concerns Junos CoS behavior aggregate versus multifield classifiers. The related controlled intervention is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
B: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 RED drop profiles and rewrite-marking validation.
D:That option concerns VPLS service control plane LDP versus BGP distribution. The related controlled intervention is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
Question 280
A Junos service-provider routing engineer investigates this service-provider network scenario. A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP.
- Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
- 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.
- Choose a supported VPLS signaling model and verify peer discovery, service membership and MPLS forwarding transport independently.
Explanation
Correct Answers
B:The case-specific routing and services action is: Tune congestion drop behavior and outbound packet markings while preserving intentional service differentiation across trusted interfaces.
C:The direct discriminating observation is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
Incorrect Answers
A:This alternative proposes: Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation in the stated situation (A queue begins dropping best-effort packets long before saturation because the configured drop profile threshold is much lower than planned.). A better case-specific check is: Check egress queue occupancy, WRED/drop-profile thresholds, packet-loss-priority settings, rewrite maps and observed DSCP or MPLS EXP values.
D:This alternative proposes: Review forwarding-class definitions, queue identifiers, packet-loss priority classification, interface CoS output and measured packet counters. 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 RED drop profiles and rewrite-marking validation.
E:This alternative proposes: Choose a supported VPLS signaling model and verify peer discovery, service membership and MPLS forwarding transport independently. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue CoS RED drop profiles and rewrite-marking validation.