JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
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?
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.
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.
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.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.