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 15

Question 140

During provider troubleshooting at Cedar Coast Telecom, this symptom is observed: A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. Which targeted inspection should precede remediation?

  1. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  2. Compare advertised link metrics and calculated route costs across both alternatives, rather than changing Junos inter-protocol route preference.
  3. Compare `show ospf database` and LSA sequence/age for the exact origin across the neighboring routers and check adjacency database-exchange states.
  4. Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.

Correct answer: C

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. Instead inspect: Compare `show ospf database` and LSA sequence/age for the exact origin across the neighboring routers and check adjacency database-exchange states.

B.

The check diagnoses a different layer of service. Its source issue is: Traffic prefers a slow OSPF path despite a faster link because manual interface costs reverse the intended SPF ranking. The relevant initial check is: Compare `show ospf database` and LSA sequence/age for the exact origin across the neighboring routers and check adjacency database-exchange states.

C.

Compare `show ospf database` and LSA sequence/age for the exact origin across the neighboring routers and check adjacency database-exchange states. A consistent LSDB, not merely the presence of a Hello, is the control-plane evidence required to trust OSPF topology calculations.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. Instead inspect: Compare `show ospf database` and LSA sequence/age for the exact origin across the neighboring routers and check adjacency database-exchange states.

Question 141

A production change request at Orion Transit Exchange includes this finding: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. What should the engineer change to address it?

  1. Align the OSPF Hello and dead interval settings and other required adjacency parameters on both ends of the directly connected link.
  2. Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.
  3. Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.
  4. Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.

Correct answer: C

Explanation of each choice

A.

That would address a separate configuration fault: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. This stem identifies a different cause, corrected by: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

B.

This action may apply to a different problem, for example: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. It does not repair the stated failure boundary. The case-specific reason is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

C.

Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure. The case-specific reason is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization. A direct acceptance test is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

D.

That would address a separate configuration fault: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. This stem identifies a different cause, corrected by: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

Question 142

After Orion Transit Exchange applies its proposed fix to this problem — A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. — which observation best proves the specific failure has been resolved?

  1. The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
  2. Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
  3. The two peers exchange compatible Hellos, progress to a stable Full adjacency when appropriate, and advertise expected routes without repeated adjacency resets.
  4. Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

Correct answer: D

Explanation of each choice

A.

That check proves something else, such as: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. It could pass while the stated problem remains. The targeted evidence here is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

B.

This would be valid for another situation: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. It does not establish that the failing boundary in this scenario works; verify: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

C.

The observation confirms a different component's behavior. Its source context is: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. In this case the success criterion is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

D.

Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full. Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

Question 143

An architecture review at Orion Transit Exchange examines the following symptom: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. What Junos or protocol mechanism is most directly responsible?

  1. OSPF uses a logical 32-bit Router ID to identify LSA originators and adjacency participants, independent of physical interface address numbering.
  2. Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
  3. OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.
  4. OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. The directly relevant mechanism is: OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

B.

That principle belongs to a different service stage: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. The directly relevant mechanism is: OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

C.

OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents. The key distinction is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization. Accordingly the remedy is: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

D.

The statement can be true when A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. But it does not explain the reported failure. Here: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

Question 144

The team at Orion Transit Exchange defers a fix for this condition: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. What failure is most likely if no targeted control is applied?

  1. Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.
  2. Traffic can stay on a congested or expensive path even though links and adjacencies are healthy.
  3. Misinterpreting normal two-way neighbors can trigger unnecessary outages or lead to an improperly managed DR transition.
  4. Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

Correct answer: D

Explanation of each choice

A.

The concern could occur elsewhere when After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. For the stated scenario, the immediate risk is: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

B.

That consequence is more closely associated with another deficiency, such as: A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. The described fault instead exposes: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

C.

It is a risk in another topology or protocol state: On a broadcast multiaccess segment, engineers expect every pair of routers to form Full adjacencies and incorrectly diagnose normal two-way states. Here the most direct failure path is: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

D.

Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible. The direct mitigation is: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

Question 145

During provider troubleshooting at Orion Transit Exchange, this symptom is observed: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. Which targeted inspection should precede remediation?

  1. Inspect local and neighbor router IDs plus conflicting LSA originators before modifying OSPF interface cost or routing policy.
  2. Compare `show ospf neighbor` with both interfaces' configured timers and a Hello packet capture before changing routing import policies.
  3. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  4. Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

Correct answer: D

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. Instead inspect: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

B.

That evidence could be normal while the reported defect persists. It is aimed at: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. Instead inspect: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

C.

The check diagnoses a different layer of service. Its source issue is: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. The relevant initial check is: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

D.

Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress. Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

Question 146

At Baystone Energy, a service provider router shows this failure: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. What is the best targeted configuration or operations action?

  1. Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
  2. Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
  3. Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.
  4. Verify the broadcast-network DR/BDR roles and adjacency expectations, and plan a controlled election transition if a DR change is required.

Correct answer: C

Explanation of each choice

A.

The other action is relevant when A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. The current case instead requires: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure. The distinction is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

B.

That would address a separate configuration fault: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. This stem identifies a different cause, corrected by: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

C.

Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure. The case-specific reason is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization. A direct acceptance test is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

D.

The other action is relevant when On a broadcast multiaccess segment, engineers expect every pair of routers to form Full adjacencies and incorrectly diagnose normal two-way states. The current case instead requires: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure. The distinction is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

Question 147

A change auditor at Baystone Energy must validate remediation of this finding: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. Which test outcome is the strongest acceptance evidence?

  1. Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.
  2. The two peers exchange compatible Hellos, progress to a stable Full adjacency when appropriate, and advertise expected routes without repeated adjacency resets.
  3. Area routers hold consistent, current relevant LSAs and compute next hops consistent with the corrected topology after SPF runs.
  4. Expected interarea or external reachability appears with the appropriate LSA origin and type, while area-local topology LSAs remain scoped correctly.

Correct answer: A

Explanation of each choice

A.

Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full. Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

B.

That check proves something else, such as: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. It could pass while the stated problem remains. The targeted evidence here is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

C.

This would be valid for another situation: A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. It does not establish that the failing boundary in this scenario works; verify: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

D.

The observation confirms a different component's behavior. Its source context is: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. In this case the success criterion is: Database-description negotiation completes, missing LSAs are requested and updated, acknowledgments are received and the neighbor progresses to Full.

Question 148

The operations training team at Baystone Energy discusses this issue: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. Which technical explanation matches the intended correction?

  1. OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
  2. OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.
  3. Different OSPF LSA types describe router links, multiaccess networks, interarea summaries and redistributed external destinations.
  4. OSPF uses a logical 32-bit Router ID to identify LSA originators and adjacency participants, independent of physical interface address numbering.

Correct answer: B

Explanation of each choice

A.

This explains a separate protocol behavior: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. In the current facts, the controlling mechanism is: OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

B.

OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents. The key distinction is: Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization. Accordingly the remedy is: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

C.

That principle belongs to a different service stage: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. The directly relevant mechanism is: OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

D.

This explains a separate protocol behavior: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. In the current facts, the controlling mechanism is: OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

Question 149

At Baystone Energy, a service acceptance review considers the unresolved issue: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. Which operational exposure follows most directly?

  1. Misinterpreting normal two-way neighbors can trigger unnecessary outages or lead to an improperly managed DR transition.
  2. Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.
  3. Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
  4. An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A newly attached router with high priority fails to preempt an existing designated router, and the design team assumes priority alone forces immediate re-election. Here the most direct failure path is: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

B.

Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible. The direct mitigation is: Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

C.

That consequence is more closely associated with another deficiency, such as: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. The described fault instead exposes: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

D.

It is a risk in another topology or protocol state: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. Here the most direct failure path is: Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.

Question 150

Before changing configuration at Baystone Energy, an engineer investigates: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. Which first diagnostic most directly tests the suspected cause?

  1. Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.
  2. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  3. Compare advertised link metrics and calculated route costs across both alternatives, rather than changing Junos inter-protocol route preference.
  4. Inspect local and neighbor router IDs plus conflicting LSA originators before modifying OSPF interface cost or routing policy.

Correct answer: A

Explanation of each choice

A.

Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress. Different OSPF packet types have distinct adjacency functions; successful Hello discovery does not establish database synchronization.

B.

This check may help with another root cause, for example: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. It does not test the first failed condition; start with: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. Instead inspect: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

D.

The check diagnoses a different layer of service. Its source issue is: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. The relevant initial check is: Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

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