Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 640

A support escalation at Crestpoint Research describes: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Where should the Junos operator look first for decisive evidence?

  1. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.
  2. Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.
  3. Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
  4. Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

Correct answer: C

Explanation of each choice

A.

This check may help with another root cause, for example: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. It does not test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.

B.

That evidence could be normal while the reported defect persists. It is aimed at: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Instead inspect: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.

C.

Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.

D.

This check may help with another root cause, for example: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. It does not test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.

Question 641

During a Junos network change at Eastvale MetroNet, the engineer observes: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which remediation most directly fixes the described problem?

  1. Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.
  2. Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.
  3. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.
  4. Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

Correct answer: D

Explanation of each choice

A.

The other action is relevant when An MPLS service fails for one destination though IGP adjacencies and transport IP routes are stable; the team needs to identify the first broken label operation. The current case instead requires: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

B.

That would address a separate configuration fault: An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. This stem identifies a different cause, corrected by: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

C.

This action may apply to a different problem, for example: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

D.

Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. A direct acceptance test is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

Question 642

The Junos team at Eastvale MetroNet needs a success criterion for this defect: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which observed result most precisely confirms the intended repair?

  1. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
  2. Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.
  3. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  4. The transit forwarding entry maps the expected incoming label to the downstream outgoing label and packets progress to the next LSR.

Correct answer: A

Explanation of each choice

A.

The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

B.

That check proves something else, such as: An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. It could pass while the stated problem remains. The targeted evidence here is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

C.

This would be valid for another situation: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. It does not establish that the failing boundary in this scenario works; verify: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

D.

The observation confirms a different component's behavior. Its source context is: A provider replaces an MPLS transit router and packets fail at the next hop because the local forwarding table has an invalid outgoing label operation. In this case the success criterion is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

Question 643

While analyzing a service failure at Eastvale MetroNet, the following is observed: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.
  2. SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.
  3. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  4. RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

Correct answer: D

Explanation of each choice

A.

This explains a separate protocol behavior: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. In the current facts, the controlling mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

B.

The statement can be true when A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. But it does not explain the reported failure. Here: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

C.

That principle belongs to a different service stage: An MPLS service fails for one destination though IGP adjacencies and transport IP routes are stable; the team needs to identify the first broken label operation. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

D.

RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling. The key distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. Accordingly the remedy is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

Question 644

The following provider defect remains uncorrected at Eastvale MetroNet: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. What is the most direct service or security risk of leaving it unresolved?

  1. A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
  2. An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
  3. An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
  4. A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. Here the most direct failure path is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

B.

An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP. The direct mitigation is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

C.

That consequence is more closely associated with another deficiency, such as: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

D.

It is a risk in another topology or protocol state: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Here the most direct failure path is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

Question 645

A support escalation at Eastvale MetroNet describes: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Where should the Junos operator look first for decisive evidence?

  1. Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
  2. Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
  3. Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.
  4. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.

Correct answer: A

Explanation of each choice

A.

Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

B.

This check may help with another root cause, for example: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. It does not test the first failed condition; start with: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

C.

That evidence could be normal while the reported defect persists. It is aimed at: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. Instead inspect: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

D.

The check diagnoses a different layer of service. Its source issue is: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. The relevant initial check is: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

Question 646

The provider operations team at Bridgeway Cloud reports: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which implementation decision best corrects the cause?

  1. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.
  2. Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
  3. Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.
  4. Check the downstream label advertisement and configure supported penultimate-hop popping behavior to remove the intended transport label before egress when appropriate.

Correct answer: B

Explanation of each choice

A.

This action may apply to a different problem, for example: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

B.

Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. A direct acceptance test is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

C.

That would address a separate configuration fault: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. This stem identifies a different cause, corrected by: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

D.

This action may apply to a different problem, for example: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. It does not repair the stated failure boundary. The case-specific reason is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

Question 647

During a post-change check at Bridgeway Cloud, the original condition was: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. What evidence would validate the corrected behavior?

  1. The transit forwarding entry maps the expected incoming label to the downstream outgoing label and packets progress to the next LSR.
  2. The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
  3. A penultimate transit hop performs the expected pop and the egress sees the remaining service label or IP packet matching the LSP design.
  4. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

Correct answer: D

Explanation of each choice

A.

This would be valid for another situation: A provider replaces an MPLS transit router and packets fail at the next hop because the local forwarding table has an invalid outgoing label operation. It does not establish that the failing boundary in this scenario works; verify: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

B.

The observation confirms a different component's behavior. Its source context is: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. In this case the success criterion is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

C.

That check proves something else, such as: A provider sees an implicit-null binding from the egress but its transit operator misreads that as a request to forward a literal implicit-null label in data traffic. It could pass while the stated problem remains. The targeted evidence here is: The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

D.

The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

Question 648

At Bridgeway Cloud, an engineer is asked to explain this case: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which underlying routing or switching principle accounts for the appropriate solution?

  1. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  2. RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
  3. Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state.
  4. An MPLS shim header contains a 20-bit label, 3-bit traffic-class field, 1-bit bottom-of-stack indicator and 8-bit TTL.

Correct answer: B

Explanation of each choice

A.

That principle belongs to a different service stage: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

B.

RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling. The key distinction is: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem. Accordingly the remedy is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

C.

The statement can be true when A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. But it does not explain the reported failure. Here: The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

D.

That principle belongs to a different service stage: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. The directly relevant mechanism is: RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

Question 649

A risk assessment at Bridgeway Cloud identifies: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. Which practical consequence is most specifically tied to this failure?

  1. A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.
  2. An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.
  3. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.
  4. Invalid transit label swapping sends packets to a neighbor with no matching label entry, causing packet discard despite healthy IP connectivity.

Correct answer: B

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

B.

An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP. The direct mitigation is: Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.

C.

The concern could occur elsewhere when An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. For the stated scenario, the immediate risk is: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

D.

That consequence is more closely associated with another deficiency, such as: A transit LSR receives a labeled frame but sends a packet bearing the same incoming label to the next hop when the downstream binding expects another label. The described fault instead exposes: An engineered transport path stays unusable or violates intended constraints if its signaling failure is ignored and traffic silently follows another LSP.

Question 650

The on-call engineer at Bridgeway Cloud receives this fault report: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. What initial check best isolates the actual failing protocol stage?

  1. Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
  2. Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.
  3. Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.
  4. Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

Correct answer: A

Explanation of each choice

A.

Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.

B.

The check diagnoses a different layer of service. Its source issue is: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. The relevant initial check is: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

C.

This check may help with another root cause, for example: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. It does not test the first failed condition; start with: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

D.

That evidence could be normal while the reported defect persists. It is aimed at: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Instead inspect: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports