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 21

Question 200

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions.
  2. Point a BGP neighbor at a remote loopback across three routers without supporting multihop or an IGP/static route and call the repeated Connect state a BGP software defect.
  3. Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
  4. Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU.

Explanation

Correct Answer

B:

That conflicts with the edge-to-cloud principle: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.

Incorrect Answers

A:

This alternative proposes: Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.

C:

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 external multihop and loopback peer reachability.

D:

This alternative proposes: Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.

Question 201

A Junos service-provider routing engineer investigates the following routing and service incident: A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
  2. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
  3. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
  4. Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.

Explanation

Correct Answer

B:

The case-specific routing and services action is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. The governing Junos routing/service principle is: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.

Incorrect Answers

A:

This alternative proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP flap damping penalties and recovery.

C:

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 flap damping penalties and recovery.

D:

This alternative proposes: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 202

A provider routing design review considers this situation. A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect. A colleague proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. Which technical principle BEST supports that action? Select ONE best answer.

  1. 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.
  2. Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.
  3. BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
  4. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. In the described provider-network case (A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect.), it supports the planned action: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Incorrect Answers

A:

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 BGP flap damping penalties and recovery.

C:

This alternative proposes: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP flap damping penalties and recovery.

D:

This alternative proposes: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 203

A Juniper service-provider engineer needs decisive verification evidence for this situation. A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  2. Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
  3. Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state.
  4. Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.

Explanation

Correct Answer

B:

The direct discriminating observation is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. In the stated situation (A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect.), the intended acceptance outcome is: After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.

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 flap damping penalties and recovery.

C:

This alternative proposes: Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue BGP flap damping penalties and recovery.

D:

This alternative proposes: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 204

A service-provider acceptance team reviews the result of a provider-service change. A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect. The intended verification is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.
  2. Access routers learn only authorized leaked routes, continue using their correct area exit and do not create interlevel routing loops.
  3. Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
  4. After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.

Explanation

Correct Answer

D:

The verified success outcome is: After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes. Confirm this by: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.

Incorrect Answers

A:

That option concerns BGP communities and selective transit routing policy. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

B:

That option concerns IS-IS Level 2 to Level 1 route leaking and summaries. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

C:

This alternative proposes: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 205

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A multihomed customer's /24 flaps during fiber repair and remains hidden after physical restoration because damping suppression is still in effect. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions.
  2. Configure aggressive route damping globally and assume any withdrawn customer prefix instantly becomes available after its neighbor comes back up.
  3. Point a BGP neighbor at a remote loopback across three routers without supporting multihop or an IGP/static route and call the repeated Connect state a BGP software defect.
  4. Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU.

Explanation

Correct Answer

B:

That conflicts with the edge-to-cloud principle: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.

Incorrect Answers

A:

This alternative proposes: Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP flap damping penalties and recovery.

C:

This alternative proposes: Point a BGP neighbor at a remote loopback across three routers without supporting multihop or an IGP/static route and call the repeated Connect state a BGP software defect. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP flap damping penalties and recovery.

D:

This alternative proposes: Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 206

A Junos service-provider routing engineer investigates the following routing and service incident: A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
  2. Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
  3. 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.
  4. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Explanation

Correct Answer

D:

The case-specific routing and services action is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. The governing Junos routing/service principle is: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. Verify the decision through: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.

Incorrect Answers

A:

This alternative proposes: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP flap damping penalties and recovery.

B:

This alternative proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP flap damping penalties and recovery.

C:

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 BGP flap damping penalties and recovery.

Question 207

A provider routing design review considers this situation. A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. A colleague proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. Which technical principle BEST supports that action? Select ONE best answer.

  1. IS-IS wide metrics support extended values and modern topology use cases, but cost selection depends on configured interface metrics and supported protocol behavior.
  2. Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.
  3. BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
  4. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. In the described provider-network case (A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability.), it supports the planned action: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Incorrect Answers

A:

This alternative proposes: IS-IS wide metrics support extended values and modern topology use cases, but cost selection depends on configured interface metrics and supported protocol behavior. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue BGP flap damping penalties and recovery.

C:

This alternative proposes: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP flap damping penalties and recovery.

D:

This alternative proposes: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 208

A Juniper service-provider engineer needs decisive verification evidence for this situation. A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
  2. Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
  3. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  4. Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.

Explanation

Correct Answer

A:

The direct discriminating observation is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. In the stated situation (A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability.), the intended acceptance outcome is: After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.

Incorrect Answers

B:

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 flap damping penalties and recovery.

C:

This alternative proposes: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP flap damping penalties and recovery.

D:

This alternative proposes: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue BGP flap damping penalties and recovery.

Question 209

A service-provider acceptance team reviews the result of a provider-service change. A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. The intended verification is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. 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. Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
  3. Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
  4. The appropriate designated and backup routers maintain required adjacencies and exchange reachability across the shared Ethernet without unnecessary resets.

Explanation

Correct Answer

A:

The verified success outcome is: After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes. Confirm this by: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Incorrect Answers

B:

That option concerns BGP export import policy and prefix controls. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

C:

That option concerns BGP multipath equal cost and per-flow forwarding. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

D:

That option concerns OSPF designated router election on a multiaccess segment. The related controlled intervention is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

Question 210

A Junos service-provider routing engineer investigates this service-provider network scenario. A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. 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. Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
  3. Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
  4. Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
  5. 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.

Explanation

Correct Answers

B:

The case-specific routing and services action is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.

C:

The direct discriminating observation is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.

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 flap damping penalties and recovery.

D:

This alternative proposes: Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue BGP flap damping penalties and recovery.

E:

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 flap damping penalties and recovery.

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