cert
cert-1
cert-2

Pass Juniper JN0-664 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
JN0-664 Exam - Verified By Experts
JN0-664 Premium File

JN0-664 Premium File

$69.99
$76.99
  • Premium File 96 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 20 downloads in the last 7 days
block-screenshots
Juniper JN0-664 Practice Test 16

Question 150

A Junos service-provider routing engineer investigates this service-provider network scenario. An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  2. Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
  3. Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
  4. 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.
  5. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Explanation

Correct Answers

D:

The direct discriminating observation is: 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.

E:

The case-specific routing and services action is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. The governing Junos routing/service principle is: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. Verify the decision through: 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.

Incorrect Answers

A:

This alternative proposes: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

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 BGP NEXT_HOP reachability and inet.3 recursion.

Question 151

A Junos service-provider routing engineer investigates the following routing and service incident: A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Choose the correct OSPF stub or NSSA area design according to the requirement for redistributed external routes and verify supported Type 7 translation.
  2. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
  3. Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
  4. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Explanation

Correct Answer

C:

The case-specific routing and services action is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership. The governing Junos routing/service principle is: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.

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 BGP route reflectors originator and cluster loop prevention.

B:

This alternative proposes: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

D:

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 BGP route reflectors originator and cluster loop prevention.

Question 152

A provider routing design review considers this situation. A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer. A colleague proposes: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership. Which technical principle BEST supports that action? Select ONE best answer.

  1. BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
  2. A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel.
  3. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
  4. Junos schedulers assign queue service treatment, but weights, strict priority and buffer settings must be balanced against starvation and hardware limitations.

Explanation

Correct Answer

C:

The relevant Junos service-provider networking principle is: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. In the described provider-network case (A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer.), it supports the planned action: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Incorrect Answers

A:

This alternative proposes: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

B:

This alternative proposes: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

D:

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 BGP route reflectors originator and cluster loop prevention.

Question 153

A Juniper service-provider engineer needs decisive verification evidence for this situation. A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. 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.
  2. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  3. Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
  4. Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.

Explanation

Correct Answer

B:

The direct discriminating observation is: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. In the stated situation (A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer.), the intended acceptance outcome is: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.

Incorrect Answers

A:

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 BGP route reflectors originator and cluster loop prevention in the stated situation (A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer.). A better case-specific check is: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. The more targeted action is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

C:

This alternative proposes: Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

D:

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 BGP route reflectors originator and cluster loop prevention.

Question 154

A service-provider acceptance team reviews the result of a provider-service change. A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer. The intended verification is: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. Which outcome BEST demonstrates success? Select ONE best answer.

  1. After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.
  2. Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
  3. The configured mode serves actual receivers without uncontrolled multicast flood in sparsely subscribed provider regions.
  4. Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.

Explanation

Correct Answer

B:

The verified success outcome is: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. Confirm this by: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.

Incorrect Answers

A:

That option concerns BGP flap damping penalties and recovery. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

C:

That option concerns PIM dense mode versus sparse mode interface deployment. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

D:

That option concerns BGP multipath equal cost and per-flow forwarding. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Question 155

A Junos service-provider routing engineer investigates this service-provider network scenario. A carrier adds two nonclient PEs and neither learns the other's route because the only hub is configured as a conventional iBGP peer. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
  2. Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
  3. Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
  4. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  5. Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.

Explanation

Correct Answers

C:

The case-specific routing and services action is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership. The governing Junos routing/service principle is: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. Verify the decision through: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.

D:

The direct discriminating observation is: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.

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 BGP route reflectors originator and cluster loop prevention.

B:

This alternative proposes: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

E:

This alternative proposes: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

Question 156

A Junos service-provider routing engineer investigates the following routing and service incident: Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
  2. Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
  3. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
  4. Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Explanation

Correct Answer

D:

The case-specific routing and services action is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Incorrect Answers

A:

This alternative proposes: Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

B:

This alternative proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

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 BGP route reflectors originator and cluster loop prevention.

Question 157

A provider routing design review considers this situation. Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. A colleague proposes: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership. Which technical principle BEST supports that action? Select ONE best answer.

  1. EVPN all-active or single-active multihoming uses a shared ESI and appropriate DF/aliasing coordination to prevent BUM duplication and maintain reachable paths under failure.
  2. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
  3. BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
  4. Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. In the described provider-network case (Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards.), it supports the planned action: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Incorrect Answers

A:

This alternative proposes: EVPN all-active or single-active multihoming uses a shared ESI and appropriate DF/aliasing coordination to prevent BUM duplication and maintain reachable paths under failure. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

C:

This alternative proposes: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

D:

This alternative proposes: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

Question 158

A Juniper service-provider engineer needs decisive verification evidence for this situation. Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers.
  2. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  3. Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
  4. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.

Explanation

Correct Answer

D:

In the stated situation (Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards.), the intended acceptance outcome is: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.

Incorrect Answers

A:

This alternative proposes: Inspect show ospf neighbor detail, interface MTU, hello/dead timers, authentication, area settings, and database exchange errors on both routers. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

B:

This alternative proposes: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

C:

This alternative proposes: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

Question 159

A service-provider acceptance team reviews the result of a provider-service change. Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. The intended verification is: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
  2. A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
  3. The intended remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
  4. Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.

Explanation

Correct Answer

D:

The verified success outcome is: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. Confirm this by: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Incorrect Answers

A:

That option concerns BGP export import policy and prefix controls. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

B:

That option concerns BGP FlowSpec validation and filtering boundaries. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

C:

That option concerns Interprovider Layer 3 VPN options and carrier of carriers. The related controlled intervention is: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.

Question 160

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Assume every route present in bgp.l3vpn.0 is automatically installed into every customer's instance.inet.0 regardless of import policies.
  2. Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
  3. Assume ordinary iBGP peers will automatically pass their learned routes to every other iBGP peer without a route reflector or full mesh.
  4. 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: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.

Incorrect Answers

A:

This alternative proposes: Assume every route present in bgp.l3vpn.0 is automatically installed into every customer's instance.inet.0 regardless of import policies. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.

B:

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 BGP route reflectors originator and cluster loop prevention.

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 BGP route reflectors originator and cluster loop prevention.

Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests