Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 290

The on-call engineer at Copperwick Markets receives this fault report: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. What initial check best isolates the actual failing protocol stage?

  1. Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
  2. Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
  3. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
  4. Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.

Correct answer: A

Explanation of each choice

A.

Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence. A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.

B.

The check diagnoses a different layer of service. Its source issue is: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. The relevant initial check is: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.

C.

This check may help with another root cause, for example: A new higher-priority router joins an IS-IS LAN but the team expects OSPF's DR/BDR rules and cannot explain the pseudonode origin. It does not test the first failed condition; start with: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. Instead inspect: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.

Question 291

The provider operations team at Harborline Transit reports: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. Which implementation decision best corrects the cause?

  1. Enable supported BGP multipath for the intended group and verify the installed forwarding next-hop set under the required path-eligibility constraints.
  2. Set a suitable higher BGP local preference on the desired imported egress route and propagate it consistently inside the AS.
  3. Attach and match the intended BGP community through correctly ordered routing policy, and validate propagation and neighbor policy handling.
  4. Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

Correct answer: D

Explanation of each choice

A.

That would address a separate configuration fault: Two equal eligible BGP paths to a destination exist, but forwarding uses only the best path while the service design needs shared capacity. This stem identifies a different cause, corrected by: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

B.

This action may apply to a different problem, for example: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. It does not repair the stated failure boundary. The case-specific reason is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

C.

The other action is relevant when A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. The current case instead requires: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required. The distinction is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

D.

Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required. The case-specific reason is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference. A direct acceptance test is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

Question 292

During a post-change check at Harborline Transit, the original condition was: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. What evidence would validate the corrected behavior?

  1. The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
  2. The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
  3. The exact BGP path becomes active once its next hop resolves and the forwarding table has a usable adjacency or recursive next hop.
  4. The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

Correct answer: D

Explanation of each choice

A.

That check proves something else, such as: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. It could pass while the stated problem remains. The targeted evidence here is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

B.

This would be valid for another situation: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. It does not establish that the failing boundary in this scenario works; verify: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

C.

The observation confirms a different component's behavior. Its source context is: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. In this case the success criterion is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

D.

The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated. A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

Question 293

At Harborline Transit, an engineer is asked to explain this case: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. Which underlying routing or switching principle accounts for the appropriate solution?

  1. Ordered Junos BGP export policies determine which eligible local routes are advertised to a BGP group or neighbor.
  2. A BGP route must have a resolvable next hop before it can become active and install usable forwarding state.
  3. BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment.
  4. Junos BGP import policy screens and modifies routes as they enter BGP route consideration rather than controlling what the local router advertises outward.

Correct answer: C

Explanation of each choice

A.

The statement can be true when A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. But it does not explain the reported failure. Here: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

B.

That principle belongs to a different service stage: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. The directly relevant mechanism is: BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment.

C.

BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment. The key distinction is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference. Accordingly the remedy is: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

D.

The statement can be true when A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. But it does not explain the reported failure. Here: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

Question 294

A risk assessment at Harborline Transit identifies: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. Which practical consequence is most specifically tied to this failure?

  1. An unresolvable BGP route may be received but never forwarded, making the prefix unreachable to customers.
  2. Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.
  3. Unwanted prefixes can become active, or intended reachability can be lost if a legitimate route is rejected at import.
  4. Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.

Correct answer: B

Explanation of each choice

A.

The concern could occur elsewhere when A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. For the stated scenario, the immediate risk is: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

B.

Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed. The direct mitigation is: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

C.

It is a risk in another topology or protocol state: A provider receives a malformed or unauthorized customer prefix yet it enters route selection after a loose import policy. Here the most direct failure path is: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

D.

The concern could occur elsewhere when A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. For the stated scenario, the immediate risk is: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

Question 295

The on-call engineer at Harborline Transit receives this fault report: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. What initial check best isolates the actual failing protocol stage?

  1. Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
  2. Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference.
  3. Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route.
  4. Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

Correct answer: D

Explanation of each choice

A.

This check may help with another root cause, for example: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. It does not test the first failed condition; start with: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

B.

That evidence could be normal while the reported defect persists. It is aimed at: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. Instead inspect: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

C.

The check diagnoses a different layer of service. Its source issue is: A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. The relevant initial check is: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

D.

Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability. A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

Question 296

