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 52

Question 510

A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. What is the most defensible network engineering correction?

  1. Recommended change: Review EBGP multihop transport reachability and session parameters.
  2. Next step: Confirm the configured local and peer AS values with the authoritative design.
  3. Corrective action: Verify IP reachability, routing instance context, TCP transport and session authentication.
  4. Apply this control: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: BGP OPEN negotiation includes AS identity that must match peering intent. Remedy: Confirm the configured local and peer AS values with the authoritative design. Proof: The session reaches Established only with the documented correct peer AS.

Incorrect Answers

A:

Review EBGP multihop transport reachability and session parameters is a relevant step for the separate scenario in which a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. It does not directly fix this case. Instead confirm the configured local and peer AS values with the authoritative design; verify: The session reaches Established only with the documented correct peer AS.

C:

This answer would be more suitable when a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, where the corrective action is to verify IP reachability, routing instance context, TCP transport and session authentication. The failure here is different: BGP OPEN negotiation includes AS identity that must match peering intent. Required validation: The session reaches Established only with the documented correct peer AS.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF neighbor-state interpretation depends on multiaccess election roles, while this scenario depends on bGP OPEN negotiation includes AS identity that must match peering intent. Verify the correction with: The session reaches Established only with the documented correct peer AS.

Question 511

A carrier attachment must not allow a customer switch to become the provider's root bridge. Which statement identifies the key design assumption that failed?

  1. The governing rule is: MSTP region agreement affects how instances interoperate across links.
  2. The key distinction is: Bridges learn source MAC locations and flood unknown destinations within a permitted domain.
  3. Protocol behavior: A redundant alternate path can remain nonforwarding until a failure changes roles.
  4. Underlying principle: Root protection can prevent undesired superior-root claims from changing root placement.

Explanation

Correct Answer

D:

Underlying cause: Root protection can prevent undesired superior-root claims from changing root placement. Corrective action: review root protection at the provider-facing boundary. Verify the outcome: A superior BPDU test does not move the approved provider root.

Incorrect Answers

A:

The proposed principle concerns another network fault: MSTP region agreement affects how instances interoperate across links. Here, root protection can prevent undesired superior-root claims from changing root placement. The most direct correction is to review root protection at the provider-facing boundary, confirmed by a superior BPDU test does not move the approved provider root.

B:

That result would be useful for a different failure, namely: A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. The current case specifically calls for: Review root protection at the provider-facing boundary. The required observed result is: A superior BPDU test does not move the approved provider root.

C:

This response would target a different source scenario: A switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth. It cannot establish the current acceptance requirement, which is: A superior BPDU test does not move the approved provider root. The relevant action is: Review root protection at the provider-facing boundary.

Question 512

A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Restore explicit policy matching and confirm external route advertisements. Check: An LSA and route inspection finds only the authorized external prefix set.
  2. Change: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. Test: The segment passes route and database tests with the expected neighbor states.
  3. Implement: Verify compatible network and Hello parameters including mask where applicable. Verify: A controlled neighbor check reaches Full after configuration correction.
  4. Control: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Accepted result: The test demonstrates loop prevention without advertising false service reachability.

Explanation

Correct Answer

B:

Correct diagnosis: OSPF neighbor-state interpretation depends on multiaccess election roles. The appropriate action is: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. The follow-up evidence required is: The segment passes route and database tests with the expected neighbor states.

Incorrect Answers

A:

This answer would be more suitable when a BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design, where the corrective action is to restore explicit policy matching and confirm external route advertisements. The failure here is different: OSPF neighbor-state interpretation depends on multiaccess election roles. Required validation: The segment passes route and database tests with the expected neighbor states.

C:

OSPF network-type and Hello compatibility can prevent adjacency formation describes a neighboring protocol concern. In this case the controlling fact is oSPF neighbor-state interpretation depends on multiaccess election roles. A correct remediation would check DR and BDR roles and expected 2-Way peers before changing a healthy segment and demonstrate: The segment passes route and database tests with the expected neighbor states.

D:

The proposed principle concerns another network fault: Discard routes may intentionally bound routing loops while dynamic specifics converge. Here, oSPF neighbor-state interpretation depends on multiaccess election roles. The most direct correction is to check DR and BDR roles and expected 2-Way peers before changing a healthy segment, confirmed by the segment passes route and database tests with the expected neighbor states.

Question 513

An input firewall filter diverts all transit traffic to a management routing instance by mistake. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes.
  2. Apply this control: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  3. Remediation: Evaluate routing-table relationships and next-hop resolution when using RIB groups.
  4. Recommended change: Inspect the configuration, active route state and next-hop reachability before changing preference.

Explanation

Correct Answer

A:

Underlying cause: Filter-based routing policy requires explicit match conditions and a safe default behavior. Corrective action: narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes. Verify the outcome: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Incorrect Answers

B:

Restore appropriate IGP next-hop reachability or approved next-hop-self behavior is a relevant step for the separate scenario in which an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. It does not directly fix this case. Instead narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes; verify: Only approved traffic uses the alternate table while ordinary transit remains on its path.

C:

The alternative addresses a route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there, not the present root cause. Here the selected correction must reflect filter-based routing policy requires explicit match conditions and a safe default behavior. Test for: Only approved traffic uses the alternate table while ordinary transit remains on its path.

D:

This answer would be more suitable when after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, where the corrective action is to inspect the configuration, active route state and next-hop reachability before changing preference. The failure here is different: Filter-based routing policy requires explicit match conditions and a safe default behavior. Required validation: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Question 514

An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. Which next action best resolves this observed routing or switching failure?

  1. Next step: Compare RIB selection with forwarding-table installation and next-hop resolution.
  2. Corrective action: Review route-reflector client and cluster design, including loop-prevention attributes.
  3. Apply this control: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  4. Remediation: Compare installed forwarding entries with interface operational status and adjacency resolution.

Explanation

Correct Answer

C:

Correct diagnosis: Discard routes may intentionally bound routing loops while dynamic specifics converge. The appropriate action is: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. The follow-up evidence required is: The test demonstrates loop prevention without advertising false service reachability.

Incorrect Answers

A:

Control-plane route visibility and installed forwarding state are distinct evidence describes a neighboring protocol concern. In this case the controlling fact is discard routes may intentionally bound routing loops while dynamic specifics converge. A correct remediation would compare withdrawal and blackhole behavior under a lab failure before changing the safety route and demonstrate: The test demonstrates loop prevention without advertising false service reachability.

B:

The proposed principle concerns another network fault: Route reflection relies on correct client boundaries and originator or cluster tracking. Here, discard routes may intentionally bound routing loops while dynamic specifics converge. The most direct correction is to compare withdrawal and blackhole behavior under a lab failure before changing the safety route, confirmed by the test demonstrates loop prevention without advertising false service reachability.

D:

This response would target a different source scenario: A route shows as active but the interface destination still drops traffic after an interface move. It cannot establish the current acceptance requirement, which is: The test demonstrates loop prevention without advertising false service reachability. The relevant action is: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.

Question 515

An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. What remediation is most directly applicable?

  1. Recommended change: Inspect local preference, export/import inheritance and selected BGP path attributes.
  2. Next step: Identify TLVs as structured information within IS-IS protocol data units.
  3. Corrective action: Verify compatible area membership or use the designed Level 2 boundary.
  4. Apply this control: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

Explanation

Correct Answer

C:

The selected response implements the principle that iS-IS Level 1 adjacency formation depends on common area context. The engineer should verify compatible area membership or use the designed Level 2 boundary. Successful confirmation means: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Incorrect Answers

A:

The alternative addresses a policy change unexpectedly makes a backup transit provider carry most outbound traffic, not the present root cause. Here the selected correction must reflect iS-IS Level 1 adjacency formation depends on common area context. Test for: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

B:

This answer would be more suitable when an operator calls an IS-IS TLV a transport packet and ignores its role in link-state information, where the corrective action is to identify TLVs as structured information within IS-IS protocol data units. The failure here is different: IS-IS Level 1 adjacency formation depends on common area context. Required validation: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

D:

Structured protocol-layer evidence separates link health from routing convergence issues describes a neighboring protocol concern. In this case the controlling fact is iS-IS Level 1 adjacency formation depends on common area context. A correct remediation would verify compatible area membership or use the designed Level 2 boundary and demonstrate: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Question 516

A technician edits a router ID but tests immediately without accounting for established OSPF process state. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: Changing router identity may require controlled protocol restart or adjacency reestablishment. Repair: Apply a safe approved OSPF process refresh and verify advertised router identity.
  2. Fault mechanism: OSPF neighbor-state interpretation depends on multiaccess election roles. Remediation: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.
  3. Root issue: An operational interface is not evidence of matching IS-IS protocol configuration. Correction: Inspect IS-IS interface enablement, levels, area identifiers and link type.
  4. Cause: OSPF route selection follows each router's synchronized topology view. Response: Inspect link-state databases and SPF output on affected routers.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Changing router identity may require controlled protocol restart or adjacency reestablishment. Remedy: Apply a safe approved OSPF process refresh and verify advertised router identity. Proof: All neighbors record the new unique ID and routing stability is restored.

Incorrect Answers

B:

This response would target a different source scenario: A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. It cannot establish the current acceptance requirement, which is: All neighbors record the new unique ID and routing stability is restored. The relevant action is: Apply a safe approved OSPF process refresh and verify advertised router identity.

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 apply a safe approved OSPF process refresh and verify advertised router identity; verify: All neighbors record the new unique ID and routing stability is restored.

D:

The alternative addresses a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, not the present root cause. Here the selected correction must reflect changing router identity may require controlled protocol restart or adjacency reestablishment. Test for: All neighbors record the new unique ID and routing stability is restored.

Question 517

A provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor. What implementation step and validation result should be selected?

  1. Repair: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. Check: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  2. Change: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. Test: The remote PE learns and uses the intended IPv6 prefix.
  3. Implement: Distinguish IPv6 Neighbor Discovery from IPv4 ARP. Verify: The neighbor cache resolves the IPv6 next hop and traffic passes.
  4. Control: Inspect link quality, interface settings and DIS state before forcing election behavior. Accepted result: A stable neighbor and LAN LSP remain after link faults are corrected.

Explanation

Correct Answer

C:

Underlying cause: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Corrective action: distinguish IPv6 Neighbor Discovery from IPv4 ARP. Verify the outcome: The neighbor cache resolves the IPv6 next hop and traffic passes.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is tunneling carries one protocol over an underlay that may not route that payload natively, while this scenario depends on iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Verify the correction with: The neighbor cache resolves the IPv6 next hop and traffic passes.

B:

Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence describes a neighboring protocol concern. In this case the controlling fact is iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. A correct remediation would distinguish IPv6 Neighbor Discovery from IPv4 ARP and demonstrate: The neighbor cache resolves the IPv6 next hop and traffic passes.

D:

That result would be useful for a different failure, namely: An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. The current case specifically calls for: Distinguish IPv6 Neighbor Discovery from IPv4 ARP. The required observed result is: The neighbor cache resolves the IPv6 next hop and traffic passes.

Question 518

A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: The expected redistributed prefix appears with the right OSPF route type.
  2. Verification result: A switchover test assesses both packet forwarding and routing neighbor continuity.
  3. Closeout evidence: The fault is visible and surviving members carry traffic within the approved limits.
  4. Acceptance check: An authorized switchover maintains bridge control state and service reachability.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Remedy: Differentiate forwarding continuity under GRES from routing-protocol state preservation. Proof: A switchover test assesses both packet forwarding and routing neighbor continuity.

Incorrect Answers

A:

Distinguish internal LSAs from externally originated route information is a relevant step for the separate scenario in which a link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. It does not directly fix this case. Instead differentiate forwarding continuity under GRES from routing-protocol state preservation; verify: A switchover test assesses both packet forwarding and routing neighbor continuity.

C:

This answer would be more suitable when one LAG member fails silently and the service loses capacity even though the logical interface remains active, where the corrective action is to inspect member states, traffic distribution and configured minimum link expectations. The failure here is different: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Required validation: A switchover test assesses both packet forwarding and routing neighbor continuity.

D:

This option overlooks the decisive condition. Its supporting principle is nonstop bridging protects relevant Layer 2 control-protocol state during switchover, while this scenario depends on gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Verify the correction with: A switchover test assesses both packet forwarding and routing neighbor continuity.

Question 519

An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. What assessment accurately links the fault to its correction?

  1. Root issue: RSTP can converge faster using explicit roles and handshakes where conditions allow. Correction: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  2. Cause: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Response: Differentiate forwarding continuity under GRES from routing-protocol state preservation.
  3. Diagnosis: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Action: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.
  4. Explanation: Aggregated links need operational member health monitoring and suitable capacity planning. Repair: Inspect member states, traffic distribution and configured minimum link expectations.

Explanation

Correct Answer

C:

The case turns on the distinction that nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Apply this concrete engineering step: Evaluate nonstop bridging together with the supported Routing Engine redundancy design. An acceptable verification outcome is: An authorized switchover maintains bridge control state and service reachability.

Incorrect Answers

A:

The proposed principle concerns another network fault: RSTP can converge faster using explicit roles and handshakes where conditions allow. Here, nonstop bridging protects relevant Layer 2 control-protocol state during switchover. The most direct correction is to evaluate nonstop bridging together with the supported Routing Engine redundancy design, confirmed by an authorized switchover maintains bridge control state and service reachability.

B:

That result would be useful for a different failure, namely: A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. The current case specifically calls for: Evaluate nonstop bridging together with the supported Routing Engine redundancy design. The required observed result is: An authorized switchover maintains bridge control state and service reachability.

D:

Inspect member states, traffic distribution and configured minimum link expectations is a relevant step for the separate scenario in which one LAG member fails silently and the service loses capacity even though the logical interface remains active. It does not directly fix this case. Instead evaluate nonstop bridging together with the supported Routing Engine redundancy design; verify: An authorized switchover maintains bridge control state and service reachability.

Question 520

A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: A capture identifies the label used at each transit stage.
  2. The test confirms that the chosen protocol establishes the intended type of LSP.
  3. Expected observation: The backup LSP establishes on a permitted alternate path.
  4. Verification result: A test packet follows the expected active forwarding next hop and interface.

Explanation

Correct Answer

B:

Correct diagnosis: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. The appropriate action is: Separate RSVP-signaled LSP functions from LDP label distribution. The follow-up evidence required is: The chosen protocol establishes the intended type of LSP.

Incorrect Answers

A:

This answer would be more suitable when a router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport, where the corrective action is to inspect the full MPLS label stack and outgoing label operation. The failure here is different: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Required validation: The chosen protocol establishes the intended type of LSP.

C:

An LSP cannot follow an unavailable required hop describes a neighboring protocol concern. In this case the controlling fact is rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. A correct remediation would separate RSVP-signaled LSP functions from LDP label distribution and demonstrate: The chosen protocol establishes the intended type of LSP.

D:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. Here, rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. The most direct correction is to separate RSVP-signaled LSP functions from LDP label distribution, confirmed by the chosen protocol establishes the intended type of LSP.

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