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 10

Question 90

A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. Which technical explanation and controlled action address the symptom?

  1. Fault mechanism: Labels are generally meaningful within the forwarding context where they are allocated. Remediation: Explain local label significance and neighbor label binding.
  2. Root issue: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Correction: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  3. Cause: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Response: Document the discard behavior and determine whether the aggregate should remain advertised.
  4. Diagnosis: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Action: Check SR label advertisements, segment configuration and installed MPLS forwarding.

Explanation

Correct Answer

B:

This is the model-intended best choice because end-to-end signaling state alone cannot pinpoint a data-plane label failure. The targeted correction is to collect hop-local LFIB, label forwarding and interface counters along the LSP. Validate it by observing that the corrected transit hop forwards the expected incoming label to its planned outgoing label.

Incorrect Answers

A:

Labels are generally meaningful within the forwarding context where they are allocated describes a neighboring protocol concern. In this case the controlling fact is end-to-end signaling state alone cannot pinpoint a data-plane label failure. A correct remediation would collect hop-local LFIB, label forwarding and interface counters along the LSP and demonstrate: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

C:

That result would be useful for a different failure, namely: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. The current case specifically calls for: Collect hop-local LFIB, label forwarding and interface counters along the LSP. The required observed result is: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

D:

This response would target a different source scenario: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. It cannot establish the current acceptance requirement, which is: The corrected transit hop forwards the expected incoming label to its planned outgoing label. The relevant action is: Collect hop-local LFIB, label forwarding and interface counters along the LSP.

Question 91

An IS-IS route disappears after a policy update while the LSP database still contains the topology. What implementation step and validation result should be selected?

  1. Change: Review current DIS election rules for the network and protocol instance. Test: The LAN's DIS and pseudonode LSP match the documented protocol state.
  2. Implement: Coordinate authentication parameters and test the key change under maintenance controls. Verify: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.
  3. Control: Inspect route import policy and forwarding selection separately from LSP presence. Accepted result: The route policy and active table agree with the approved advertised prefixes.
  4. Action: Check the IPv6 family configuration and advertised reachability rather than rebuilding IPv4 adjacency. Evidence: Both address families display their expected prefixes through the same stable topology.

Explanation

Correct Answer

C:

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

Incorrect Answers

A:

The alternative addresses an IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node, not the present root cause. Here the selected correction must reflect a learned LSP does not ensure a destination is selected into the active routing table. Test for: The route policy and active table agree with the approved advertised prefixes.

B:

This answer would be more suitable when a customer edge loses its OSPF neighbor after an authentication key rollover, where the corrective action is to coordinate authentication parameters and test the key change under maintenance controls. The failure here is different: A learned LSP does not ensure a destination is selected into the active routing table. Required validation: The route policy and active table agree with the approved advertised prefixes.

D:

IS-IS can convey multiple address families with appropriate support describes a neighboring protocol concern. In this case the controlling fact is a learned LSP does not ensure a destination is selected into the active routing table. A correct remediation would inspect route import policy and forwarding selection separately from LSP presence and demonstrate: The route policy and active table agree with the approved advertised prefixes.

Question 92

A new redundant uplink produces a broadcast storm on an access VLAN. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Repair: Distinguish access port traffic from trunk tagging behavior. Check: An end-host packet enters the correct VLAN without requiring endpoint tagging.
  2. Change: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain. Test: The ring converges with no forwarding loop and sustained connectivity.
  3. Implement: Apply supported root protection at the appropriate customer-facing boundary. Verify: A superior BPDU test preserves the intended root with a logged protective state.
  4. Control: Review root protection at the provider-facing boundary. Accepted result: A superior BPDU test does not move the approved provider root.

Explanation

Correct Answer

B:

Because loop prevention depends on compatible STP participation across redundant Ethernet links, the best response is to inspect STP state and enable the approved spanning-tree protocol for that bridge domain. A reviewer can close the technical case only after confirming that the ring converges with no forwarding loop and sustained connectivity.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. The current case specifically calls for: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain. The required observed result is: The ring converges with no forwarding loop and sustained connectivity.

C:

Apply supported root protection at the appropriate customer-facing boundary is a relevant step for the separate scenario in which a provider STP domain changes root when a customer sends superior BPDUs from an access port. It does not directly fix this case. Instead inspect STP state and enable the approved spanning-tree protocol for that bridge domain; verify: The ring converges with no forwarding loop and sustained connectivity.

D:

The alternative addresses a carrier attachment must not allow a customer switch to become the provider's root bridge, not the present root cause. Here the selected correction must reflect loop prevention depends on compatible STP participation across redundant Ethernet links. Test for: The ring converges with no forwarding loop and sustained connectivity.

Question 93

A provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge. What implementation step and validation result should be selected?

  1. Action: Test effective MTU and path MTU discovery across the encapsulated route. Evidence: A controlled large-payload test succeeds after MTU or MSS adjustment.
  2. Repair: Treat tunnel decapsulation as a routing and security boundary. Check: Only authorized customer prefixes enter or leave the decapsulated routing context.
  3. Change: Verify reachability between tunnel source and destination addresses. Test: The remote tunnel endpoint is reachable through the intended underlay.
  4. Implement: 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.

Explanation

Correct Answer

B:

The case turns on the distinction that encapsulation does not replace explicit customer route filtering and access policy. Apply this concrete engineering step: Treat tunnel decapsulation as a routing and security boundary. An acceptable verification outcome is: Only authorized customer prefixes enter or leave the decapsulated routing context.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is gRE encapsulation overhead can expose MTU blackholes for larger payloads, while this scenario depends on encapsulation does not replace explicit customer route filtering and access policy. Verify the correction with: Only authorized customer prefixes enter or leave the decapsulated routing context.

C:

The proposed principle concerns another network fault: Tunnel interfaces depend on a working underlay path between endpoints. Here, encapsulation does not replace explicit customer route filtering and access policy. The most direct correction is to treat tunnel decapsulation as a routing and security boundary, confirmed by only authorized customer prefixes enter or leave the decapsulated routing context.

D:

That result would be useful for a different failure, namely: An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. The current case specifically calls for: Treat tunnel decapsulation as a routing and security boundary. The required observed result is: Only authorized customer prefixes enter or leave the decapsulated routing context.

Question 94

A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. Which technical explanation and controlled action address the symptom?

  1. Root issue: Neighbor state must be traced through transport before modifying route policy. Correction: Verify IP reachability, routing instance context, TCP transport and session authentication.
  2. Cause: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Response: Review EBGP multihop transport reachability and session parameters.
  3. Diagnosis: A stale label binding cannot compensate for unusable transport forwarding. Action: Compare label bindings with the active IGP next hop and installed forwarding entries.
  4. Explanation: BGP selection is policy-driven and is not equivalent to IGP least-hop routing. Repair: Trace the applicable BGP route-selection steps and local policies.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Remedy: Review EBGP multihop transport reachability and session parameters. Proof: The TCP session establishes across the intended transport path.

Incorrect Answers

A:

Verify IP reachability, routing instance context, TCP transport and session authentication is a relevant step for the separate scenario in which a BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It does not directly fix this case. Instead review EBGP multihop transport reachability and session parameters; verify: The TCP session establishes across the intended transport path.

C:

This answer would be more suitable when an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop, where the corrective action is to compare label bindings with the active IGP next hop and installed forwarding entries. The failure here is different: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Required validation: The TCP session establishes across the intended transport path.

D:

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 eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Verify the correction with: The TCP session establishes across the intended transport path.

Question 95

A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. Which technical distinction best describes the observed symptom?

  1. The key distinction is: IS-IS route dissemination follows hierarchical level boundaries.
  2. Protocol behavior: BGP route acceptance must be constrained rather than inferred from neighbor identity.
  3. Underlying principle: A learned LSP does not ensure a destination is selected into the active routing table.
  4. Root design issue: IS-IS routing levels determine topology knowledge and area reachability.

Explanation

Correct Answer

D:

Underlying cause: IS-IS routing levels determine topology knowledge and area reachability. Corrective action: review Level 1 and Level 2 routing roles and their intended boundaries. Verify the outcome: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Incorrect Answers

A:

The proposed principle concerns another network fault: IS-IS route dissemination follows hierarchical level boundaries. Here, iS-IS routing levels determine topology knowledge and area reachability. The most direct correction is to review Level 1 and Level 2 routing roles and their intended boundaries, confirmed by an eligible Level 2 or L1/L2 path provides the approved interarea destination.

B:

That result would be useful for a different failure, namely: A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. The current case specifically calls for: Review Level 1 and Level 2 routing roles and their intended boundaries. The required observed result is: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

C:

This response would target a different source scenario: An IS-IS route disappears after a policy update while the LSP database still contains the topology. It cannot establish the current acceptance requirement, which is: An eligible Level 2 or L1/L2 path provides the approved interarea destination. The relevant action is: Review Level 1 and Level 2 routing roles and their intended boundaries.

Question 96

Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. What observable result most directly verifies the intended configuration?

  1. Closeout evidence: The correct summarized route appears in the receiving area's route table.
  2. Acceptance check: The intended lower-total-cost path wins under steady-state conditions.
  3. The test confirms that the peers progress to the expected adjacency state and exchange LSAs.
  4. Expected observation: The test demonstrates loop prevention without advertising false service reachability.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: OSPF adjacency requires compatible area and interface parameters. Remedy: Align the area membership and verify OSPF interface settings on both sides. Proof: The peers progress to the expected adjacency state and exchange LSAs.

Incorrect Answers

A:

This answer would be more suitable when an area border router stops advertising an expected summarized interarea route after a policy change, where the corrective action is to inspect ABR area configuration, route export rules and summary policy. The failure here is different: OSPF adjacency requires compatible area and interface parameters. Required validation: The peers progress to the expected adjacency state and exchange LSAs.

B:

This option overlooks the decisive condition. Its supporting principle is oSPF normally prefers the least accumulated metric to a destination, while this scenario depends on oSPF adjacency requires compatible area and interface parameters. Verify the correction with: The peers progress to the expected adjacency state and exchange LSAs.

D:

The proposed principle concerns another network fault: Discard routes may intentionally bound routing loops while dynamic specifics converge. Here, oSPF adjacency requires compatible area and interface parameters. The most direct correction is to align the area membership and verify OSPF interface settings on both sides, confirmed by the peers progress to the expected adjacency state and exchange LSAs.

Question 97

An operator assumes MPLS labels are globally unique across the provider network. Which technical distinction best describes the observed symptom?

  1. Root design issue: A usable IP path need not supply a suitable MPLS LSP or labeled transport path.
  2. The governing rule is: BGP message types have separate roles in session formation and reachability exchange.
  3. The key distinction is: Labels are generally meaningful within the forwarding context where they are allocated.
  4. Protocol behavior: LDP signaling depends on the routing and transport state of its endpoints.

Explanation

Correct Answer

C:

The critical observation is: Labels are generally meaningful within the forwarding context where they are allocated. Correct it by taking this action: Explain local label significance and neighbor label binding. Confirm the outcome with: A path test records locally valid incoming and outgoing label mappings.

Incorrect Answers

A:

This response would target a different source scenario: A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. It cannot establish the current acceptance requirement, which is: A path test records locally valid incoming and outgoing label mappings. The relevant action is: Explain local label significance and neighbor label binding.

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 explain local label significance and neighbor label binding; verify: A path test records locally valid incoming and outgoing label mappings.

D:

This answer would be more suitable when a provider's LDP neighbors disappear after an IGP outage while physical links remain up, where the corrective action is to check transport reachability, LDP session state and the relevant IGP routes. The failure here is different: Labels are generally meaningful within the forwarding context where they are allocated. Required validation: A path test records locally valid incoming and outgoing label mappings.

Question 98

One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. Which combined repair and acceptance criterion is strongest?

  1. Action: Evaluate policy terms in effective order and test matching routes. Evidence: The approved route matches an accepting term and the denied route remains denied.
  2. Repair: Create explicit import policy and prefix limits aligned to customer contracts. Check: Only approved customer prefixes enter the provider's active routing table.
  3. Change: Split export policy by authorized customer scope and verify negative advertisements. Test: The unauthorized customer receives no leaked prefixes in a route advertisement check.
  4. Implement: Distinguish signaling reservations from physical link speed and admission control. Verify: A controlled setup respects the approved link reservation policy.

Explanation

Correct Answer

C:

Correct diagnosis: BGP group-level export policies must preserve customer routing isolation. The appropriate action is: Split export policy by authorized customer scope and verify negative advertisements. The follow-up evidence required is: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Incorrect Answers

A:

Policy evaluation order can short-circuit later intended acceptance describes a neighboring protocol concern. In this case the controlling fact is bGP group-level export policies must preserve customer routing isolation. A correct remediation would split export policy by authorized customer scope and verify negative advertisements and demonstrate: The unauthorized customer receives no leaked prefixes in a route advertisement check.

B:

The proposed principle concerns another network fault: BGP route acceptance must be constrained rather than inferred from neighbor identity. Here, bGP group-level export policies must preserve customer routing isolation. The most direct correction is to split export policy by authorized customer scope and verify negative advertisements, confirmed by the unauthorized customer receives no leaked prefixes in a route advertisement check.

D:

This response would target a different source scenario: An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. It cannot establish the current acceptance requirement, which is: The unauthorized customer receives no leaked prefixes in a route advertisement check. The relevant action is: Split export policy by authorized customer scope and verify negative advertisements.

Question 99

A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. Which evidence would justify closing this troubleshooting case?

  1. The test confirms that a segment trace follows the desired prefix or explicit adjacency.
  2. Expected observation: The intended SR transport path forwards without unintended dependence on the retired LDP path.
  3. Verification result: The TCP session establishes across the intended transport path.
  4. Closeout evidence: The repaired hop has the expected swap operation and carries a test packet.

Explanation

Correct Answer

B:

Underlying cause: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Corrective action: check SR label advertisements, segment configuration and installed MPLS forwarding. Verify the outcome: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Incorrect Answers

A:

The alternative addresses a segment routing node uses a prefix segment but the operator treats it as a local adjacency segment, not the present root cause. Here the selected correction must reflect lDP and SR-MPLS may coexist but each needs its own valid label/route state. Test for: The intended SR transport path forwards without unintended dependence on the retired LDP path.

C:

This option overlooks the decisive condition. Its supporting principle is eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy, while this scenario depends on lDP and SR-MPLS may coexist but each needs its own valid label/route state. Verify the correction with: The intended SR transport path forwards without unintended dependence on the retired LDP path.

D:

Label-switching errors can occur even when control-plane endpoint reachability is good describes a neighboring protocol concern. In this case the controlling fact is lDP and SR-MPLS may coexist but each needs its own valid label/route state. A correct remediation would check SR label advertisements, segment configuration and installed MPLS forwarding and demonstrate: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Question 100

An OSPF route appears longer than expected after failover because a backup link's cost was never verified. Which combined repair and acceptance criterion is strongest?

  1. Implement: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. Verify: Each router is uniquely identified and the link-state database converges.
  2. Control: Compare area, interface mode, timers, authentication and physical status on both endpoints. Accepted result: The corrected link reaches stable Full adjacency and exchanges the intended routes.
  3. Action: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Evidence: When the primary fails the documented backup path is selected without loops.
  4. Repair: Inspect route import policy and forwarding selection separately from LSP presence. Check: The route policy and active table agree with the approved advertised prefixes.

Explanation

Correct Answer

C:

This is the model-intended best choice because failover paths are governed by their actual configured metrics. The targeted correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Validate it by observing that when the primary fails the documented backup path is selected without loops.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. The current case specifically calls for: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. The required observed result is: When the primary fails the documented backup path is selected without loops.

B:

This response would target a different source scenario: A new OSPF uplink remains down at the adjacency stage after a router replacement. It cannot establish the current acceptance requirement, which is: When the primary fails the documented backup path is selected without loops. The relevant action is: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

D:

The alternative addresses an IS-IS route disappears after a policy update while the LSP database still contains the topology, not the present root cause. Here the selected correction must reflect failover paths are governed by their actual configured metrics. Test for: When the primary fails the documented backup path is selected without loops.

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