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 58

Question 570

The on-call engineer at Seawood Media receives this fault report: A blocked redundant path becomes vulnerable to unidirectional failure when expected BPDUs stop, allowing accidental forwarding of both halves of a loop. What initial check best isolates the actual failing protocol stage?

  1. Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.
  2. Check the actual neighbor device, BPDU observations and interface spanning-tree edge/role state before changing port behavior.
  3. Compare MST region name, revision, VLAN mappings and instance-specific BPDU/root data across the connected switches.
  4. Compare root bridge ID, local bridge ID, port path costs and received BPDUs across the affected VLAN/instance.

Correct answer: A

Explanation of each choice

A.

Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard. Root protection and loop protection address different failure modes, so swapping one for the other without evidence is not sufficient.

B.

This check may help with another root cause, for example: A host access interface takes too long to forward after a link flap because it is treated as a non-edge spanning-tree segment. It does not test the first failed condition; start with: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.

C.

That evidence could be normal while the reported defect persists. It is aimed at: A provider partitions VLANs across MST instances but one participating switch uses another configuration digest, producing unexpected root decisions. Instead inspect: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.

D.

The check diagnoses a different layer of service. Its source issue is: A newly connected low-end switch becomes the spanning-tree root after a topology change, routing Ethernet traffic along an inefficient path. The relevant initial check is: Inspect the specific inbound BPDU superiority/absence pattern, role and designated protection state before selecting the guard.

Question 571

The provider operations team at Copperwick Markets reports: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. Which implementation decision best corrects the cause?

  1. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.
  2. Use LSP/label-aware operational checks and hop-by-hop incoming/outgoing label verification to find the first divergent MPLS forwarding entry.
  3. Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.
  4. Verify the inbound label binding and correct the transit MPLS swap operation using the downstream-advertised label for the FEC.

Correct answer: C

Explanation of each choice

A.

This action may apply to a different problem, for example: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. It does not repair the stated failure boundary. The case-specific reason is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

B.

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 forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission. The distinction is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

C.

Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission. The case-specific reason is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it. A direct acceptance test is: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

D.

This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

Question 572

During a post-change check at Copperwick Markets, the original condition was: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. What evidence would validate the corrected behavior?

  1. The RSVP LSP signals successfully along the approved route and appears Up with expected path, reservations and label-switched forwarding.
  2. Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.
  3. A penultimate transit hop performs the expected pop and the egress sees the remaining service label or IP packet matching the LSP design.
  4. The 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.

This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

B.

Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP. Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

C.

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: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

D.

This would be valid for another situation: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. It does not establish that the failing boundary in this scenario works; verify: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

Question 573

At Copperwick Markets, an engineer is asked to explain this case: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. Which underlying routing or switching principle accounts for the appropriate solution?

  1. MPLS forwarding follows label operations that can diverge from ordinary IP next-hop lookup, requiring LSP-specific verification.
  2. A transit MPLS router normally swaps an incoming transport label with the outgoing label selected for the same forwarding equivalence class.
  3. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.
  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: 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: At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

B.

This explains a separate protocol behavior: A provider replaces an MPLS transit router and packets fail at the next hop because the local forwarding table has an invalid outgoing label operation. In the current facts, the controlling mechanism is: At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

C.

At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path. The key distinction is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it. Accordingly the remedy is: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.

D.

That principle belongs to a different service stage: 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 directly relevant mechanism is: At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

Question 574

A risk assessment at Copperwick Markets identifies: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. Which practical consequence is most specifically tied to this failure?

  1. Traffic can bypass intended waypoints or drop at a transit LSR if a SID or label-stack entry is unresolved.
  2. Misunderstanding implicit null can lead to incorrect troubleshooting assumptions or malformed label handling at an MPLS edge.
  3. An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
  4. Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

Correct answer: D

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. The described fault instead exposes: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

B.

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: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

C.

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: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

D.

Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops. The direct mitigation is: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.

Question 575

The on-call engineer at Copperwick Markets receives this fault report: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. What initial check best isolates the actual failing protocol stage?

  1. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.
  2. Inspect downstream implicit-null binding and the actual label stack on the penultimate-to-egress interface.
  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: C

