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 20

Question 190

Before changing configuration at Cloverbank Mobile, an engineer investigates: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Which first diagnostic most directly tests the suspected cause?

  1. Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
  2. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  3. Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
  4. Compare `show ospf neighbor` with both interfaces' configured timers and a Hello packet capture before changing routing import policies.

Correct answer: A

Explanation of each choice

A.

Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs. Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.

B.

That evidence could be normal while the reported defect persists. It is aimed at: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Instead inspect: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.

C.

The check diagnoses a different layer of service. Its source issue is: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. The relevant initial check is: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.

D.

This check may help with another root cause, for example: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. It does not test the first failed condition; start with: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.

Question 191

At Northline Communications, a service provider router shows this failure: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. What is the best targeted configuration or operations action?

  1. Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.
  2. Verify the broadcast-network DR/BDR roles and adjacency expectations, and plan a controlled election transition if a DR change is required.
  3. Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
  4. Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.

Correct answer: C

Explanation of each choice

A.

The other action is relevant when After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

B.

That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

C.

Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. A direct acceptance test is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

D.

The other action is relevant when An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

Question 192

A change auditor at Northline Communications must validate remediation of this finding: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. 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. Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
  3. The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.
  4. The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

Correct answer: D

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. In this case the success criterion is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

B.

That check proves something else, such as: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. It could pass while the stated problem remains. The targeted evidence here is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

C.

This would be valid for another situation: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. It does not establish that the failing boundary in this scenario works; verify: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

D.

The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

Question 193

The operations training team at Northline Communications discusses this issue: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which technical explanation matches the intended correction?

  1. OSPF uses a logical 32-bit Router ID to identify LSA originators and adjacency participants, independent of physical interface address numbering.
  2. OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
  3. OSPF Hello parameters must match across neighbors for adjacency formation; IP reachability alone does not establish an OSPF relationship.
  4. OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.

Correct answer: B

Explanation of each choice

A.

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 database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

B.

OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery. The key distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. Accordingly the remedy is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

C.

That principle belongs to a different service stage: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

D.

This explains a separate protocol behavior: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. In the current facts, the controlling mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

Question 194

At Northline Communications, a service acceptance review considers the unresolved issue: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which operational exposure follows most directly?

  1. The control-plane adjacency never stabilizes, leaving reachability dependent on stale or alternate routes despite a functioning physical link.
  2. The router can calculate a path from incomplete or stale link-state information, creating asymmetric reachability or loops during convergence.
  3. Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.
  4. Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

Correct answer: D

Explanation of each choice

A.

It is a risk in another topology or protocol state: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. Here the most direct failure path is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

B.

The concern could occur elsewhere when A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. For the stated scenario, the immediate risk is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

C.

That consequence is more closely associated with another deficiency, such as: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. The described fault instead exposes: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

D.

Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity. The direct mitigation is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

Question 195

Before changing configuration at Northline Communications, an engineer investigates: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which first diagnostic most directly tests the suspected cause?

  1. Compare `show ospf neighbor` with both interfaces' configured timers and a Hello packet capture before changing routing import policies.
  2. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  3. Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
  4. Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

Correct answer: D

Explanation of each choice

A.

This check may help with another root cause, for example: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

B.

This check may help with another root cause, for example: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

C.

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: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

D.

Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

Question 196

During a Junos network change at Briarfield Healthcare, the engineer observes: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which remediation most directly fixes the described problem?

  1. Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
  2. Check LSDB synchronization and required LSA flooding within the affected area, repairing the source or adjacency problem responsible for stale advertisements.
  3. Trace OSPF database description, link-state request/update and acknowledgment packets during adjacency initialization, then fix the precise exchange failure.
  4. Inspect the relevant router, network, summary, and external LSA types and repair the correct ABR or ASBR advertisement scope.

Correct answer: A

Explanation of each choice

A.

Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. A direct acceptance test is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

B.

The other action is relevant when An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

C.

That would address a separate configuration fault: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. This stem identifies a different cause, corrected by: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

D.

This action may apply to a different problem, for example: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. It does not repair the stated failure boundary. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

Question 197

The Junos team at Briarfield Healthcare needs a success criterion for this defect: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which observed result most precisely confirms the intended repair?

  1. The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.
  2. The neighboring LSDB contains unique router-LSA origins, adjacencies converge and the configured router identity persists across interface changes.
  3. Expected interarea or external reachability appears with the appropriate LSA origin and type, while area-local topology LSAs remain scoped correctly.
  4. The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

Correct answer: D

Explanation of each choice

A.

This would be valid for another situation: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. It does not establish that the failing boundary in this scenario works; verify: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

B.

The observation confirms a different component's behavior. Its source context is: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. In this case the success criterion is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

C.

That check proves something else, such as: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. It could pass while the stated problem remains. The targeted evidence here is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

D.

The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

Question 198

While analyzing a service failure at Briarfield Healthcare, the following is observed: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. OSPF Hello packets discover neighbors; DD packets summarize LSDBs; requests, updates and acknowledgments reconcile link-state contents.
  2. Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
  3. OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
  4. OSPF derives SPF paths from its area LSDB; Hellos alone do not prove that database exchange and flooding completed correctly.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

B.

This explains a separate protocol behavior: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. In the current facts, the controlling mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

C.

OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery. The key distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. Accordingly the remedy is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

D.

That principle belongs to a different service stage: An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.

Question 199

The following provider defect remains uncorrected at Briarfield Healthcare: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. What is the most direct service or security risk of leaving it unresolved?

  1. Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.
  2. Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
  3. Misinterpreting normal two-way neighbors can trigger unnecessary outages or lead to an improperly managed DR transition.
  4. The team can diagnose the wrong flood scope and either miss external reachability or leak a route where it was not intended.

Correct answer: B

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The described fault instead exposes: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

B.

Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity. The direct mitigation is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.

C.

The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

D.

That consequence is more closely associated with another deficiency, such as: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The described fault instead exposes: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.

Question 200

A support escalation at Briarfield Healthcare describes: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Where should the Junos operator look first for decisive evidence?

  1. Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
  2. Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
  3. Compare `show ospf neighbor` with both interfaces' configured timers and a Hello packet capture before changing routing import policies.
  4. Compare advertised link metrics and calculated route costs across both alternatives, rather than changing Junos inter-protocol route preference.

Correct answer: A

Explanation of each choice

A.

Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.

B.

The check diagnoses a different layer of service. Its source issue is: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The relevant initial check is: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

C.

This check may help with another root cause, for example: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

D.

That evidence could be normal while the reported defect persists. It is aimed at: Traffic prefers a slow OSPF path despite a faster link because manual interface costs reverse the intended SPF ranking. Instead inspect: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.

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