A production change request at Firthbank Medical includes this finding: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. What should the engineer change to address it?

  1. Attach and match the intended BGP community through correctly ordered routing policy, and validate propagation and neighbor policy handling.
  2. Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.
  3. Use an appropriate externally communicated MED or an agreed inbound routing policy and verify the neighbor's comparison behavior and limitations.
  4. Constrain Junos BGP export terms to approved active prefixes and attributes, preserving explicit accept/reject behavior for the neighbor.

Correct answer: B

Explanation of each choice

A.

The other action is relevant when A neighbor's agreed selective-routing behavior fails because a community is added after the rejecting export term rather than before policy selection. The current case instead requires: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required. The distinction is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

B.

Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required. The case-specific reason is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference. A direct acceptance test is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

C.

This action may apply to a different problem, for example: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. It does not repair the stated failure boundary. The case-specific reason is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

D.

The other action is relevant when A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. The current case instead requires: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required. The distinction is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

Question 297

After Firthbank Medical applies its proposed fix to this problem — A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. — which observation best proves the specific failure has been resolved?

  1. The required internal BGP speakers receive routes across the topology without iBGP re-advertisement violations or looped next hops.
  2. The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.
  3. Best-path output shows the anticipated winner with equal preceding attributes and the intended AS-path length or policy influence.
  4. Received or advertised route detail shows the agreed community on the exact prefixes, and downstream policy actions match its value.

Correct answer: B

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A provider adds more iBGP speakers without a route-reflector or full-mesh design and assumes iBGP will transitively flood routes. In this case the success criterion is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

B.

The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated. A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

C.

This would be valid for another situation: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. It does not establish that the failing boundary in this scenario works; verify: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

D.

The observation confirms a different component's behavior. Its source context is: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. In this case the success criterion is: The BGP TCP session establishes, OPEN negotiation accepts the correct AS information and the peer reaches Established before routes are evaluated.

Question 298

An architecture review at Firthbank Medical examines the following symptom: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. What Junos or protocol mechanism is most directly responsible?

  1. Junos BGP import policy screens and modifies routes as they enter BGP route consideration rather than controlling what the local router advertises outward.
  2. BGP communities are transitive policy tags when preserved and permitted; they do not themselves impose forwarding without route-policy interpretation.
  3. BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment.
  4. BGP local preference is carried within an autonomous system and favors larger values for route selection; it is not advertised to external eBGP peers.

Correct answer: C

Explanation of each choice

A.

This explains a separate protocol behavior: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. In the current facts, the controlling mechanism is: BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment.

B.

The statement can be true when A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. But it does not explain the reported failure. Here: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

C.

BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment. The key distinction is: A session that fails at peer AS negotiation is not repaired by changing route export community or local preference. Accordingly the remedy is: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

D.

This explains a separate protocol behavior: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. In the current facts, the controlling mechanism is: BGP session establishment uses a TCP connection followed by OPEN capability and AS checks; a wrong peer-as prevents normal establishment.

Question 299

The team at Firthbank Medical defers a fix for this condition: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. What failure is most likely if no targeted control is applied?

  1. Traffic may exit through the wrong carrier, producing inconsistent routing or unwanted transit cost across the AS.
  2. Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.
  3. Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
  4. Parts of the AS can lack routes despite each router having some established iBGP neighbors.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. Here the most direct failure path is: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

B.

Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed. The direct mitigation is: Set the correct local/peer AS relationship and neighbor addressing for the eBGP group, ensuring port 179 connectivity as required.

C.

That consequence is more closely associated with another deficiency, such as: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. The described fault instead exposes: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

D.

It is a risk in another topology or protocol state: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. Here the most direct failure path is: Routes are never exchanged with the partner, even if ICMP reachability tests across the physical link succeed.

Question 300

During provider troubleshooting at Firthbank Medical, this symptom is observed: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. Which targeted inspection should precede remediation?

  1. Check outbound advertised path attributes and the remote neighbor's policy and MED comparison rules rather than assuming remote local preference.
  2. Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.
  3. Inspect the received route's next-hop field and `show route <next-hop>` resolution path, then check the IGP transport route.
  4. Compare best paths and local-preference values for the exact prefix on internal speakers and identify the import policy setting it.

Correct answer: B

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. The relevant initial check is: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

B.

Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability. A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. Instead inspect: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

D.

The check diagnoses a different layer of service. Its source issue is: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. The relevant initial check is: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports