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 6

Question 50

A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: OSPF broadcast topology reduces unnecessary full adjacency mesh formation.
  2. Protocol behavior: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.
  3. Underlying principle: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane.
  4. Root design issue: NSR and graceful restart on the local restarting device are different approaches and can conflict.

Explanation

Correct Answer

C:

Correct diagnosis: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. The appropriate action is: Differentiate forwarding continuity under GRES from routing-protocol state preservation. The follow-up evidence required is: A switchover test assesses both packet forwarding and routing neighbor continuity.

Incorrect Answers

A:

OSPF broadcast topology reduces unnecessary full adjacency mesh formation describes a neighboring protocol concern. In this case the controlling fact is gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. A correct remediation would differentiate forwarding continuity under GRES from routing-protocol state preservation and demonstrate: A switchover test assesses both packet forwarding and routing neighbor continuity.

B:

The proposed principle concerns another network fault: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Here, gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. The most direct correction is to differentiate forwarding continuity under GRES from routing-protocol state preservation, confirmed by a switchover test assesses both packet forwarding and routing neighbor continuity.

D:

This response would target a different source scenario: A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. It cannot establish the current acceptance requirement, which is: A switchover test assesses both packet forwarding and routing neighbor continuity. The relevant action is: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

Question 51

An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. What operational check demonstrates that the intended outcome occurred?

  1. Closeout evidence: The selected path and its preference match the intended backup policy.
  2. Acceptance check: The test demonstrates loop prevention without advertising false service reachability.
  3. The test confirms that a neighbor route view confirms the approved community-tagged routes are sent.
  4. Expected observation: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Explanation

Correct Answer

B:

Underlying cause: Discard routes may intentionally bound routing loops while dynamic specifics converge. Corrective action: compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Verify the outcome: The test demonstrates loop prevention without advertising false service reachability.

Incorrect Answers

A:

The alternative addresses two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic, not the present root cause. Here the selected correction must reflect discard routes may intentionally bound routing loops while dynamic specifics converge. Test for: The test demonstrates loop prevention without advertising false service reachability.

C:

This option overlooks the decisive condition. Its supporting principle is policy inheritance and term action order affect BGP route advertisement, while this scenario depends on discard routes may intentionally bound routing loops while dynamic specifics converge. Verify the correction with: The test demonstrates loop prevention without advertising false service reachability.

D:

Filter-based routing policy requires explicit match conditions and a safe default behavior 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.

Question 52

Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. What action-and-test pairing directly resolves the case?

  1. Repair: Review route preference before considering equivalent forwarding paths. Check: The selected path and its preference match the intended backup policy.
  2. Change: Compare installed forwarding entries with interface operational status and adjacency resolution. Test: A test packet follows the expected active forwarding next hop and interface.
  3. Implement: Trace the applicable BGP route-selection steps and local policies. Verify: The chosen path matches the configured preference and applicable attributes.
  4. Control: Define the intended route-leaking boundary between the customer's instance and the master routing table. Accepted result: Each customer route is visible only in the tables approved by the design.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Route preference determines the selected route before any multipath decision. Remedy: Review route preference before considering equivalent forwarding paths. Proof: The selected path and its preference match the intended backup policy.

Incorrect Answers

B:

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 selected path and its preference match the intended backup policy. The relevant action is: Review route preference before considering equivalent forwarding paths.

C:

Trace the applicable BGP route-selection steps and local policies is a relevant step for the separate scenario in which a router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count. It does not directly fix this case. Instead review route preference before considering equivalent forwarding paths; verify: The selected path and its preference match the intended backup policy.

D:

The alternative addresses a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table, not the present root cause. Here the selected correction must reflect route preference determines the selected route before any multipath decision. Test for: The selected path and its preference match the intended backup policy.

Question 53

A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. Which corrective action and confirmation pair is most appropriate?

  1. Action: Trace the applicable BGP route-selection steps and local policies. Evidence: The chosen path matches the configured preference and applicable attributes.
  2. Repair: Distinguish signaling reservations from physical link speed and admission control. Check: A controlled setup respects the approved link reservation policy.
  3. Change: Inspect label-switched next-hop resolution separately from generic IP reachability. Test: The labeled service route resolves after the intended LSP is restored.
  4. Implement: Check SR label advertisements, segment configuration and installed MPLS forwarding. Verify: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Explanation

Correct Answer

C:

Underlying cause: A usable IP path need not supply a suitable MPLS LSP or labeled transport path. Corrective action: inspect label-switched next-hop resolution separately from generic IP reachability. Verify the outcome: The labeled service route resolves after the intended LSP is restored.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is bGP selection is policy-driven and is not equivalent to IGP least-hop routing, while this scenario depends on a usable IP path need not supply a suitable MPLS LSP or labeled transport path. Verify the correction with: The labeled service route resolves after the intended LSP is restored.

B:

RSVP resource reservation may affect which additional constrained LSPs can be admitted describes a neighboring protocol concern. In this case the controlling fact is a usable IP path need not supply a suitable MPLS LSP or labeled transport path. A correct remediation would inspect label-switched next-hop resolution separately from generic IP reachability and demonstrate: The labeled service route resolves after the intended LSP is restored.

D:

That result would be useful for a different failure, namely: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. The current case specifically calls for: Inspect label-switched next-hop resolution separately from generic IP reachability. The required observed result is: The labeled service route resolves after the intended LSP is restored.

Question 54

A customer edge loses its OSPF neighbor after an authentication key rollover. Which root-cause explanation and corrective action fit the case?

  1. Root issue: Authentication mismatches can reject otherwise valid OSPF protocol packets. Correction: Coordinate authentication parameters and test the key change under maintenance controls.
  2. Cause: Failover paths are governed by their actual configured metrics. Response: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  3. Diagnosis: Discard routes may intentionally bound routing loops while dynamic specifics converge. Action: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  4. Explanation: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Repair: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

A:

Correct diagnosis: Authentication mismatches can reject otherwise valid OSPF protocol packets. The appropriate action is: Coordinate authentication parameters and test the key change under maintenance controls. The follow-up evidence required is: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Incorrect Answers

B:

The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect authentication mismatches can reject otherwise valid OSPF protocol packets. Test for: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

C:

This answer would be more suitable when an engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop, where the corrective action is to compare withdrawal and blackhole behavior under a lab failure before changing the safety route. The failure here is different: Authentication mismatches can reject otherwise valid OSPF protocol packets. Required validation: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF broadcast topology reduces unnecessary full adjacency mesh formation, while this scenario depends on authentication mismatches can reject otherwise valid OSPF protocol packets. Verify the correction with: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Question 55

A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. Which statement identifies the key design assumption that failed?

  1. The key distinction is: Discard routes may intentionally bound routing loops while dynamic specifics converge.
  2. Protocol behavior: A generated route depends on its contributing-route conditions rather than mere configuration presence.
  3. Underlying principle: Neighbor state must be traced through transport before modifying route policy.
  4. Root design issue: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong.

Explanation

Correct Answer

D:

Underlying cause: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Corrective action: document the discard behavior and determine whether the aggregate should remain advertised. Verify the outcome: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.

Incorrect Answers

A:

The proposed principle concerns another network fault: Discard routes may intentionally bound routing loops while dynamic specifics converge. Here, a discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. The most direct correction is to document the discard behavior and determine whether the aggregate should remain advertised, confirmed by loss-of-specific-route testing produces the approved withdrawal or discard outcome.

B:

That result would be useful for a different failure, namely: A generated route is configured but its expected contributing route is absent from the routing table. The current case specifically calls for: Document the discard behavior and determine whether the aggregate should remain advertised. The required observed result is: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.

C:

This response would target a different source scenario: A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It cannot establish the current acceptance requirement, which is: Loss-of-specific-route testing produces the approved withdrawal or discard outcome. The relevant action is: Document the discard behavior and determine whether the aggregate should remain advertised.

Question 56

A RIB group leak forwards a VPN service toward the wrong next hop after a route update. Which combined repair and acceptance criterion is strongest?

  1. Change: Check import destinations, next-hop resolution and effective routes in every receiving table. Test: The receiving instance shows the correct route and installed next hop after correction.
  2. Implement: Evaluate routing-table relationships and next-hop resolution when using RIB groups. Verify: The imported route resolves and forwarding behavior matches the intended instance.
  3. Control: Coordinate authentication parameters and test the key change under maintenance controls. Accepted result: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.
  4. Action: Separate route-selection and lookup-table changes and test each with candidate configuration. Evidence: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Explanation

Correct Answer

A:

This is the model-intended best choice because imported routes must be validated in the destination lookup context. The targeted correction is to check import destinations, next-hop resolution and effective routes in every receiving table. Validate it by observing that the receiving instance shows the correct route and installed next hop after correction.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is moving route information between tables does not remove the need for a valid forwarding next hop, while this scenario depends on imported routes must be validated in the destination lookup context. Verify the correction with: The receiving instance shows the correct route and installed next hop after correction.

C:

Authentication mismatches can reject otherwise valid OSPF protocol packets describes a neighboring protocol concern. In this case the controlling fact is imported routes must be validated in the destination lookup context. A correct remediation would check import destinations, next-hop resolution and effective routes in every receiving table and demonstrate: The receiving instance shows the correct route and installed next hop after correction.

D:

The proposed principle concerns another network fault: Small reversible route-policy changes simplify troubleshooting and rollback. Here, imported routes must be validated in the destination lookup context. The most direct correction is to check import destinations, next-hop resolution and effective routes in every receiving table, confirmed by the receiving instance shows the correct route and installed next hop after correction.

Question 57

An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Verify compatible area membership or use the designed Level 2 boundary.
  2. Remediation: Distinguish session negotiation from UPDATE message route advertisements.
  3. Recommended change: Compare path metrics and each router's route selection before altering LSP state.
  4. Next step: Inspect link quality, interface settings and DIS state before forcing election behavior.

