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 62

Question 610

The on-call engineer at Northline Communications receives this fault report: 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. What initial check best isolates the actual failing protocol stage?

  1. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.
  2. Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
  3. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.
  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.

Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry. The traffic-class field is not the transport label; the bottom-of-stack bit differentiates inner and outer label entries.

B.

That evidence could be normal while the reported defect persists. It is aimed at: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. Instead inspect: Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.

C.

The check diagnoses a different layer of service. Its source issue 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. The relevant initial check is: Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.

D.

This check may help with another root cause, 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 test the first failed condition; start with: Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.

Question 611

The provider operations team at ValleyCross Fiber reports: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Which implementation decision best corrects the cause?

  1. Verify the inbound label binding and correct the transit MPLS swap operation using the downstream-advertised label for the FEC.
  2. Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.
  3. Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
  4. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

Correct answer: D

Explanation of each choice

A.

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: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action. The distinction is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

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: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

C.

This action may apply to a different problem, for example: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. It does not repair the stated failure boundary. The case-specific reason is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

D.

Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action. The case-specific reason is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC. A direct acceptance test is: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

Question 612

During a post-change check at ValleyCross Fiber, the original condition was: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. What evidence would validate the corrected behavior?

  1. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  2. The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.
  3. Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.
  4. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

Correct answer: B

Explanation of each choice

A.

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 relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

B.

The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement. A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

C.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

D.

The observation confirms a different component's behavior. Its source context is: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. In this case the success criterion is: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

Question 613

At ValleyCross Fiber, an engineer is asked to explain this case: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Which underlying routing or switching principle accounts for the appropriate solution?

  1. A transit MPLS router normally swaps an incoming transport label with the outgoing label selected for the same forwarding equivalence class.
  2. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.
  3. Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.
  4. Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.

Correct answer: C

Explanation of each choice

A.

This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.

B.

The statement can be true when 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. But it does not explain the reported failure. Here: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

C.

Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations. The key distinction is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC. Accordingly the remedy is: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

D.

This explains a separate protocol behavior: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. In the current facts, the controlling mechanism is: Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.

Question 614

A risk assessment at ValleyCross Fiber identifies: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Which practical consequence is most specifically tied to this failure?

  1. Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.
  2. Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.
  3. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.
  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.

The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

B.

The concern could occur elsewhere when A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. For the stated scenario, the immediate risk is: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

C.

Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent. The direct mitigation is: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

D.

It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

Question 615

The on-call engineer at ValleyCross Fiber receives this fault report: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. What initial check best isolates the actual failing protocol stage?

  1. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.
  2. Inspect downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.
  3. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.
  4. Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

Correct answer: D

Explanation of each choice

A.

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.

B.

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 LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

C.

That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect LDP/label database entries alongside `show route table mpls.0` or supported MPLS forwarding entries and next-hop resolution.

D.

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.

Question 616

A production change request at Oakbend Education includes this finding: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. What should the engineer change to address it?

  1. Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
  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. Validate RSVP-TE signaling, path constraints and resource availability along the intended explicit LSP, correcting the rejecting hop or constraint.
  4. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

Correct answer: D

Explanation of each choice

A.

This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

B.

The other action is relevant when A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. The current case instead requires: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action. The distinction is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

C.

That would address a separate configuration fault: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. This stem identifies a different cause, corrected by: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

D.

Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action. The case-specific reason is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC. A direct acceptance test is: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

Question 617

After Oakbend Education applies its proposed fix to this problem — An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. — which observation best proves the specific failure has been resolved?

  1. Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.
  2. The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.
  3. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
  4. Packet capture decodes the label stack and fields correctly, allowing forwarding and CoS behavior to be checked against design.

Correct answer: B

Explanation of each choice

A.

This would be valid for another situation: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. It does not establish that the failing boundary in this scenario works; verify: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

B.

The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement. A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

C.

That check proves something else, such as: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. It could pass while the stated problem remains. The targeted evidence here is: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

D.

This would be valid for another situation: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. It does not establish that the failing boundary in this scenario works; verify: The relevant FEC has a usable selected incoming/outgoing label operation in forwarding state, not just a received label advertisement.

Question 618

An architecture review at Oakbend Education examines the following symptom: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. What Junos or protocol mechanism is most directly responsible?

  1. Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.
  2. Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.
  3. An implicit-null label advertisement requests penultimate-hop popping; the special label is control-plane instruction, not normally a transmitted label value.
  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: A

Explanation of each choice

A.

Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations. The key distinction is: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC. Accordingly the remedy is: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

B.

This explains a separate protocol behavior: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. In the current facts, the controlling mechanism is: Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.

C.

The statement can be true when 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. But it does not explain the reported failure. Here: A learned binding is control-plane information; it does not automatically prove installed label switching for the affected FEC.

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: Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.

Question 619

The team at Oakbend Education defers a fix for this condition: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. What failure is most likely if no targeted control is applied?

  1. A decoding error can hide wrong label forwarding, incorrect QoS marking or TTL expiry on a transit hop.
  2. Misunderstanding implicit null can lead to incorrect troubleshooting assumptions or malformed label handling at an MPLS edge.
  3. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.
  4. A control-plane route can be visible while failing to install a labeled forwarding path over the desired MPLS core.

Correct answer: C

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: 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. The described fault instead exposes: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

B.

It is a risk in another topology or protocol state: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. Here the most direct failure path is: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

C.

Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent. The direct mitigation is: Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

D.

That consequence is more closely associated with another deficiency, such as: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. The described fault instead exposes: Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.

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.

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