mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

Juniper JN0-364 Questions & Answers

Reliable & Actual Study Materials for JN0-364 Exam Success

69 Questions & Answers with Testing Engine

"JN0-364: Service Provider Routing and Switching, Specialist (JNCIS-SP)" Testing Engine covers all the knowledge points of the real Juniper JN0-364 exam.

The latest actual JN0-364 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-364 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 27

Question 260

An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. Which test result would best confirm a successful fix?

  1. The test confirms that the peers progress to the expected adjacency state and exchange LSAs.
  2. Expected observation: The routing table exposes the selection reason and the intended route is installed.
  3. Verification result: The corrected circuit shows the expected neighbor and link-state entries.
  4. Closeout evidence: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Explanation

Correct Answer

D:

Correct diagnosis: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. The appropriate action is: Review the passive-interface configuration and required active neighbor links. The follow-up evidence required is: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. The current case specifically calls for: Review the passive-interface configuration and required active neighbor links. The required observed result is: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

B:

This response would target a different source scenario: An OSPF packet capture shows Link State Updates but the route remains hidden from the active table. It cannot establish the current acceptance requirement, which is: The intended backbone neighbor forms and customer-only passive interfaces remain passive. The relevant action is: Review the passive-interface configuration and required active neighbor links.

C:

Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead review the passive-interface configuration and required active neighbor links; verify: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Question 261

A technician edits a router ID but tests immediately without accounting for established OSPF process state. What should the operations engineer do first to address the stated fault?

  1. Recommended change: Assign distinct stable router IDs and clear stale protocol state using an approved procedure.
  2. Next step: Apply a safe approved OSPF process refresh and verify advertised router identity.
  3. Corrective action: Compare received LSAs with route selection, area eligibility and next-hop resolution.
  4. Apply this control: Separate route-selection and lookup-table changes and test each with candidate configuration.

Explanation

Correct Answer

B:

The case turns on the distinction that changing router identity may require controlled protocol restart or adjacency reestablishment. Apply this concrete engineering step: Apply a safe approved OSPF process refresh and verify advertised router identity. An acceptable verification outcome is: All neighbors record the new unique ID and routing stability is restored.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is oSPF identifies speakers by router ID, which must be unique inside a routing domain, while this scenario depends on changing router identity may require controlled protocol restart or adjacency reestablishment. Verify the correction with: All neighbors record the new unique ID and routing stability is restored.

C:

The proposed principle concerns another network fault: Receiving topology data does not guarantee a route becomes active and installed. Here, changing router identity may require controlled protocol restart or adjacency reestablishment. The most direct correction is to apply a safe approved OSPF process refresh and verify advertised router identity, confirmed by all neighbors record the new unique ID and routing stability is restored.

D:

That result would be useful for a different failure, namely: A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. The current case specifically calls for: Apply a safe approved OSPF process refresh and verify advertised router identity. The required observed result is: All neighbors record the new unique ID and routing stability is restored.

Question 262

An IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment. What is the most defensible network engineering correction?

  1. Remediation: Compare path metrics and each router's route selection before altering LSP state.
  2. Recommended change: Compare interface level settings and area configuration.
  3. Next step: Distinguish IS-IS adjacency from address-family reachability advertisements.
  4. Corrective action: Compare area, interface mode, timers, authentication and physical status on both endpoints.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Compatible IS-IS levels and area information determine available adjacency types. Remedy: Compare interface level settings and area configuration. Proof: The neighbor table shows the intended level and stable adjacency.

Incorrect Answers

A:

Compare path metrics and each router's route selection before altering LSP state is a relevant step for the separate scenario in which an IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. It does not directly fix this case. Instead compare interface level settings and area configuration; verify: The neighbor table shows the intended level and stable adjacency.

C:

This answer would be more suitable when a core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken, where the corrective action is to distinguish IS-IS adjacency from address-family reachability advertisements. The failure here is different: Compatible IS-IS levels and area information determine available adjacency types. Required validation: The neighbor table shows the intended level and stable adjacency.

D:

This option overlooks the decisive condition. Its supporting principle is layered neighbor troubleshooting should separate transport from OSPF parameter mismatches, while this scenario depends on compatible IS-IS levels and area information determine available adjacency types. Verify the correction with: The neighbor table shows the intended level and stable adjacency.

Question 263

A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. Which evidence would justify closing this troubleshooting case?

  1. Verification result: An unwanted looped route is rejected in a lab before production change.
  2. Closeout evidence: A controlled route lookup confirms the neighbor's actual selected entry path.
  3. Acceptance check: The label table and LSP state match the intended forwarding path.
  4. The test confirms that a packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Explanation

Correct Answer

D:

Underlying cause: BGP message types have separate roles in session formation and reachability exchange. Corrective action: distinguish session negotiation from UPDATE message route advertisements. Verify the outcome: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Incorrect Answers

A:

The proposed principle concerns another network fault: Disabling loop prevention can introduce persistent interdomain routing loops. Here, bGP message types have separate roles in session formation and reachability exchange. The most direct correction is to distinguish session negotiation from UPDATE message route advertisements, confirmed by a packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

B:

That result would be useful for a different failure, namely: An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. The current case specifically calls for: Distinguish session negotiation from UPDATE message route advertisements. The required observed result is: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

C:

This response would target a different source scenario: A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. It cannot establish the current acceptance requirement, which is: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information. The relevant action is: Distinguish session negotiation from UPDATE message route advertisements.

Question 264

A dual-stack peer is Established but the IPv6 customer route is absent. What implementation step and validation result should be selected?

  1. Action: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Evidence: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.
  2. Repair: Revisit additive path cost and verify SPF outcomes across alternative links. Check: The intended lower-total-cost path wins under steady-state conditions.
  3. Change: Inspect local preference, export/import inheritance and selected BGP path attributes. Test: Traffic uses the primary provider until the documented failover condition occurs.
  4. Implement: Review route-reflector client and cluster design, including loop-prevention attributes. Verify: A test prefix reaches permitted clients without cycling through reflector clusters.

Explanation

Correct Answer

A:

This is the model-intended best choice because iPv4 BGP session liveness does not prove IPv6 family route exchange. The targeted correction is to inspect inet6 family negotiation, filters and IPv6 next-hop validity. Validate it by observing that the expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is oSPF normally prefers the least accumulated metric to a destination, while this scenario depends on iPv4 BGP session liveness does not prove IPv6 family route exchange. Verify the correction with: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

C:

Routing policy changes can override expected primary and backup peering intent describes a neighboring protocol concern. In this case the controlling fact is iPv4 BGP session liveness does not prove IPv6 family route exchange. A correct remediation would inspect inet6 family negotiation, filters and IPv6 next-hop validity and demonstrate: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

D:

The proposed principle concerns another network fault: Route reflection relies on correct client boundaries and originator or cluster tracking. Here, iPv4 BGP session liveness does not prove IPv6 family route exchange. The most direct correction is to inspect inet6 family negotiation, filters and IPv6 next-hop validity, confirmed by the expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Question 265

IPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. Which evidence would justify closing this troubleshooting case?

  1. The test confirms that the neighbor table shows the intended level and stable adjacency.
  2. Expected observation: A destination lookup chooses the intended most specific valid route.
  3. Verification result: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.
  4. Closeout evidence: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Explanation

Correct Answer

C:

The critical observation is: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Correct it by taking this action: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU. Confirm the outcome with: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Incorrect Answers

A:

This response would target a different source scenario: An IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment. It cannot establish the current acceptance requirement, which is: IPv6 test packets traverse the restored tunnel with appropriate MTU handling. The relevant action is: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU.

B:

Apply longest-prefix-match route lookup to the IPv6 destination is a relevant step for the separate scenario in which an engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. It does not directly fix this case. Instead verify tunnel protocol allowance, endpoint encapsulation and effective MTU; verify: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

D:

This answer would be more suitable when an IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution, where the corrective action is to verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. The failure here is different: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Required validation: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Question 266

A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: BGP message types have separate roles in session formation and reachability exchange. Remediation: Distinguish session negotiation from UPDATE message route advertisements.
  2. Root issue: iBGP scaling mechanisms reduce the full-mesh session requirement. Correction: Evaluate route reflection with defined cluster and client boundaries.
  3. Cause: BGP sessions require sustained TCP connectivity independent of physical interface health. Response: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  4. Diagnosis: Incorrect label removal can expose payload handling that the egress does not expect. Action: Verify the label action and egress handling for the intended service stack.

Explanation

Correct Answer

B:

This is the model-intended best choice because iBGP scaling mechanisms reduce the full-mesh session requirement. The targeted correction is to evaluate route reflection with defined cluster and client boundaries. Validate it by observing that the route-reflector design distributes approved prefixes without unintended loops.

Incorrect Answers

A:

BGP message types have separate roles in session formation and reachability exchange describes a neighboring protocol concern. In this case the controlling fact is iBGP scaling mechanisms reduce the full-mesh session requirement. A correct remediation would evaluate route reflection with defined cluster and client boundaries and demonstrate: The route-reflector design distributes approved prefixes without unintended loops.

C:

That result would be useful for a different failure, namely: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. The current case specifically calls for: Evaluate route reflection with defined cluster and client boundaries. The required observed result is: The route-reflector design distributes approved prefixes without unintended loops.

D:

This response would target a different source scenario: An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. It cannot establish the current acceptance requirement, which is: The route-reflector design distributes approved prefixes without unintended loops. The relevant action is: Evaluate route reflection with defined cluster and client boundaries.

Question 267

An IS-IS route disappears after a policy update while the LSP database still contains the topology. What assessment accurately links the fault to its correction?

  1. Explanation: Authentication mismatches can reject otherwise valid OSPF protocol packets. Repair: Coordinate authentication parameters and test the key change under maintenance controls.
  2. Fault mechanism: IS-IS routing levels determine topology knowledge and area reachability. Remediation: Review Level 1 and Level 2 routing roles and their intended boundaries.
  3. Root issue: A learned LSP does not ensure a destination is selected into the active routing table. Correction: Inspect route import policy and forwarding selection separately from LSP presence.
  4. Cause: Common topology information can still produce direction-dependent shortest paths. Response: Compare path metrics and each router's route selection before altering LSP state.

Explanation

Correct Answer

C:

The selected response implements the principle that a learned LSP does not ensure a destination is selected into the active routing table. The engineer should inspect route import policy and forwarding selection separately from LSP presence. Successful confirmation means: The route policy and active table agree with the approved advertised prefixes.

Incorrect Answers

A:

The alternative addresses a customer edge loses its OSPF neighbor after an authentication key rollover, not the present root cause. Here the selected correction must reflect a learned LSP does not ensure a destination is selected into the active routing table. Test for: The route policy and active table agree with the approved advertised prefixes.

B:

This answer would be more suitable when a router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view, where the corrective action is to review Level 1 and Level 2 routing roles and their intended boundaries. The failure here is different: A learned LSP does not ensure a destination is selected into the active routing table. Required validation: The route policy and active table agree with the approved advertised prefixes.

D:

Common topology information can still produce direction-dependent shortest paths describes a neighboring protocol concern. In this case the controlling fact is a learned LSP does not ensure a destination is selected into the active routing table. A correct remediation would inspect route import policy and forwarding selection separately from LSP presence and demonstrate: The route policy and active table agree with the approved advertised prefixes.

Question 268

A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. What is the most defensible network engineering correction?

  1. Apply this control: Distinguish session negotiation from UPDATE message route advertisements.
  2. Remediation: Separate RSVP-signaled LSP functions from LDP label distribution.
  3. Recommended change: Compare label bindings with the active IGP next hop and installed forwarding entries.
  4. Next step: Review LDP dependence on reachability and routing of the transport endpoints.

Explanation

Correct Answer

B:

Because rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability, the best response is to separate RSVP-signaled LSP functions from LDP label distribution. A reviewer can close the technical case only after confirming that the chosen protocol establishes the intended type of LSP.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. The current case specifically calls for: Separate RSVP-signaled LSP functions from LDP label distribution. The required observed result is: The chosen protocol establishes the intended type of LSP.

C:

Compare label bindings with the active IGP next hop and installed forwarding entries is a relevant step for the separate scenario in which an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. It does not directly fix this case. Instead separate RSVP-signaled LSP functions from LDP label distribution; verify: The chosen protocol establishes the intended type of LSP.

D:

The alternative addresses an LDP-signaled LSP fails when the IGP route to the remote loopback disappears, not the present root cause. Here the selected correction must reflect rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Test for: The chosen protocol establishes the intended type of LSP.

Question 269

A router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: The label table and LSP state match the intended forwarding path.
  2. Verification result: The imported route resolves and forwarding behavior matches the intended instance.
  3. Closeout evidence: The intended SR transport path forwards without unintended dependence on the retired LDP path.
  4. Acceptance check: A capture identifies the label used at each transit stage.

Explanation

Correct Answer

D:

The selected response implements the principle that outer and inner labels can have distinct transport and service roles. The engineer should inspect the full MPLS label stack and outgoing label operation. Successful confirmation means: A capture identifies the label used at each transit stage.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is mPLS forwarding requires coordinated label signaling and forwarding entries, while this scenario depends on outer and inner labels can have distinct transport and service roles. Verify the correction with: A capture identifies the label used at each transit stage.

B:

Moving route information between tables does not remove the need for a valid forwarding next hop describes a neighboring protocol concern. In this case the controlling fact is outer and inner labels can have distinct transport and service roles. A correct remediation would inspect the full MPLS label stack and outgoing label operation and demonstrate: A capture identifies the label used at each transit stage.

C:

The proposed principle concerns another network fault: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Here, outer and inner labels can have distinct transport and service roles. The most direct correction is to inspect the full MPLS label stack and outgoing label operation, confirmed by a capture identifies the label used at each transit stage.

Question 270

A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that the tenant-specific lookup resolves and the same source-based test reaches its destination.
  2. Expected observation: All neighbors record the new unique ID and routing stability is restored.
  3. Verification result: The segment passes route and database tests with the expected neighbor states.
  4. Closeout evidence: Each router is uniquely identified and the link-state database converges.

Explanation

Correct Answer

C:

Because oSPF neighbor-state interpretation depends on multiaccess election roles, the best response is to check DR and BDR roles and expected 2-Way peers before changing a healthy segment. A reviewer can close the technical case only after confirming that the segment passes route and database tests with the expected neighbor states.

Incorrect Answers

A:

Run route and connectivity checks in the explicitly intended routing instance is a relevant step for the separate scenario in which a provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It does not directly fix this case. Instead check DR and BDR roles and expected 2-Way peers before changing a healthy segment; verify: The segment passes route and database tests with the expected neighbor states.

B:

The alternative addresses a technician edits a router ID but tests immediately without accounting for established OSPF process state, not the present root cause. Here the selected correction must reflect oSPF neighbor-state interpretation depends on multiaccess election roles. Test for: The segment passes route and database tests with the expected neighbor states.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF identifies speakers by router ID, which must be unique inside a routing domain, while this scenario depends on oSPF neighbor-state interpretation depends on multiaccess election roles. Verify the correction with: The segment passes route and database tests with the expected neighbor states.

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