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 68

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.

Question 671

At Cloverbank Mobile, a service provider router shows this failure: 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. 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. Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.
  4. Correct the supported segment list and SID-to-forwarding resolution so the SR-MPLS ingress imposes the intended labels in the correct stack order.

Correct answer: A

Explanation of each choice

A.

Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry. The case-specific reason is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP. A direct acceptance test is: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

B.

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: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

C.

This action may apply to a different problem, for example: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. It does not repair the stated failure boundary. The case-specific reason is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

D.

The other action is relevant when A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. The current case instead requires: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry. The distinction is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

Question 672

A change auditor at Cloverbank Mobile must validate remediation of this finding: 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. 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. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  3. The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.
  4. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.

Correct answer: C

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context 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. In this case the success criterion is: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

B.

That check proves something else, such as: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. It could pass while the stated problem remains. The targeted evidence here is: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

C.

The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC. Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

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 first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

Question 673

The operations training team at Cloverbank Mobile discusses this issue: 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. Which technical explanation matches the intended correction?

  1. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.
  2. Junos uses separate routing tables for IP reachability and MPLS transport or label forwarding; the relevant RIB depends on route resolution context.
  3. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  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: C

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: MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.

B.

The statement can be true when The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. But it does not explain the reported failure. Here: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

C.

MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification. The key distinction is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP. Accordingly the remedy is: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

D.

This explains a separate protocol behavior: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. In the current facts, the controlling mechanism is: MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.

Question 674

At Cloverbank Mobile, a service acceptance review considers the unresolved issue: 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. 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. A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.
  3. Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.
  4. Misunderstanding implicit null can lead to incorrect troubleshooting assumptions or malformed label handling at an MPLS edge.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. Here the most direct failure path is: A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

B.

A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route. The direct mitigation is: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

C.

That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

D.

It is a risk in another topology or protocol state: 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. Here the most direct failure path is: A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

Question 675

Before changing configuration at Cloverbank Mobile, an engineer investigates: 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. Which first diagnostic most directly tests the suspected cause?

  1. Inspect SR-MPLS SID advertisements, label stack at ingress and forwarding resolution for each segment before changing BGP attributes.
  2. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.
  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. Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

Correct answer: D

Explanation of each choice

A.

The check diagnoses a different layer of service. Its source issue is: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. The relevant initial check is: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

B.

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: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

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: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

D.

Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported. Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

Question 676

During a Junos network change at Redleaf Airports, the engineer observes: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. 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. 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. Check the downstream label advertisement and configure supported penultimate-hop popping behavior to remove the intended transport label before egress when appropriate.

Correct answer: A

Explanation of each choice

A.

Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry. The case-specific reason is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP. A direct acceptance test is: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target 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: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry. The distinction is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

C.

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: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

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: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

Question 677

The Junos team at Redleaf Airports needs a success criterion for this defect: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. Which observed result most precisely confirms the intended repair?

  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 first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.
  3. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
  4. The remote next hop resolves over the intended active LSP where applicable and the forwarding entry has the correct label-switched path.

Correct answer: B

Explanation of each choice

A.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

B.

The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC. Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

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 first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

D.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.

Question 678

While analyzing a service failure at Redleaf Airports, the following is observed: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. SR-MPLS encodes intended segments as MPLS labels interpreted by the domain, rather than depending on RSVP-TE signaling for every hop.
  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. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  4. LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.

Correct answer: C

Explanation of each choice

A.

That principle belongs to a different service stage: A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. The directly relevant mechanism is: MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.

B.

This explains a separate protocol behavior: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. In the current facts, the controlling mechanism is: MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.

C.

MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification. The key distinction is: Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP. Accordingly the remedy is: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

D.

That principle belongs to a different service stage: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. The directly relevant mechanism is: MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.

Question 679

The following provider defect remains uncorrected at Redleaf Airports: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. What is the most direct service or security risk of leaving it unresolved?

  1. Invalid transit label swapping sends packets to a neighbor with no matching label entry, causing packet discard despite healthy IP connectivity.
  2. A decoding error can hide wrong label forwarding, incorrect QoS marking or TTL expiry on a transit hop.
  3. An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
  4. A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

Correct answer: D

Explanation of each choice

A.

It is a risk in another topology or protocol state: 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. Here the most direct failure path is: A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

B.

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 fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

C.

The concern could occur elsewhere when An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. For the stated scenario, the immediate risk is: A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.

D.

A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route. The direct mitigation is: Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.

Question 680

A support escalation at Redleaf Airports describes: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. Where should the Junos operator look first for decisive evidence?

  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. Check each LSP path's signaling state and hop constraints independently, then test traffic during a controlled primary path failure.
  3. Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.
  4. Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.

Correct answer: C

Explanation of each choice

A.

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: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

B.

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: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

C.

Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported. Successful plain-IP ping does not validate the label-switched forwarding plane or the service's active LSP.

D.

That evidence could be normal while the reported defect persists. It is aimed at: An explicitly constrained MPLS LSP should avoid one core link, but its RSVP-TE signaling never completes because a transit hop lacks appropriate resources. Instead inspect: Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

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