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 40

Question 390

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 098, a carrier-edge and core routing team, following a monitored network change window, engineers find: An IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. Which networking principle explains why the proposed correction is appropriate?

  1. BGP address-family negotiation determines which network-layer reachability data can be exchanged.
  2. Junos BGP exports only routes accepted by the applicable export policy.
  3. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.
  4. Junos directly connected reachability depends on active logical interface configuration and state.

Explanation

Correct Answer

C:

A BGP path cannot be installed for forwarding when its next hop cannot be resolved. The BGP route becomes active and the next hop resolves to a reachable core interface. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy.

Incorrect Answers

A:

BGP address-family negotiation determines which network-layer reachability data can be exchanged. 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 an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

B:

Junos BGP exports only routes accepted by the applicable export policy. This could help if a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it, but not when an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

D:

Junos directly connected reachability depends on active logical interface configuration and state. It is useful for situations where a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; the reported fault, though, is that an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

Question 391

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 098, a carrier-edge and core routing team, following a monitored network change window, engineers find: An IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. Which validation result would confirm the design is now functioning?

  1. The intended EBGP neighbor becomes Established and exchanges authorized prefixes.
  2. Tagged prefixes receive the documented policy action and untagged routes are unaffected.
  3. The BGP route becomes active and the next hop resolves to a reachable core interface.
  4. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary.

Explanation

Correct Answer

C:

The BGP route becomes active and the next hop resolves to a reachable core interface. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.

Incorrect Answers

A:

The intended EBGP neighbor becomes Established and exchanges authorized prefixes. This is applicable when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS; the present condition is that an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

B:

Tagged prefixes receive the documented policy action and untagged routes are unaffected. 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 an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

D:

The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. This relates to a case where an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the current situation is that an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

Question 392

In a separate fictional JNCIS-SP lab review for Stonefield Telecom 098, a carrier-edge and core routing team, following a monitored network change window, engineers find: An IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. What likely service impact does this condition create?

  1. Repeated control-plane resets withdraw customer routes.
  2. Services remain blackholed despite a received BGP update.
  3. Unwanted routes may alter forwarding or create customer traffic leakage.
  4. Duplicate identity produces unstable topology and confusing route calculations.

Explanation

Correct Answer

B:

Services remain blackholed despite a received BGP update. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.

Incorrect Answers

A:

Repeated control-plane resets withdraw customer routes. That could help when a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; here, an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

C:

Unwanted routes may alter forwarding or create customer traffic leakage. It is relevant if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy, but the reported issue is that an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

D:

Duplicate identity produces unstable topology and confusing route calculations. This could help if two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template, but not when an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability.

Question 393

At fictional Clearwater Peering 099, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. Which configuration or operational correction most directly addresses this failure?

  1. Restore deliberate local-preference assignment and check selected egress paths.
  2. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes.
  3. Fix the peer export policy match for the authorized prefix and verify the announced routes.
  4. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path.

Explanation

Correct Answer

A:

Restore deliberate local-preference assignment and check selected egress paths. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. Route detail shows intended local preference values and traffic exits through the designated link.

Incorrect Answers

B:

Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. That could help when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Fix the peer export policy match for the authorized prefix and verify the announced 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 customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. It is relevant if a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low, but the reported issue is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 394

At fictional Clearwater Peering 099, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. Which Junos forwarding or control-plane rule applies to this case?

  1. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.
  2. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.
  3. BGP import policy governs which learned prefixes enter local route selection.
  4. BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers.

Explanation

Correct Answer

A:

Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. Restore deliberate local-preference assignment and check selected egress paths. Route detail shows intended local preference values and traffic exits through the designated link.

Incorrect Answers

B:

A BGP path cannot be installed for forwarding when its next hop cannot be resolved. This could matter when an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. In this case, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

BGP import policy governs which learned prefixes enter local route selection. That could help when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. This is applicable when a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; the present condition is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 395

At fictional Clearwater Peering 099, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. What operational evidence best establishes successful remediation?

  1. The intended EBGP neighbor becomes Established and exchanges authorized prefixes.
  2. The suspect path is explained and only eligible loop-free routes are selected.
  3. The penultimate and egress forwarding entries match the intended label disposition.
  4. Route detail shows intended local preference values and traffic exits through the designated link.

Explanation

Correct Answer

D:

Route detail shows intended local preference values and traffic exits through the designated link. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. Restore deliberate local-preference assignment and check selected egress paths.

