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 67

Question 660

During provider troubleshooting at Orion Transit Exchange, this symptom is observed: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. Which targeted inspection should precede remediation?

  1. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.
  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. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.

Correct answer: A

Explanation of each choice

A.

Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure. A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.

B.

This check may help with another root cause, for example: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. It does not test the first failed condition; start with: Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.

C.

That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.

D.

The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.

Question 661

A production change request at Redleaf Airports includes this finding: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. 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. Inspect and interpret the MPLS label header fields correctly, including label value, traffic class, bottom-of-stack indicator and TTL.
  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: B

Explanation of each choice

A.

This action may apply to a different problem, for example: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. It does not repair the stated failure boundary. The case-specific reason is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

B.

Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order. The case-specific reason is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination. A direct acceptance test is: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

C.

That would address a separate configuration fault: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. This stem identifies a different cause, corrected by: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

D.

This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

Question 662

After Redleaf Airports applies its proposed fix to this problem — A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. — 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. Packet capture decodes the label stack and fields correctly, allowing forwarding and CoS behavior to be checked against design.
  4. Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

Correct answer: A

Explanation of each choice

A.

Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint. A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

B.

The observation confirms a different component's behavior. Its source context is: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. In this case the success criterion is: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

C.

That check proves something else, such as: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. It could pass while the stated problem remains. The targeted evidence here is: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

D.

This would be valid for another situation: 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 does not establish that the failing boundary in this scenario works; verify: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

Question 663

An architecture review at Redleaf Airports examines the following symptom: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. What Junos or protocol mechanism is most directly responsible?

  1. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  2. LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
  3. SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.
  4. RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.

Correct answer: C

Explanation of each choice

A.

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: SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

B.

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: SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

C.

SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop. The key distinction is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination. Accordingly the remedy is: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

D.

That principle belongs to a different service stage: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. The directly relevant mechanism is: SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

Question 664

The team at Redleaf Airports defers a fix for this condition: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. What failure is most likely if no targeted control is applied?

  1. Invalid transit label swapping sends packets to a neighbor with no matching label entry, causing packet discard despite healthy IP connectivity.
  2. Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.
  3. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.
  4. Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

Correct answer: D

Explanation of each choice

A.

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: Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

B.

It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

C.

The concern could occur elsewhere when An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. For the stated scenario, the immediate risk is: Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

D.

Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved. The direct mitigation is: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

Question 665

During provider troubleshooting at Redleaf Airports, this symptom is observed: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. Which targeted inspection should precede remediation?

  1. Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.
  2. Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.
  3. Inspect downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.
  4. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.

Correct answer: A

Explanation of each choice

A.

Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes. A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

B.

The check diagnoses a different layer of service. Its source issue is: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. The relevant initial check is: Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

C.

This check may help with another root cause, for example: A transport egress receives an extra MPLS label that an upstream design expected the penultimate hop to remove. It does not test the first failed condition; start with: Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

D.

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 SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

Question 666

At Silverpeak Data Networks, a service provider router shows this failure: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. What is the best targeted configuration or operations action?

  1. Inspect and interpret the MPLS label header fields correctly, including label value, traffic class, bottom-of-stack indicator and TTL.
  2. Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.
  3. Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.
  4. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.

Correct answer: C

Explanation of each choice

A.

That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

B.

This action may apply to a different problem, for example: 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. It does not repair the stated failure boundary. The case-specific reason is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

C.

Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order. The case-specific reason is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination. A direct acceptance test is: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

D.

That would address a separate configuration fault: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. This stem identifies a different cause, corrected by: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

Question 667

A change auditor at Silverpeak Data Networks must validate remediation of this finding: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. Which test outcome is the strongest acceptance evidence?

  1. Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.
  2. The transit forwarding entry maps the expected incoming label to the downstream outgoing label and packets progress to the next LSR.
  3. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
  4. Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

Correct answer: D

Explanation of each choice

A.

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: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

B.

This would be valid for another situation: 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. It does not establish that the failing boundary in this scenario works; verify: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

C.

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: Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

D.

Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint. A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

Question 668

The operations training team at Silverpeak Data Networks discusses this issue: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. Which technical explanation matches the intended correction?

  1. RSVP-TE can signal constraint-aware LSPs with per-path reservation and label state, unlike ordinary LDP FEC signaling.
  2. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.
  3. An MPLS shim header contains a 20-bit label, 3-bit traffic-class field, 1-bit bottom-of-stack indicator and 8-bit TTL.
  4. SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

Correct answer: D

Explanation of each choice

A.

The statement can be true when A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. But it does not explain the reported failure. Here: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

B.

That principle belongs to a different service stage: 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 directly relevant mechanism is: SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

C.

This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.

D.

SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop. The key distinction is: A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination. Accordingly the remedy is: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

Question 669

At Silverpeak Data Networks, a service acceptance review considers the unresolved issue: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. Which operational exposure follows most directly?

  1. Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.
  2. Traffic can fail even when the protocol adjacency and remote label advertisement appear healthy if the forwarding entry is absent.
  3. A decoding error can hide wrong label forwarding, incorrect QoS marking or TTL expiry on a transit hop.
  4. A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

Correct answer: A

Explanation of each choice

A.

Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved. The direct mitigation is: Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

B.

That consequence is more closely associated with another deficiency, such as: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. The described fault instead exposes: Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

C.

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 bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

D.

The concern could occur elsewhere 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. For the stated scenario, the immediate risk is: Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.

Question 670

Before changing configuration at Silverpeak Data Networks, an engineer investigates: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. Which first diagnostic most directly tests the suspected cause?

  1. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.
  2. Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
  3. Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.
  4. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.

Correct answer: C

Explanation of each choice

A.

This check may help with another root cause, for example: 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 test the first failed condition; start with: Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

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: Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

C.

Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes. A segment list expresses a source-specified transit path through MPLS labels; it is not the same as a single LDP binding for a final destination.

D.

This check may help with another root cause, for example: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. It does not test the first failed condition; start with: Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.

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