McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 43

Question 420

At fictional Seabrook Metro 105, a regional service-provider network, during a preproduction design validation, operations observes: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Which failure consequence follows most closely from ignoring this issue?

  1. Unwanted routes may alter forwarding or create customer traffic leakage.
  2. IPv6 customers lose external paths despite healthy IPv4 peering.
  3. MPLS traffic cannot use the planned engineered transport path.
  4. Undetected route oscillation harms network stability.

Explanation

Correct Answer

D:

Undetected route oscillation harms network stability. An established BGP session does not by itself establish which received path will be preferred. Inspect full route attributes and the BGP decision outcome for all candidate paths.

Incorrect Answers

A:

Unwanted routes may alter forwarding or create customer traffic leakage. The choice would be appropriate if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Here, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

B:

IPv6 customers lose external paths despite healthy IPv4 peering. That option concerns an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. The problem here is different: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

C:

MPLS traffic cannot use the planned engineered transport path. It addresses a different problem: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Here, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

Question 421

In a separate fictional JNCIS-SP lab review for Northpoint Access 106, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. What intervention most directly restores the intended routing or switching behavior?

  1. Restore deliberate local-preference assignment and check selected egress paths.
  2. Inspect full route attributes and the BGP decision outcome for all candidate paths.
  3. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy.
  4. Reconcile path MTU with the encapsulation overhead and test representative maximum frames.

Explanation

Correct Answer

B:

Inspect full route attributes and the BGP decision outcome for all candidate paths. The path comparison identifies the deciding attributes and final active candidate. An established BGP session does not by itself establish which received path will be preferred.

Incorrect Answers

A:

Restore deliberate local-preference assignment and check selected egress paths. This addresses a situation in which a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; however, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

C:

Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. That option concerns an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. The problem here is different: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

D:

Reconcile path MTU with the encapsulation overhead and test representative maximum frames. It addresses a different problem: A service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. Here, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

Question 422

In a separate fictional JNCIS-SP lab review for Northpoint Access 106, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Which networking principle explains why the proposed correction is appropriate?

  1. BGP route stability depends on both peer health and consistent route advertisements.
  2. BGP route limits help contain unexpected prefix-volume changes from a neighbor.
  3. An established BGP session does not by itself establish which received path will be preferred.
  4. IS-IS levels separate routing scope and require a deliberate interlevel reachability design.

Explanation

Correct Answer

C:

An established BGP session does not by itself establish which received path will be preferred. The path comparison identifies the deciding attributes and final active candidate. Inspect full route attributes and the BGP decision outcome for all candidate paths.

Incorrect Answers

A:

BGP route stability depends on both peer health and consistent route advertisements. That relates to circumstances in which an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Here the problem is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

B:

BGP route limits help contain unexpected prefix-volume changes from a neighbor. This addresses a situation in which a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale; however, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

D:

IS-IS levels separate routing scope and require a deliberate interlevel reachability design. That option concerns an L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change. The problem here is different: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

Question 423

In a separate fictional JNCIS-SP lab review for Northpoint Access 106, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Which validation result would confirm the design is now functioning?

  1. A transport test reaches the peer and the BGP state advances to Established.
  2. The forbidden test prefix is rejected while approved prefixes are accepted.
  3. The route table and forwarding lookup show the expected metric-driven next hop.
  4. The path comparison identifies the deciding attributes and final active candidate.

Explanation

Correct Answer

D:

The path comparison identifies the deciding attributes and final active candidate. Inspect full route attributes and the BGP decision outcome for all candidate paths. An established BGP session does not by itself establish which received path will be preferred.

Incorrect Answers

A:

A transport test reaches the peer and the BGP state advances to Established. It is useful for situations where a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable; the reported fault, though, is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

B:

The forbidden test prefix is rejected while approved prefixes are accepted. That relates to circumstances in which a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. Here the problem is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

C:

The route table and forwarding lookup show the expected metric-driven next hop. This addresses a situation in which the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change; however, a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

Question 424

In a separate fictional JNCIS-SP lab review for Northpoint Access 106, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. What likely service impact does this condition create?

  1. A supposedly restrictive policy inadvertently advertises internal routes.
  2. A route loop or false path preference persists due to misdiagnosis.
  3. Sensitive application traffic bypasses the required upstream inspection or transit path.
  4. Undetected route oscillation harms network stability.

Explanation

Correct Answer

D:

Undetected route oscillation harms network stability. Inspect full route attributes and the BGP decision outcome for all candidate paths. An established BGP session does not by itself establish which received path will be preferred.

Incorrect Answers

A:

A supposedly restrictive policy inadvertently advertises internal routes. This relates to a case where a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through; the current situation is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

B:

A route loop or false path preference persists due to misdiagnosis. It is useful for situations where an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path; the reported fault, though, is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

C:

Sensitive application traffic bypasses the required upstream inspection or transit path. That relates to circumstances in which a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Here the problem is that a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored.

Question 425

At fictional Linden Point 107, a regional service-provider network, during a core-routing acceptance test, operations observes: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Which configuration or operational correction most directly addresses this failure?

  1. Inspect full route attributes and the BGP decision outcome for all candidate paths.
  2. Repair transport routing and source-address selection before modifying BGP policy.
  3. Perform controlled LSP validation and only then switch the authorized service resolution.
  4. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.

Explanation

Correct Answer

D:

Review negotiated hold time and keepalive settings alongside transport health, then correct the design. BGP peers use negotiated timers to detect failed sessions and maintain liveness. The BGP session stays Established across a stability window with predictable negotiated timers.

Incorrect Answers

A:

Inspect full route attributes and the BGP decision outcome for all candidate paths. This could help if a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored, but not when a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

B:

Repair transport routing and source-address selection before modifying BGP policy. This relates to a case where a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable; the current situation is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

C:

Perform controlled LSP validation and only then switch the authorized service resolution. It is useful for situations where a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; the reported fault, though, is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Question 426

At fictional Linden Point 107, a regional service-provider network, during a core-routing acceptance test, operations observes: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Which Junos forwarding or control-plane rule applies to this case?

  1. BGP communities label routes for policy decisions only when a policy uses those labels.
  2. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.
  3. BGP peers use negotiated timers to detect failed sessions and maintain liveness.
  4. MPLS TTL handling can affect the hop visibility of path diagnostics.

Explanation

Correct Answer

C:

BGP peers use negotiated timers to detect failed sessions and maintain liveness. Review negotiated hold time and keepalive settings alongside transport health, then correct the design. The BGP session stays Established across a stability window with predictable negotiated timers.

Incorrect Answers

A:

BGP communities label routes for policy decisions only when a policy uses those labels. It is relevant if an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning, but the reported issue is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

B:

Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. This could help if a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset, but not when a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

D:

MPLS TTL handling can affect the hop visibility of path diagnostics. It is useful for situations where traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut; the reported fault, though, is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Question 427

At fictional Linden Point 107, a regional service-provider network, during a core-routing acceptance test, operations observes: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. What operational evidence best establishes successful remediation?

  1. The expected customer prefix appears in the advertised-route output and unintended prefixes do not.
  2. IPv6 prefixes appear in the correct BGP table with resolvable next hops.
  3. The BGP session stays Established across a stability window with predictable negotiated timers.
  4. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links.

Explanation

Correct Answer

C:

The BGP session stays Established across a stability window with predictable negotiated timers. BGP peers use negotiated timers to detect failed sessions and maintain liveness. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.

Incorrect Answers

A:

The expected customer prefix appears in the advertised-route output and unintended prefixes do not. This is applicable when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; the present condition is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

B:

IPv6 prefixes appear in the correct BGP table with resolvable next hops. It is relevant if an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled, but the reported issue is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

D:

A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. This relates to a case where a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed; the current situation is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Question 428

At fictional Linden Point 107, a regional service-provider network, during a core-routing acceptance test, operations observes: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Which operational harm would persist without the intended correction?

  1. Policy and reachability behavior is distorted by a false external session.
  2. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.
  3. Subscriber VLANs collide or customer traffic arrives in the wrong service.
  4. Repeated control-plane resets withdraw customer routes.

Explanation

Correct Answer

D:

Repeated control-plane resets withdraw customer routes. BGP peers use negotiated timers to detect failed sessions and maintain liveness. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.

Incorrect Answers

A:

Policy and reachability behavior is distorted by a false external session. That could help when an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary; here, a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

B:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. This is applicable when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; the present condition is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

C:

Subscriber VLANs collide or customer traffic arrives in the wrong service. It is relevant if provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag, but the reported issue is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Question 429

In a separate fictional JNCIS-SP lab review for Harborview ISP 108, a carrier-edge and core routing team, following a monitored network change window, engineers find: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. What should the Junos specialist change first to resolve this specific fault?

  1. Fix the peer export policy match for the authorized prefix and verify the announced routes.
  2. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.
  3. Inspect full route attributes and the BGP decision outcome for all candidate paths.
  4. Inspect database-exchange state and repair the adjacency rather than editing unrelated route preferences.

Explanation

Correct Answer

B:

Review negotiated hold time and keepalive settings alongside transport health, then correct the design. The BGP session stays Established across a stability window with predictable negotiated timers. BGP peers use negotiated timers to detect failed sessions and maintain liveness.

Incorrect Answers

A:

Fix the peer export policy match for the authorized prefix and verify the announced routes. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

C:

Inspect full route attributes and the BGP decision outcome for all candidate paths. This is applicable when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; the present condition is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

D:

Inspect database-exchange state and repair the adjacency rather than editing unrelated route preferences. It is relevant if two supposed adjacent routers have different views of a backbone link because database synchronization never completes, but the reported issue is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Question 430

In a separate fictional JNCIS-SP lab review for Harborview ISP 108, a carrier-edge and core routing team, following a monitored network change window, engineers find: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. What technical principle underlies the right remedy?

  1. BGP peers use negotiated timers to detect failed sessions and maintain liveness.
  2. Junos BGP exports only routes accepted by the applicable export policy.
  3. Route reflectors distribute selected IBGP reachability within the configured client topology.
  4. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions.

Explanation

Correct Answer

A:

BGP peers use negotiated timers to detect failed sessions and maintain liveness. The BGP session stays Established across a stability window with predictable negotiated timers. Review negotiated hold time and keepalive settings alongside transport health, then correct the design.

Incorrect Answers

B:

Junos BGP exports only routes accepted by the applicable export policy. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

C:

Route reflectors distribute selected IBGP reachability within the configured client topology. That could help when an internal client learns routes from another client only intermittently after the route-reflector peering address changes; here, a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

D:

Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. This is applicable when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; the present condition is that a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests