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 40

Question 390

A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. What is the primary routing or switching concept illustrated?

  1. The governing rule is: Protocol timers need reliable packet delivery and should not mask an unstable link.
  2. The key distinction is: Multi-area OSPF design requires attention to backbone connectivity.
  3. Protocol behavior: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions.
  4. Underlying principle: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Multi-area OSPF design requires attention to backbone connectivity. Remedy: Review hierarchical OSPF backbone attachment and area border placement. Proof: The planned ABR topology provides verified interarea reachability.

Incorrect Answers

A:

Compare Hello/Dead event logs with loss and interface errors before tuning timers is a relevant step for the separate scenario in which several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It does not directly fix this case. Instead review hierarchical OSPF backbone attachment and area border placement; verify: The planned ABR topology provides verified interarea reachability.

C:

This answer would be more suitable when a technician treats an OSPF Link State Request as the same message as a Hello packet, where the corrective action is to differentiate neighbor discovery from database synchronization message types. The failure here is different: Multi-area OSPF design requires attention to backbone connectivity. Required validation: The planned ABR topology provides verified interarea reachability.

D:

This option overlooks the decisive condition. Its supporting principle is policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table, while this scenario depends on multi-area OSPF design requires attention to backbone connectivity. Verify the correction with: The planned ABR topology provides verified interarea reachability.

Question 391

IPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. What assessment accurately links the fault to its correction?

  1. Diagnosis: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Action: Review IPv6 path MTU discovery and endpoint fragmentation requirements.
  2. Explanation: Policy placement determines which prefixes influence a routing table or advertisement. Repair: Apply and verify supported route policy at the intended routing import or export boundary.
  3. Fault mechanism: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Remediation: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state.
  4. Root issue: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Correction: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU.

Explanation

Correct Answer

D:

Underlying cause: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Corrective action: verify tunnel protocol allowance, endpoint encapsulation and effective MTU. Verify the outcome: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Incorrect Answers

A:

The proposed principle concerns another network fault: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Here, underlying endpoint reachability does not guarantee permitted encapsulated payloads. The most direct correction is to verify tunnel protocol allowance, endpoint encapsulation and effective MTU, confirmed by iPv6 test packets traverse the restored tunnel with appropriate MTU handling.

B:

That result would be useful for a different failure, namely: An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. The current case specifically calls for: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU. The required observed result is: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

C:

This response would target a different source scenario: An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. 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.

Question 392

One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: Aggregation can hide individual component failures if advertisement policy is not controlled.
  2. Root design issue: Labels have locally significant forwarding meaning on each LSP segment.
  3. The governing rule is: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults.
  4. The key distinction is: MPLS relies on selected underlay transport reachability and policy eligibility.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Remedy: Compare ingress label imposition with transit LFIB and egress disposition. Proof: A hop-by-hop labeled test locates and corrects the failing label action.

Incorrect Answers

A:

This answer would be more suitable when a summary route is advertised even though the operator expects every more-specific customer route to remain reachable, where the corrective action is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The failure here is different: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Required validation: A hop-by-hop labeled test locates and corrects the failing label action.

B:

This option overlooks the decisive condition. Its supporting principle is labels have locally significant forwarding meaning on each LSP segment, while this scenario depends on successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Verify the correction with: A hop-by-hop labeled test locates and corrects the failing label action.

D:

The proposed principle concerns another network fault: MPLS relies on selected underlay transport reachability and policy eligibility. Here, successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. The most direct correction is to compare ingress label imposition with transit LFIB and egress disposition, confirmed by a hop-by-hop labeled test locates and corrects the failing label action.

Question 393

An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. What action-and-test pairing directly resolves the case?

  1. Control: Compare ingress label imposition with transit LFIB and egress disposition. Accepted result: A hop-by-hop labeled test locates and corrects the failing label action.
  2. Action: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Evidence: A segment trace follows the desired prefix or explicit adjacency.
  3. Repair: Inspect the incoming label, outgoing label and interface on each affected LSR. Check: The repaired hop has the expected swap operation and carries a test packet.
  4. Change: Restrict routing-policy matches and validate the import and export boundary. Test: A negative test proves the unrelated customer prefix is absent from the target table.

Explanation

Correct Answer

C:

The critical observation is: Label-switching errors can occur even when control-plane endpoint reachability is good. Correct it by taking this action: Inspect the incoming label, outgoing label and interface on each affected LSR. Confirm the outcome with: The repaired hop has the expected swap operation and carries a test packet.

Incorrect Answers

A:

This response would target a different source scenario: One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. It cannot establish the current acceptance requirement, which is: The repaired hop has the expected swap operation and carries a test packet. The relevant action is: Inspect the incoming label, outgoing label and interface on each affected LSR.

B:

Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions is a relevant step for the separate scenario in which a segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. It does not directly fix this case. Instead inspect the incoming label, outgoing label and interface on each affected LSR; verify: The repaired hop has the expected swap operation and carries a test packet.

D:

This answer would be more suitable when a provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance, where the corrective action is to restrict routing-policy matches and validate the import and export boundary. The failure here is different: Label-switching errors can occur even when control-plane endpoint reachability is good. Required validation: The repaired hop has the expected swap operation and carries a test packet.

Question 394

An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. Which technical distinction best describes the observed symptom?

  1. The key distinction is: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table.
  2. Protocol behavior: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions.
  3. Underlying principle: Discard routes may intentionally bound routing loops while dynamic specifics converge.
  4. Root design issue: Load sharing should be evaluated with relevant flows rather than one ping stream.

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:

Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table 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: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. 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: An equal-cost path test sends nearly all flows across one member while both links remain operational. 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 395

A new IPv6 static backup route is configured but a more-specific route points into a blackhole. What is the primary routing or switching concept illustrated?

  1. The governing rule is: A configured IPv6 static route still depends on reachable forwarding next hops.
  2. The key distinction is: Tunnel interfaces depend on a working underlay path between endpoints.
  3. Protocol behavior: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence.
  4. Underlying principle: More-specific routes can override an otherwise healthy IPv6 fallback.

Explanation

Correct Answer

D:

The critical observation is: More-specific routes can override an otherwise healthy IPv6 fallback. Correct it by taking this action: Inspect longest-match results and forwarding routes for the specific destination. Confirm the outcome with: The intended most-specific route changes to a valid next hop during failover.

Incorrect Answers

A:

The alternative addresses a router has an IPv6 default route but no usable next-hop reachability on the egress link, not the present root cause. Here the selected correction must reflect more-specific routes can override an otherwise healthy IPv6 fallback. Test for: The intended most-specific route changes to a valid next hop during failover.

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: More-specific routes can override an otherwise healthy IPv6 fallback. Required validation: The intended most-specific route changes to a valid next hop during failover.

C:

This option overlooks the decisive condition. Its supporting principle is dual-stack IS-IS troubleshooting requires family-specific advertisement evidence, while this scenario depends on more-specific routes can override an otherwise healthy IPv6 fallback. Verify the correction with: The intended most-specific route changes to a valid next hop during failover.

Question 396

A router has an IPv6 default route but no usable next-hop reachability on the egress link. Which statement identifies the key design assumption that failed?

  1. Root design issue: BGP family negotiation and route policy control IPv6 NLRI exchange.
  2. The governing rule is: IS-IS routing levels determine topology knowledge and area reachability.
  3. The key distinction is: A configured IPv6 static route still depends on reachable forwarding next hops.
  4. Protocol behavior: More-specific routes can override an otherwise healthy IPv6 fallback.

Explanation

Correct Answer

C:

This is the model-intended best choice because a configured IPv6 static route still depends on reachable forwarding next hops. The targeted correction is to confirm the IPv6 next-hop adjacency and active routing entry. Validate it by observing that the IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. The current case specifically calls for: Confirm the IPv6 next-hop adjacency and active routing entry. The required observed result is: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

B:

This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: The IPv6 FIB resolves the intended next hop and a test packet crosses the link. The relevant action is: Confirm the IPv6 next-hop adjacency and active routing entry.

D:

The alternative addresses a new IPv6 static backup route is configured but a more-specific route points into a blackhole, not the present root cause. Here the selected correction must reflect a configured IPv6 static route still depends on reachable forwarding next hops. Test for: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Question 397

An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. Which combined repair and acceptance criterion is strongest?

  1. Action: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Evidence: A segment trace follows the desired prefix or explicit adjacency.
  2. Repair: Verify whether PHP or explicit-null behavior is configured and intended. Check: The observed penultimate and egress labels agree with the supported LSP behavior.
  3. Change: Review reservation constraints and available resources rather than resetting all label sessions. Test: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Implement: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Verify: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Explanation

Correct Answer

B:

The case turns on the distinction that label stack changes can be legitimate parts of LSP forwarding design. Apply this concrete engineering step: Verify whether PHP or explicit-null behavior is configured and intended. An acceptable verification outcome is: The observed penultimate and egress labels agree with the supported LSP behavior.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is different segment types express different routing or link steering semantics, while this scenario depends on label stack changes can be legitimate parts of LSP forwarding design. Verify the correction with: The observed penultimate and egress labels agree with the supported LSP behavior.

C:

The proposed principle concerns another network fault: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Here, label stack changes can be legitimate parts of LSP forwarding design. The most direct correction is to verify whether PHP or explicit-null behavior is configured and intended, confirmed by the observed penultimate and egress labels agree with the supported LSP behavior.

D:

That result would be useful for a different failure, namely: A dual-stack peer is Established but the IPv6 customer route is absent. The current case specifically calls for: Verify whether PHP or explicit-null behavior is configured and intended. The required observed result is: The observed penultimate and egress labels agree with the supported LSP behavior.

Question 398

An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. Which combined repair and acceptance criterion is strongest?

  1. Control: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU. Accepted result: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.
  2. Action: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. Evidence: The remote PE learns and uses the intended IPv6 prefix.
  3. Repair: Verify reachability between tunnel source and destination addresses. Check: The remote tunnel endpoint is reachable through the intended underlay.
  4. Change: Enable and verify the intended IPv6 BGP family and export policy. Test: The selected inet6 route appears on the authorized IPv6 peer.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Remedy: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. Proof: The remote PE learns and uses the intended IPv6 prefix.

Incorrect Answers

A:

Verify tunnel protocol allowance, endpoint encapsulation and effective MTU is a relevant step for the separate scenario in which iPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. It does not directly fix this case. Instead inspect IPv6 reachability TLVs, family configuration and active inet6 route state; verify: The remote PE learns and uses the intended IPv6 prefix.

C:

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: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Required validation: The remote PE learns and uses the intended IPv6 prefix.

D:

This option overlooks the decisive condition. Its supporting principle is bGP family negotiation and route policy control IPv6 NLRI exchange, while this scenario depends on dual-stack IS-IS troubleshooting requires family-specific advertisement evidence. Verify the correction with: The remote PE learns and uses the intended IPv6 prefix.

Question 399

A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. What observable result most directly verifies the intended configuration?

  1. Acceptance check: The chosen protocol establishes the intended type of LSP.
  2. The test confirms that the internal peer has a valid route to the BGP next hop and installs the prefix.
  3. Expected observation: The labeled service route resolves after the intended LSP is restored.
  4. Verification result: The transport endpoint again resolves and a labeled probe succeeds.

Explanation

Correct Answer

C:

The case turns on the distinction that a usable IP path need not supply a suitable MPLS LSP or labeled transport path. Apply this concrete engineering step: Inspect label-switched next-hop resolution separately from generic IP reachability. An acceptable verification outcome is: The labeled service route resolves after the intended LSP is restored.

Incorrect Answers

A:

The proposed principle concerns another network fault: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Here, a usable IP path need not supply a suitable MPLS LSP or labeled transport path. The most direct correction is to inspect label-switched next-hop resolution separately from generic IP reachability, confirmed by the labeled service route resolves after the intended LSP is restored.

B:

That result would be useful for a different failure, namely: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. 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.

D:

Restore the required transport route and inspect label-signaling and next-hop state is a relevant step for the separate scenario in which a route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. It does not directly fix this case. Instead inspect label-switched next-hop resolution separately from generic IP reachability; verify: The labeled service route resolves after the intended LSP is restored.

Question 400

An IPv6 packet exceeds an underlay path MTU and the operator expects intermediate IPv6 routers to fragment it. What should the operations engineer do first to address the stated fault?

  1. Remediation: Apply and verify supported route policy at the intended routing import or export boundary.
  2. Recommended change: Review IPv6 path MTU discovery and endpoint fragmentation requirements.
  3. Next step: Inspect longest-match results and forwarding routes for the specific destination.
  4. Corrective action: Enable and verify the intended IPv6 BGP family and export policy.

Explanation

Correct Answer

B:

Correct diagnosis: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The appropriate action is: Review IPv6 path MTU discovery and endpoint fragmentation requirements. The follow-up evidence required is: The sender adapts to a validated path MTU and payload delivery succeeds.

Incorrect Answers

A:

This answer would be more suitable when an engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context, where the corrective action is to apply and verify supported route policy at the intended routing import or export boundary. The failure here is different: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Required validation: The sender adapts to a validated path MTU and payload delivery succeeds.

C:

More-specific routes can override an otherwise healthy IPv6 fallback describes a neighboring protocol concern. In this case the controlling fact is intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. A correct remediation would review IPv6 path MTU discovery and endpoint fragmentation requirements and demonstrate: The sender adapts to a validated path MTU and payload delivery succeeds.

D:

The proposed principle concerns another network fault: BGP family negotiation and route policy control IPv6 NLRI exchange. Here, intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The most direct correction is to review IPv6 path MTU discovery and endpoint fragmentation requirements, confirmed by the sender adapts to a validated path MTU and payload delivery succeeds.

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