Explanation of each choice

A.

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 the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

B.

The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

C.

Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture. Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

D.

That evidence could be normal while the reported defect persists. It is aimed at: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. Instead inspect: Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

Question 576

A production change request at Ironcrest Payments includes this finding: 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. What should the engineer change to address it?

  1. Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.
  2. Reconcile the control-plane label binding with the selected route/LSP and verify the label has a valid installed forwarding action.
  3. Verify the inbound label binding and correct the transit MPLS swap operation using the downstream-advertised label for the FEC.
  4. Inspect and interpret the MPLS label header fields correctly, including label value, traffic class, bottom-of-stack indicator and TTL.

Correct answer: A

Explanation of each choice

A.

Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission. The case-specific reason is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it. A direct acceptance test is: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

B.

This action may apply to a different problem, for example: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. It does not repair the stated failure boundary. The case-specific reason is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

C.

The other action is relevant 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. The current case instead requires: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission. The distinction is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

D.

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: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.

Question 577

After Ironcrest Payments applies its proposed fix to this problem — 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. — which observation best proves the specific failure has been resolved?

  1. The first failing label operation is identified and corrected, after which LSP state and labeled traffic delivery recover for the target FEC.
  2. Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.
  3. LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
  4. Packet captures and router forwarding state show the expected segment identifiers in the imposed stack and traffic traverses the planned waypoint.

Correct answer: B

Explanation of each choice

A.

That check proves something else, such as: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. It could pass while the stated problem remains. The targeted evidence here is: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

B.

Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP. Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

C.

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: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

D.

That check proves something else, such as: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. It could pass while the stated problem remains. The targeted evidence here is: Packet capture on the first MPLS hop shows the expected pushed label stack and the ingress forwarding route references the active transport LSP.

Question 578

An architecture review at Ironcrest Payments examines the following symptom: 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. What Junos or protocol mechanism is most directly responsible?

  1. An MPLS shim header contains a 20-bit label, 3-bit traffic-class field, 1-bit bottom-of-stack indicator and 8-bit TTL.
  2. Label protocol databases record advertised bindings, whereas the forwarding plane requires selected and programmed label operations.
  3. LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
  4. At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

Correct answer: D

Explanation of each choice

A.

The statement can be true when 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. But it does not explain the reported failure. Here: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

B.

That principle belongs to a different service stage: 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 directly relevant mechanism is: At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

C.

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: At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path.

D.

At an MPLS ingress, label imposition pushes the forwarding label onto an IP packet as it enters a label-switched path. The key distinction is: Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it. Accordingly the remedy is: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.

Question 579

The team at Ironcrest Payments defers a fix for this condition: 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. 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. An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
  3. A fault in label imposition, swap or pop can persist even when the same destination is reachable through an IP route.
  4. Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

Correct answer: D

Explanation of each choice

A.

The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

B.

That consequence is more closely associated with another deficiency, such as: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. The described fault instead exposes: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

C.

It is a risk in another topology or protocol state: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. Here the most direct failure path is: Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops.

D.

Unlabeled traffic can bypass the intended MPLS forwarding plane or fail on core links that rely on label-based next hops. The direct mitigation is: Repair the forwarding resolution from the ingress route into the intended LSP so an MPLS transport label is pushed before core transmission.

Question 580

During provider troubleshooting at Ironcrest Payments, this symptom is observed: 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. Which targeted inspection should precede remediation?

  1. Capture MPLS frames and compare the full 32-bit label entry and stack order against the receiving router's forwarding entry.
  2. Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.
  3. Inspect MPLS forwarding state for the incoming label, the chosen outgoing label and the downstream peer's FEC binding.
  4. Compare LSP operational state, route recursion and MPLS forwarding entries hop-by-hop, including label-aware probes where supported.

Correct answer: B

Explanation of each choice

A.

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 the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

B.

Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture. Ingress push differs from a transit swap or egress pop, and an established LSP is insufficient if the IP route does not resolve over it.

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: Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

D.

This check may help with another root cause, 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 test the first failed condition; start with: Inspect the ingress route next hop, inet.3 LSP resolution when applicable and the outgoing label stack with a core-facing packet capture.

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