JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
The on-call engineer at Bridgeway Cloud receives this fault report: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. What initial check best isolates the actual failing protocol stage?
Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop. The failure is RSVP path/reservation signaling, not a generic IPv6 tunnel or OSPF route redistribution problem.
The check diagnoses a different layer of service. Its source issue 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. The relevant initial check is: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
This check may help with another root cause, 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 test the first failed condition; start with: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
That evidence could be normal while the reported defect persists. It is aimed at: An LDP peer advertises a label binding for a FEC but traffic still drops because the local MPLS forwarding table lacks a usable entry. Instead inspect: Inspect RSVP session/path errors, ERO or hop constraints, resource availability and LSP operational detail on the failing hop.
The provider operations team at Seawood Media reports: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. Which implementation decision best corrects the cause?
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: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
This action may apply to a different problem, for example: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. It does not repair the stated failure boundary. The case-specific reason is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage. The case-specific reason is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover. A direct acceptance test is: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
That would address a separate configuration fault: An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. This stem identifies a different cause, corrected by: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
During a post-change check at Seawood Media, the original condition was: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. What evidence would validate the corrected behavior?
The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable. A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
This would be valid for another situation: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. It does not establish that the failing boundary in this scenario works; verify: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
The observation confirms a different component's behavior. Its source context is: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. In this case the success criterion is: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
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 secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
At Seawood Media, an engineer is asked to explain this case: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. Which underlying routing or switching principle accounts for the appropriate solution?
Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state. The key distinction is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover. Accordingly the remedy is: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
That principle belongs to a different service stage: 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 directly relevant mechanism is: Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state.
This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state.
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: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
A risk assessment at Seawood Media identifies: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure. The direct mitigation is: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
It is a risk in another topology or protocol state: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. Here the most direct failure path is: A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
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 nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
The on-call engineer at Seawood Media receives this fault report: A provider expects a preplanned backup RSVP path to protect traffic but a primary transport failure causes prolonged loss. What initial check best isolates the actual failing protocol stage?
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: 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: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. 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: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. 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.
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.
A production change request at Orion Transit Exchange includes this finding: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. What should the engineer change to address it?
The other action is relevant when An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. The current case instead requires: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage. The distinction is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
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 backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage. The case-specific reason is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover. A direct acceptance test is: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
After Orion Transit Exchange applies its proposed fix to this problem — A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. — which observation best proves the specific failure has been resolved?
The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable. A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
That check proves something else, such as: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. It could pass while the stated problem remains. The targeted evidence here is: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
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 secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: The secondary LSP is operationally ready and traffic transfers to the defined alternate path when the primary LSP becomes unavailable.
An architecture review at Orion Transit Exchange examines the following symptom: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. What Junos or protocol mechanism is most directly responsible?
Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state. The key distinction is: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover. Accordingly the remedy is: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
The statement can be true 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. But it does not explain the reported failure. Here: A backup path's configuration presence is not proof that RSVP can reserve or activate it during failover.
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: Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state.
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: Configured primary/secondary LSP paths support planned transport failover only when the backup can itself signal and install forwarding state.
The team at Orion Transit Exchange defers a fix for this condition: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when An MPLS service ingress forwards plain IP over a core link instead of imposing the transport label despite a valid route to the remote egress. For the stated scenario, the immediate risk is: A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
The concern could occur elsewhere when A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. For the stated scenario, the immediate risk is: A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure.
A nominal backup that cannot signal leaves traffic unprotected and creates extended outages after primary path failure. The direct mitigation is: Validate a reachable secondary RSVP-signaled LSP with approved constraints and verify the actual failover procedure under a controlled primary-path outage.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.