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 16

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.

Question 151

At Westhaven Software, a service provider router shows this failure: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. What is the best targeted configuration or operations action?

  1. Inspect the relevant router, network, summary, and external LSA types and repair the correct ABR or ASBR advertisement scope.
  2. Correct the relevant OSPF interface metric values and verify the resulting path costs and SPF next-hop choice.
  3. Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
  4. Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

Correct answer: D

Explanation of each choice

A.

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: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

B.

The other action is relevant when A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. The current case instead requires: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement. The distinction is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

C.

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: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

D.

Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement. The case-specific reason is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change. A direct acceptance test is: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

Question 152

A change auditor at Westhaven Software must validate remediation of this finding: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Which test outcome is the strongest acceptance evidence?

  1. Expected interarea or external reachability appears with the appropriate LSA origin and type, while area-local topology LSAs remain scoped correctly.
  2. The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.
  3. Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
  4. The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.

Correct answer: B

Explanation of each choice

A.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

B.

The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership. Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

C.

That check proves something else, such as: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. It could pass while the stated problem remains. The targeted evidence here is: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

D.

This would be valid for another situation: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. It does not establish that the failing boundary in this scenario works; verify: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

Question 153

The operations training team at Westhaven Software discusses this issue: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Which technical explanation matches the intended correction?

  1. OSPF Hello parameters must match across neighbors for adjacency formation; IP reachability alone does not establish an OSPF relationship.
  2. OSPF elects DR/BDR on multiaccess media to limit full adjacency and flooding complexity; elections are not automatically preemptive when a higher-priority router joins.
  3. OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.
  4. OSPF SPF compares additive path costs within its topology; configured interface metrics influence shortest-path selection once LSDB information is consistent.

Correct answer: C

Explanation of each choice

A.

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 areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

B.

This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

C.

OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies. The key distinction is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change. Accordingly the remedy is: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

D.

That principle belongs to a different service stage: A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. The directly relevant mechanism is: OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

Question 154

At Westhaven Software, a service acceptance review considers the unresolved issue: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Which operational exposure follows most directly?

  1. Neighbors can remain stalled before Full and fail to learn necessary topology even while periodic Hello packets are visible.
  2. Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.
  3. Traffic can stay on a congested or expensive path even though links and adjacencies are healthy.
  4. Duplicate protocol identities can corrupt LSDB origin assumptions and prevent predictable route computation or neighbor convergence.

Correct answer: B

Explanation of each choice

A.

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: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

B.

Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable. The direct mitigation is: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

C.

The concern could occur elsewhere when Traffic prefers a slow OSPF path despite a faster link because manual interface costs reverse the intended SPF ranking. For the stated scenario, the immediate risk is: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

D.

That consequence is more closely associated with another deficiency, such as: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. The described fault instead exposes: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

Question 155

Before changing configuration at Westhaven Software, an engineer investigates: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Which first diagnostic most directly tests the suspected cause?

  1. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  2. Inspect local and neighbor router IDs plus conflicting LSA originators before modifying OSPF interface cost or routing policy.
  3. Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
  4. Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

Correct answer: A

Explanation of each choice

A.

Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference. Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

B.

The check diagnoses a different layer of service. Its source issue is: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. The relevant initial check is: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

C.

This check may help with another root cause, 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 test the first failed condition; start with: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

D.

That evidence could be normal while the reported defect persists. It is aimed at: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. Instead inspect: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

Question 156

During a Junos network change at Eastvale MetroNet, the engineer observes: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. 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. Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
  3. Verify the broadcast-network DR/BDR roles and adjacency expectations, and plan a controlled election transition if a DR change is required.
  4. Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

Correct answer: D

Explanation of each choice

A.

That would address a separate configuration fault: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. This stem identifies a different cause, corrected by: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

B.

This action may apply to a different problem, for example: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. It does not repair the stated failure boundary. The case-specific reason is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

C.

The other action is relevant 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. The current case instead requires: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement. The distinction is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

D.

Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement. The case-specific reason is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change. A direct acceptance test is: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

Question 157

The Junos team at Eastvale MetroNet needs a success criterion for this defect: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. Which observed result most precisely confirms the intended repair?

  1. The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
  2. The two peers exchange compatible Hellos, progress to a stable Full adjacency when appropriate, and advertise expected routes without repeated adjacency resets.
  3. The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.
  4. Area routers hold consistent, current relevant LSAs and compute next hops consistent with the corrected topology after SPF runs.

Correct answer: C

Explanation of each choice

A.

That check proves something else, 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. It could pass while the stated problem remains. The targeted evidence here is: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

B.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

C.

The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership. Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

D.

That check proves something else, such as: An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. It could pass while the stated problem remains. The targeted evidence here is: The interface appears under the correct area, neighbors form there and expected interarea prefixes are present without duplicate area membership.

Question 158

While analyzing a service failure at Eastvale MetroNet, the following is observed: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. OSPF SPF compares additive path costs within its topology; configured interface metrics influence shortest-path selection once LSDB information is consistent.
  2. Different OSPF LSA types describe router links, multiaccess networks, interarea summaries and redistributed external destinations.
  3. Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
  4. OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

Correct answer: D

Explanation of each choice

A.

The statement can be true when A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. But it does not explain the reported failure. Here: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

B.

That principle belongs to a different service stage: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The directly relevant mechanism is: OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

C.

This explains a separate protocol behavior: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. In the current facts, the controlling mechanism is: OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies.

D.

OSPF areas scope LSDB flooding and use area border routers to exchange reachability between distinct area topologies. The key distinction is: Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change. Accordingly the remedy is: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

Question 159

The following provider defect remains uncorrected at Eastvale MetroNet: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. What is the most direct service or security risk of leaving it unresolved?

  1. Duplicate protocol identities can corrupt LSDB origin assumptions and prevent predictable route computation or neighbor convergence.
  2. The team can diagnose the wrong flood scope and either miss external reachability or leak a route where it was not intended.
  3. An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
  4. Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

Correct answer: D

Explanation of each choice

A.

The concern could occur elsewhere when A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. For the stated scenario, the immediate risk is: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

B.

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: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

C.

It is a risk in another topology or protocol state: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Here the most direct failure path is: Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable.

D.

Area misassignment can isolate subnets or produce misleading LSDB topology even when Layer 3 interfaces remain reachable. The direct mitigation is: Place the logical interface in the intended OSPF area with correct network type and verify the ABR design and necessary route advertisement.

Question 160

A support escalation at Eastvale MetroNet describes: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. Where should the Junos operator look first for decisive evidence?

  1. Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.
  2. Compare `show ospf neighbor` with both interfaces' configured timers and a Hello packet capture before changing routing import policies.
  3. Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
  4. Capture OSPF protocol packet types and compare neighbor state transitions, focusing on DD sequence and link-state request/update progress.

Correct answer: A

Explanation of each choice

A.

Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference. Area association defines link-state boundaries and is not repaired by an unrelated BGP local-preference change.

B.

That evidence could be normal while the reported defect persists. It is aimed at: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. Instead inspect: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

C.

The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

D.

This check may help with another root cause, for example: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. It does not test the first failed condition; start with: Inspect OSPF area interface membership, neighbor area expectations and area-specific database information before tuning route preference.

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