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 63

Question 620

During provider troubleshooting at Oakbend Education, this symptom is observed: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. Which targeted inspection should precede remediation?

  1. Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.
  2. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.
  3. Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.
  4. Inspect downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.

Correct answer: C

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: 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. The relevant initial check is: Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

B.

The check diagnoses a different layer of service. Its source issue is: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. The relevant initial check is: Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

C.

Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution. A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. Instead inspect: Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

Question 621

A production change request at Stonebridge Hospitality includes this finding: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. What should the engineer change to address it?

  1. Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.
  2. Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.
  3. Check the downstream label advertisement and configure supported penultimate-hop popping behavior to remove the intended transport label before egress when appropriate.
  4. Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

Correct answer: A

Explanation of each choice

A.

Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation. The case-specific reason is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together. A direct acceptance test is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

B.

This action may apply to a different problem, for example: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. It does not repair the stated failure boundary. The case-specific reason is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

C.

The other action is relevant when A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. The current case instead requires: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation. The distinction is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

D.

That would address a separate configuration fault: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. This stem identifies a different cause, corrected by: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.

Question 622

After Stonebridge Hospitality applies its proposed fix to this problem — An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. — which observation best proves the specific failure has been resolved?

  1. A penultimate transit hop performs the expected pop and the egress sees the remaining service label or IP packet matching the LSP design.
  2. The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.
  3. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  4. The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.

Correct answer: B

Explanation of each choice

A.

That check proves something else, such as: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. It could pass while the stated problem remains. The targeted evidence here is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

B.

The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path. IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

C.

The observation confirms a different component's behavior. Its source context is: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. In this case the success criterion is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

D.

That check proves something else, such as: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. It could pass while the stated problem remains. The targeted evidence here is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

Question 623

An architecture review at Stonebridge Hospitality examines the following symptom: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. What Junos or protocol mechanism is most directly responsible?

  1. Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.
  2. LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
  3. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  4. A transit MPLS router normally swaps an incoming transport label with the outgoing label selected for the same forwarding equivalence class.

Correct answer: A

Explanation of each choice

A.

Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context. The key distinction is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together. Accordingly the remedy is: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.

B.

That principle belongs to a different service stage: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. The directly relevant mechanism is: Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.

C.

This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.

D.

The statement can be true when 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. But it does not explain the reported failure. Here: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

Question 624

The team at Stonebridge Hospitality defers a fix for this condition: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. What failure is most likely if no targeted control is applied?

  1. An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
  2. Misunderstanding implicit null can lead to incorrect troubleshooting assumptions or malformed label handling at an MPLS edge.
  3. A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.
  4. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

Correct answer: C

Explanation of each choice

A.

The concern could occur elsewhere when Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. For the stated scenario, the immediate risk is: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

B.

That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

C.

A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core. The direct mitigation is: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.

D.

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: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

Question 625

During provider troubleshooting at Stonebridge Hospitality, this symptom is observed: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. Which targeted inspection should precede remediation?

  1. Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
  2. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.
  3. Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
  4. Inspect downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.

Correct answer: C

Explanation of each choice

A.

This check may help with another root cause, for example: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. It does not test the first failed condition; start with: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.

B.

That evidence could be normal while the reported defect persists. It is aimed at: A nested LSP packet arrives with multiple labels and an observer cannot determine which label is bottom of stack or where the TTL is carried. Instead inspect: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.

C.

Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop. IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

D.

This check may help with another root cause, for example: 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 does not test the first failed condition; start with: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.

Question 626

At Canal City University, a service provider router shows this failure: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. What is the best targeted configuration or operations action?

  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 appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.
  3. Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
  4. Verify the inbound label binding and correct the transit MPLS swap operation using the downstream-advertised label for the FEC.

Correct answer: B

Explanation of each choice

A.

The other action is relevant when A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. The current case instead requires: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation. The distinction is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

B.

Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation. The case-specific reason is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together. A direct acceptance test is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

C.

This action may apply to a different problem, for example: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. It does not repair the stated failure boundary. The case-specific reason is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

D.

The other action is relevant when 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 current case instead requires: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation. The distinction is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

Question 627

A change auditor at Canal City University must validate remediation of this finding: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Which test outcome is the strongest acceptance evidence?

  1. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  2. The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.
  3. The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
  4. The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

Correct answer: B

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. In this case the success criterion is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

B.

The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path. IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

C.

This would be valid for another situation: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. It does not establish that the failing boundary in this scenario works; verify: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

D.

The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

Question 628

The operations training team at Canal City University discusses this issue: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Which technical explanation matches the intended correction?

  1. LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
  2. An MPLS shim header contains a 20-bit label, 3-bit traffic-class field, 1-bit bottom-of-stack indicator and 8-bit TTL.
  3. Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.
  4. Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.

Correct answer: C

Explanation of each choice

A.

This explains a separate protocol behavior: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. In the current facts, the controlling mechanism is: Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.

B.

The statement can be true when A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. But it does not explain the reported failure. Here: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

C.

Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context. The key distinction is: IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together. Accordingly the remedy is: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.

D.

This explains a separate protocol behavior: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. In the current facts, the controlling mechanism is: Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.

Question 629

At Canal City University, a service acceptance review considers the unresolved issue: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Which operational exposure follows most directly?

  1. A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
  2. Misunderstanding implicit null can lead to incorrect troubleshooting assumptions or malformed label handling at an MPLS edge.
  3. A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.
  4. A decoding error can hide wrong label forwarding, incorrect QoS marking or TTL expiry on a transit hop.

Correct answer: C

Explanation of each choice

A.

It is a risk in another topology or protocol state: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. Here the most direct failure path is: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

B.

The concern could occur elsewhere when A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. For the stated scenario, the immediate risk is: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

C.

A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core. The direct mitigation is: Repair the appropriate LSP reachability and transport-route resolution used by the ingress routing table, and verify label-forwarding installation.

D.

It is a risk in another topology or protocol state: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. Here the most direct failure path is: A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

Question 630

Before changing configuration at Canal City University, an engineer investigates: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Which first diagnostic most directly tests the suspected cause?

  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 downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.
  4. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.

Correct answer: B

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. The relevant initial check is: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.

B.

Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop. IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.

C.

That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.

D.

The check diagnoses a different layer of service. Its source issue is: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. The relevant initial check is: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next 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