Incorrect Answers

A:

The intended EBGP neighbor becomes Established and exchanges authorized prefixes. That option concerns an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. The problem here is different: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

B:

The suspect path is explained and only eligible loop-free routes are selected. It addresses a different problem: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

The penultimate and egress forwarding entries match the intended label disposition. This could matter when an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. In this case, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 396

At fictional Clearwater Peering 099, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. Which operational harm would persist without the intended correction?

  1. Outbound traffic takes an expensive or congested transit link.
  2. Services remain blackholed despite a received BGP update.
  3. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.
  4. A false no-route diagnosis delays the actual IPv6 repair.

Explanation

Correct Answer

A:

Outbound traffic takes an expensive or congested transit link. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. Restore deliberate local-preference assignment and check selected egress paths.

Incorrect Answers

B:

Services remain blackholed despite a received BGP update. 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 customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. It addresses a different problem: A customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

A false no-route diagnosis delays the actual IPv6 repair. This could matter when a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised. In this case, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 397

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 100, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. What should the Junos specialist change first to resolve this specific fault?

  1. Apply the agreed route-limit safeguard and validate alerts and peer handling at controlled thresholds.
  2. Restore deliberate local-preference assignment and check selected egress paths.
  3. Inspect full route attributes and the BGP decision outcome for all candidate paths.
  4. Identify the ingress, transit, and egress LSR roles before modifying label rules.

Explanation

Correct Answer

B:

Restore deliberate local-preference assignment and check selected egress paths. Route detail shows intended local preference values and traffic exits through the designated link. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.

Incorrect Answers

A:

Apply the agreed route-limit safeguard and validate alerts and peer handling at controlled thresholds. This addresses a situation in which a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale; however, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Inspect full route attributes and the BGP decision outcome for all candidate paths. That option concerns a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. The problem here is different: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

Identify the ingress, transit, and egress LSR roles before modifying label rules. It addresses a different problem: A network test expects the ingress PE to swap a label that it should actually impose. Here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 398

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 100, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. What technical principle underlies the right remedy?

  1. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.
  2. BGP address-family negotiation determines which network-layer reachability data can be exchanged.
  3. Route reflectors distribute selected IBGP reachability within the configured client topology.
  4. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity.

Explanation

Correct Answer

A:

Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS. Route detail shows intended local preference values and traffic exits through the designated link. Restore deliberate local-preference assignment and check selected egress paths.

Incorrect Answers

B:

BGP address-family negotiation determines which network-layer reachability data can be exchanged. This addresses a situation in which an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; however, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Route reflectors distribute selected IBGP reachability within the configured client topology. The choice would be appropriate if an internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. That option concerns provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. The problem here is different: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 399

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 100, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. Which acceptance finding demonstrates the affected service has recovered?

  1. Peer details show the intended internal AS relationship and routes propagate by design.
  2. The source of withdrawals is identified and the prefix stays available during observation.
  3. Route lookup and sample packets both follow the intended egress circuit after convergence.
  4. Route detail shows intended local preference values and traffic exits through the designated link.

Explanation

Correct Answer

D:

Route detail shows intended local preference values and traffic exits through the designated link. Restore deliberate local-preference assignment and check selected egress paths. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.

Incorrect Answers

A:

Peer details show the intended internal AS relationship and routes propagate by design. It is useful for situations where an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary; the reported fault, though, is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

B:

The source of withdrawals is identified and the prefix stays available during observation. 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 customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Route lookup and sample packets both follow the intended egress circuit after convergence. This addresses a situation in which an engineer sees an OSPF route in the routing table and closes the incident without testing the egress path; however, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 400

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 100, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. What is the direct residual network risk if the fault remains unresolved?

  1. Outbound traffic takes an expensive or congested transit link.
  2. Attempts to fix policy distract from a network reachability failure.
  3. Undetected route oscillation harms network stability.
  4. Packets cannot reach the intended next hop despite a syntactically valid address.

Explanation

Correct Answer

A:

Outbound traffic takes an expensive or congested transit link. Restore deliberate local-preference assignment and check selected egress paths. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.

Incorrect Answers

B:

Attempts to fix policy distract from a network reachability failure. 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 customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Undetected route oscillation harms network stability. That relates to circumstances in which a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Here the problem is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

Packets cannot reach the intended next hop despite a syntactically valid address. This addresses a situation in which an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; however, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

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