Explanation

Correct Answer

C:

The critical observation is: Common topology information can still produce direction-dependent shortest paths. Correct it by taking this action: Compare path metrics and each router's route selection before altering LSP state. Confirm the outcome with: Each direction's active route matches the documented costs and design.

Incorrect Answers

A:

This response would target a different source scenario: An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. It cannot establish the current acceptance requirement, which is: Each direction's active route matches the documented costs and design. The relevant action is: Compare path metrics and each router's route selection before altering LSP state.

B:

Distinguish session negotiation from UPDATE message route advertisements is a relevant step for the separate scenario in which a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. It does not directly fix this case. Instead compare path metrics and each router's route selection before altering LSP state; verify: Each direction's active route matches the documented costs and design.

D:

This answer would be more suitable when an IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss, where the corrective action is to inspect link quality, interface settings and DIS state before forcing election behavior. The failure here is different: Common topology information can still produce direction-dependent shortest paths. Required validation: Each direction's active route matches the documented costs and design.

Question 58

An RSVP-signaled LSP enters a failed state after a link bandwidth change. What observable result most directly verifies the intended configuration?

  1. Expected observation: Policy based on the intended community alters admission or preference as designed.
  2. Verification result: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
  3. Closeout evidence: A segment trace follows the desired prefix or explicit adjacency.
  4. Acceptance check: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Remedy: Review reservation constraints and available resources rather than resetting all label sessions. Proof: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Incorrect Answers

A:

Communities are policy signaling metadata and not the packet-forwarding next hop themselves describes a neighboring protocol concern. In this case the controlling fact is rSVP LSP setup can fail resource or path constraints even with valid IP reachability. A correct remediation would review reservation constraints and available resources rather than resetting all label sessions and demonstrate: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

B:

The proposed principle concerns another network fault: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Here, rSVP LSP setup can fail resource or path constraints even with valid IP reachability. The most direct correction is to review reservation constraints and available resources rather than resetting all label sessions, confirmed by a compatible bandwidth or path choice allows the target RSVP LSP to establish.

C:

That result would be useful for a different failure, namely: A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. The current case specifically calls for: Review reservation constraints and available resources rather than resetting all label sessions. The required observed result is: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Question 59

A GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Control: Enable and verify the intended IPv6 address-family reachability advertisements. Accepted result: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.
  2. Action: Verify reachability between tunnel source and destination addresses. Evidence: The remote tunnel endpoint is reachable through the intended underlay.
  3. Repair: Verify instance ownership and route policy at both tunnel endpoints. Check: Traffic uses the tunnel in the intended customer routing instance only.
  4. Change: Test effective MTU and path MTU discovery across the encapsulated route. Test: A controlled large-payload test succeeds after MTU or MSS adjustment.

Explanation

Correct Answer

C:

The selected response implements the principle that tunneling transport and customer route isolation are separate configurations. The engineer should verify instance ownership and route policy at both tunnel endpoints. Successful confirmation means: Traffic uses the tunnel in the intended customer routing instance only.

Incorrect Answers

A:

The alternative addresses an IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled, not the present root cause. Here the selected correction must reflect tunneling transport and customer route isolation are separate configurations. Test for: Traffic uses the tunnel in the intended customer routing instance only.

B:

This answer would be more suitable when a GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint, where the corrective action is to verify reachability between tunnel source and destination addresses. The failure here is different: Tunneling transport and customer route isolation are separate configurations. Required validation: Traffic uses the tunnel in the intended customer routing instance only.

D:

GRE encapsulation overhead can expose MTU blackholes for larger payloads describes a neighboring protocol concern. In this case the controlling fact is tunneling transport and customer route isolation are separate configurations. A correct remediation would verify instance ownership and route policy at both tunnel endpoints and demonstrate: Traffic uses the tunnel in the intended customer routing instance only.

Question 60

IPv4 IS-IS routing works but IPv6 routes do not appear on a dual-stack backbone. Which post-change observation most strongly confirms the correction?

  1. Acceptance check: The route policy and active table agree with the approved advertised prefixes.
  2. The test confirms that the neighbor table shows the intended level and stable adjacency.
  3. Expected observation: Both address families display their expected prefixes through the same stable topology.
  4. Verification result: The chosen path matches the configured preference and applicable attributes.

Explanation

Correct Answer

C:

This is the model-intended best choice because iS-IS can convey multiple address families with appropriate support. The targeted correction is to check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency. Validate it by observing that both address families display their expected prefixes through the same stable topology.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An IS-IS route disappears after a policy update while the LSP database still contains the topology. The current case specifically calls for: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency. The required observed result is: Both address families display their expected prefixes through the same stable topology.

B:

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: Both address families display their expected prefixes through the same stable topology. The relevant action is: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency.

D:

The alternative addresses a router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count, not the present root cause. Here the selected correction must reflect iS-IS can convey multiple address families with appropriate support. Test for: Both address families display their expected prefixes through the same stable topology.

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