JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
Before changing configuration at Canal City University, an engineer investigates: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. Which first diagnostic most directly tests the suspected cause?
The check diagnoses a different layer of service. Its source issue is: A provider sets a preferred RSVP LSP path but it remains down after a network change despite working LDP labels elsewhere. The relevant initial check is: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop. IP reachability alone is not identical to an eligible transport LSP; route recursion and MPLS forwarding state must be examined together.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
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: Inspect inet.0, applicable inet.3 LSP routes, and mpls.0 label forwarding for the precise remote next hop.
At Bridgeway Cloud, a service provider router shows this failure: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. What is the best targeted configuration or operations action?
Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange. The case-specific reason is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling. A direct acceptance test is: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
The other action is relevant when The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. The current case instead requires: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange. The distinction is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
That would address a separate configuration fault: An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. This stem identifies a different cause, corrected by: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
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: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
A change auditor at Bridgeway Cloud must validate remediation of this finding: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. Which test outcome is the strongest acceptance evidence?
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: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
The observation confirms a different component's behavior. Its source context is: A provider observes end-to-end label-switched traffic loss but checks only an IP traceroute and concludes MPLS is healthy. In this case the success criterion is: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
This would be valid for another situation: An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. It does not establish that the failing boundary in this scenario works; verify: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
The operations training team at Bridgeway Cloud discusses this issue: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. Which technical explanation matches the intended correction?
LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels. The key distinction is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling. Accordingly the remedy is: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
This explains a separate protocol behavior: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. In the current facts, the controlling mechanism is: LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
The statement can be true when An ingress LER receives unlabeled customer IPv4 packets but the intended LSP is active and no MPLS label appears on the core-facing wire. But it does not explain the reported failure. Here: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
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: LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
At Bridgeway Cloud, a service acceptance review considers the unresolved issue: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. Which operational exposure follows most directly?
That consequence is more closely associated with another deficiency, such as: An ingress BGP route has an intended LSP next hop but recursive transport reachability is absent in the table used for LSP resolution. The described fault instead exposes: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
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: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist. The direct mitigation is: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
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: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
Before changing configuration at Bridgeway Cloud, an engineer investigates: Two transit routers have IGP reachability but cannot establish LDP neighbor state, so no labels are distributed for the intended FEC. Which first diagnostic most directly tests the suspected cause?
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: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
This check may help with another root cause, for example: 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 test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
That evidence could be normal while the reported defect persists. It is aimed at: A service edge has both primary and secondary LSP definitions yet the backup remains unusable due to stale explicit route constraints. Instead inspect: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
During a Junos network change at Crestpoint Research, the engineer observes: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Which remediation most directly fixes the described problem?
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
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: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
The other action is relevant when An engineer assumes that seeing a label in a protocol database means it must already be programmed into the forwarding plane. The current case instead requires: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange. The distinction is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange. The case-specific reason is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling. A direct acceptance test is: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
The Junos team at Crestpoint Research needs a success criterion for this defect: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Which observed result most precisely confirms the intended repair?
That check proves something else, such as: The provider can ping a remote loopback by ordinary IP, yet LSP-based forwarding never becomes eligible for that BGP next hop. It could pass while the stated problem remains. The targeted evidence here is: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
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: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
That check proves something else, 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. It could pass while the stated problem remains. The targeted evidence here is: LDP peers establish and the expected FEC-to-label bindings are exchanged and installed for the transport path.
While analyzing a service failure at Crestpoint Research, the following is observed: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true when A new SR-MPLS ingress advertises a segment list but its label stack does not reflect the intended waypoint SID. But it does not explain the reported failure. Here: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
That principle belongs to a different service stage: A provider's MPLS QoS troubleshooting treats the three-bit traffic class as though it were the forwarding label value. The directly relevant mechanism is: LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels.
LDP uses discovery Hellos and a session for label distribution; IGP connectivity does not itself exchange MPLS labels. The key distinction is: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling. Accordingly the remedy is: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
The statement can be true when 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. But it does not explain the reported failure. Here: LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
The following provider defect remains uncorrected at Crestpoint Research: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. What is the most direct service or security risk of leaving it unresolved?
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: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
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: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
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: An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist.
An IGP path can remain active while MPLS services blackhole because no usable downstream label bindings exist. The direct mitigation is: Restore LDP discovery and TCP session reachability plus compatible authentication or transport addressing, then validate FEC label exchange.
A support escalation at Crestpoint Research describes: An LDP router discovers its neighbor but no session forms after a control-plane filter was added to the core-facing interface. Where should the Junos operator look first for decisive evidence?
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: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
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: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC. LDP session establishment is distinct from OSPF/IS-IS adjacency and from RSVP-TE reservation signaling.
This check may help with another root cause, for example: A provider's Segment Routing over MPLS policy should steer traffic via an intermediate segment but packets use only ordinary shortest-path transport. It does not test the first failed condition; start with: Check LDP neighbor/session states, discovery Hellos, TCP session reachability and advertised bindings for the affected FEC.
Please check your mailbox for a message from support@examlabs.com and follow the directions.