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 14

Question 130

A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: MPLS relies on selected underlay transport reachability and policy eligibility. Action: Restore the required transport route and inspect label-signaling and next-hop state.
  2. Explanation: Label stack changes can be legitimate parts of LSP forwarding design. Repair: Verify whether PHP or explicit-null behavior is configured and intended.
  3. Fault mechanism: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Remediation: Review segment identifiers and forwarding under SR-MPLS.
  4. Root issue: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Correction: Restrict routing-policy matches and validate the import and export boundary.

Explanation

Correct Answer

A:

Because mPLS relies on selected underlay transport reachability and policy eligibility, the best response is to restore the required transport route and inspect label-signaling and next-hop state. A reviewer can close the technical case only after confirming that the transport endpoint again resolves and a labeled probe succeeds.

Incorrect Answers

B:

The proposed principle concerns another network fault: Label stack changes can be legitimate parts of LSP forwarding design. Here, mPLS relies on selected underlay transport reachability and policy eligibility. The most direct correction is to restore the required transport route and inspect label-signaling and next-hop state, confirmed by the transport endpoint again resolves and a labeled probe succeeds.

C:

That result would be useful for a different failure, namely: A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.

D:

This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The transport endpoint again resolves and a labeled probe succeeds. The relevant action is: Restore the required transport route and inspect label-signaling and next-hop state.

Question 131

An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. What is the most defensible network engineering correction?

  1. Corrective action: Explain local label significance and neighbor label binding.
  2. Apply this control: Distinguish signaling reservations from physical link speed and admission control.
  3. Remediation: Review reservation constraints and available resources rather than resetting all label sessions.
  4. Recommended change: Check client definitions, route-reflector session state and export policy.

Explanation

Correct Answer

B:

Underlying cause: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Corrective action: distinguish signaling reservations from physical link speed and admission control. Verify the outcome: A controlled setup respects the approved link reservation policy.

Incorrect Answers

A:

The alternative addresses an operator assumes MPLS labels are globally unique across the provider network, not the present root cause. Here the selected correction must reflect rSVP resource reservation may affect which additional constrained LSPs can be admitted. Test for: A controlled setup respects the approved link reservation policy.

C:

This option overlooks the decisive condition. Its supporting principle is rSVP LSP setup can fail resource or path constraints even with valid IP reachability, while this scenario depends on rSVP resource reservation may affect which additional constrained LSPs can be admitted. Verify the correction with: A controlled setup respects the approved link reservation policy.

D:

Route reflection can fail due to session or policy scope even when the route exists centrally describes a neighboring protocol concern. In this case the controlling fact is rSVP resource reservation may affect which additional constrained LSPs can be admitted. A correct remediation would distinguish signaling reservations from physical link speed and admission control and demonstrate: A controlled setup respects the approved link reservation policy.

Question 132

A BGP prefix remains rejected after an intended route filter update because an earlier term rejects it. What is the primary routing or switching concept illustrated?

  1. Protocol behavior: Route reflection can fail due to session or policy scope even when the route exists centrally.
  2. Underlying principle: OSPF DR selection depends on eligible routers and the current election event.
  3. Root design issue: BGP group inheritance and policy direction govern which advertisements are modified.
  4. The governing rule is: Policy evaluation order can short-circuit later intended acceptance.

Explanation

Correct Answer

D:

Correct diagnosis: Policy evaluation order can short-circuit later intended acceptance. The appropriate action is: Evaluate policy terms in effective order and test matching routes. The follow-up evidence required is: The approved route matches an accepting term and the denied route remains denied.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A route reflector receives a new branch prefix but one iBGP client never learns it. The current case specifically calls for: Evaluate policy terms in effective order and test matching routes. The required observed result is: The approved route matches an accepting term and the denied route remains denied.

B:

This response would target a different source scenario: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. It cannot establish the current acceptance requirement, which is: The approved route matches an accepting term and the denied route remains denied. The relevant action is: Evaluate policy terms in effective order and test matching routes.

C:

Map inbound and outbound policy points and confirm the intended communities is a relevant step for the separate scenario in which a service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. It does not directly fix this case. Instead evaluate policy terms in effective order and test matching routes; verify: The approved route matches an accepting term and the denied route remains denied.

Question 133

An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Label stack changes can be legitimate parts of LSP forwarding design.
  2. Protocol behavior: Different segment types express different routing or link steering semantics.
  3. Underlying principle: Traffic-engineering intent must be reflected in the signaled operational LSP path.
  4. Root design issue: Disabling loop prevention can introduce persistent interdomain routing loops.

Explanation

Correct Answer

A:

The critical observation is: Label stack changes can be legitimate parts of LSP forwarding design. Correct it by taking this action: Verify whether PHP or explicit-null behavior is configured and intended. Confirm the outcome with: The observed penultimate and egress labels agree with the supported LSP behavior.

Incorrect Answers

B:

Different segment types express different routing or link steering semantics describes a neighboring protocol concern. In this case the controlling fact is label stack changes can be legitimate parts of LSP forwarding design. A correct remediation would verify whether PHP or explicit-null behavior is configured and intended and demonstrate: The observed penultimate and egress labels agree with the supported LSP behavior.

C:

The proposed principle concerns another network fault: Traffic-engineering intent must be reflected in the signaled operational LSP path. 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 provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. 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 134

An operator configured an explicit RSVP path through a link that is now administratively down. What assessment accurately links the fault to its correction?

  1. Explanation: An LSP cannot follow an unavailable required hop. Repair: Update the engineered path constraints and verify candidate topology availability.
  2. Fault mechanism: MPLS relies on selected underlay transport reachability and policy eligibility. Remediation: Restore the required transport route and inspect label-signaling and next-hop state.
  3. Root issue: Moving route information between tables does not remove the need for a valid forwarding next hop. Correction: Evaluate routing-table relationships and next-hop resolution when using RIB groups.
  4. Cause: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Response: Distinguish signaling reservations from physical link speed and admission control.

Explanation

Correct Answer

A:

Correct diagnosis: An LSP cannot follow an unavailable required hop. The appropriate action is: Update the engineered path constraints and verify candidate topology availability. The follow-up evidence required is: The backup LSP establishes on a permitted alternate path.

Incorrect Answers

B:

The alternative addresses a route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes, not the present root cause. Here the selected correction must reflect an LSP cannot follow an unavailable required hop. Test for: The backup LSP establishes on a permitted alternate path.

C:

This answer would be more suitable when a route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there, where the corrective action is to evaluate routing-table relationships and next-hop resolution when using RIB groups. The failure here is different: An LSP cannot follow an unavailable required hop. Required validation: The backup LSP establishes on a permitted alternate path.

D:

This option overlooks the decisive condition. Its supporting principle is rSVP resource reservation may affect which additional constrained LSPs can be admitted, while this scenario depends on an LSP cannot follow an unavailable required hop. Verify the correction with: The backup LSP establishes on a permitted alternate path.

Question 135

A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. What should the operations engineer do first to address the stated fault?

  1. Apply this control: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.
  2. Remediation: Differentiate forwarding continuity under GRES from routing-protocol state preservation.
  3. Recommended change: Compare Hello/Dead event logs with loss and interface errors before tuning timers.
  4. Next step: Evaluate BFD liveness detection with the associated routing protocol.

Explanation

Correct Answer

D:

Underlying cause: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Corrective action: evaluate BFD liveness detection with the associated routing protocol. Verify the outcome: A controlled forwarding failure is detected within the approved target.

Incorrect Answers

A:

The proposed principle concerns another network fault: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Here, bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. The most direct correction is to evaluate BFD liveness detection with the associated routing protocol, confirmed by a controlled forwarding failure is detected within the approved target.

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 BFD liveness detection with the associated routing protocol. The required observed result is: A controlled forwarding failure is detected within the approved target.

C:

This response would target a different source scenario: Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It cannot establish the current acceptance requirement, which is: A controlled forwarding failure is detected within the approved target. The relevant action is: Evaluate BFD liveness detection with the associated routing protocol.

Question 136

An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: The point-to-point adjacency forms without an unnecessary DR election.
  2. Verification result: A post-change route view selects the approved shortest path.
  3. Closeout evidence: A negative test proves the unrelated customer prefix is absent from the target table.
  4. Acceptance check: The adjacency advances through database synchronization to Full.

Explanation

Correct Answer

D:

Because neighbor discovery can succeed even when database exchange parameters prevent completion, the best response is to check MTU and interface compatibility and inspect neighbor-state details. A reviewer can close the technical case only after confirming that the adjacency advances through database synchronization to Full.

Incorrect Answers

A:

This answer would be more suitable when an engineer expects a designated router to be elected on a point-to-point OSPF circuit, where the corrective action is to select the correct network-type behavior and inspect the neighbor-state model. The failure here is different: Neighbor discovery can succeed even when database exchange parameters prevent completion. Required validation: The adjacency advances through database synchronization to Full.

B:

This option overlooks the decisive condition. Its supporting principle is oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone, while this scenario depends on neighbor discovery can succeed even when database exchange parameters prevent completion. Verify the correction with: The adjacency advances through database synchronization to Full.

C:

Route redistribution must be intentionally scoped to prevent cross-tenant leakage describes a neighboring protocol concern. In this case the controlling fact is neighbor discovery can succeed even when database exchange parameters prevent completion. A correct remediation would check MTU and interface compatibility and inspect neighbor-state details and demonstrate: The adjacency advances through database synchronization to Full.

Question 137

A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. What remediation is most directly applicable?

  1. Next step: Review MAC learning and unknown-unicast handling within the correct bridge domain.
  2. Corrective action: Generate controlled frames and observe normal learning on the correct bridge domain.
  3. Apply this control: Document VLAN-aware versus flexible tagging and unit classification requirements.
  4. Remediation: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.

Explanation

Correct Answer

A:

Underlying cause: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. Corrective action: review MAC learning and unknown-unicast handling within the correct bridge domain. Verify the outcome: A frame trace shows only expected domain members receive the unknown destination.

Incorrect Answers

B:

Generate controlled frames and observe normal learning on the correct bridge domain is a relevant step for the separate scenario in which a MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. It does not directly fix this case. Instead review MAC learning and unknown-unicast handling within the correct bridge domain; verify: A frame trace shows only expected domain members receive the unknown destination.

C:

The alternative addresses an Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation, not the present root cause. Here the selected correction must reflect bridges learn source MAC locations and flood unknown destinations within a permitted domain. Test for: A frame trace shows only expected domain members receive the unknown destination.

D:

This answer would be more suitable when two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP, where the corrective action is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The failure here is different: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. Required validation: A frame trace shows only expected domain members receive the unknown destination.

Question 138

An equal-cost path test sends nearly all flows across one member while both links remain operational. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Implement: Validate forwarding load-sharing configuration and run representative multi-flow traffic. Verify: A documented multi-flow test matches the configured distribution policy.
  2. Control: Compare installed forwarding entries with interface operational status and adjacency resolution. Accepted result: A test packet follows the expected active forwarding next hop and interface.
  3. Action: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. Evidence: A controlled flow test verifies the selected load-sharing behavior.
  4. Repair: Review router priorities and the nonpreemptive properties of DR elections. Check: The elected DR and BDR align with the tested election conditions.

Explanation

Correct Answer

A:

Because load sharing should be evaluated with relevant flows rather than one ping stream, the best response is to validate forwarding load-sharing configuration and run representative multi-flow traffic. A reviewer can close the technical case only after confirming that a documented multi-flow test matches the configured distribution policy.

Incorrect Answers

B:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. Here, load sharing should be evaluated with relevant flows rather than one ping stream. The most direct correction is to validate forwarding load-sharing configuration and run representative multi-flow traffic, confirmed by a documented multi-flow test matches the configured distribution policy.

C:

That result would be useful for a different failure, namely: Two equal-cost next hops exist but a customer assumes every successive packet must alternate between links. The current case specifically calls for: Validate forwarding load-sharing configuration and run representative multi-flow traffic. The required observed result is: A documented multi-flow test matches the configured distribution policy.

D:

This response would target a different source scenario: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. It cannot establish the current acceptance requirement, which is: A documented multi-flow test matches the configured distribution policy. The relevant action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic.

Question 139

Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. Which change best corrects the failure without losing the intended design?

  1. Remediation: Check VRRP group, interface, priority, advertisements and tracking conditions.
  2. Recommended change: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff.
  3. Next step: Assign distinct service encapsulation and verify edge translation rules.
  4. Corrective action: Validate outer tag encapsulation and EtherType expectations across the handoff.

Explanation

Correct Answer

B:

Underlying cause: Provider bridging service tags must be applied and removed at the designed boundaries. Corrective action: check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Verify the outcome: A capture shows the expected outer service tag between provider edges.

Incorrect Answers

A:

The alternative addresses a VRRP backup router does not take over when the primary gateway interface is disabled, not the present root cause. Here the selected correction must reflect provider bridging service tags must be applied and removed at the designed boundaries. Test for: A capture shows the expected outer service tag between provider edges.

C:

This option overlooks the decisive condition. Its supporting principle is provider outer VLAN classification must preserve tenant isolation, while this scenario depends on provider bridging service tags must be applied and removed at the designed boundaries. Verify the correction with: A capture shows the expected outer service tag between provider edges.

D:

Stacked VLAN services require compatible tagging interpretation at both ends describes a neighboring protocol concern. In this case the controlling fact is provider bridging service tags must be applied and removed at the designed boundaries. A correct remediation would check Q-in-Q input/output encapsulation and rewrite behavior at the handoff and demonstrate: A capture shows the expected outer service tag between provider edges.

Question 140

A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Add a precise prefix and instance match, then inspect effective imports.
  2. Remediation: Restrict routing-policy matches and validate the import and export boundary.
  3. Recommended change: Distinguish internal LSAs from externally originated route information.
  4. Next step: Verify recursive next-hop reachability before relying on the static route.

Explanation

Correct Answer

B:

Because route redistribution must be intentionally scoped to prevent cross-tenant leakage, the best response is to restrict routing-policy matches and validate the import and export boundary. A reviewer can close the technical case only after confirming that a negative test proves the unrelated customer prefix is absent from the target table.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. The current case specifically calls for: Restrict routing-policy matches and validate the import and export boundary. The required observed result is: A negative test proves the unrelated customer prefix is absent from the target table.

C:

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 restrict routing-policy matches and validate the import and export boundary; verify: A negative test proves the unrelated customer prefix is absent from the target table.

D:

The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect route redistribution must be intentionally scoped to prevent cross-tenant leakage. Test for: A negative test proves the unrelated customer prefix is absent from the target table.

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