Juniper JN0-364 Questions & Answers

A controlled Routing Engine switchover retains forwarding and the planned bridge or routing state without unexpected protocol resets. That establishes GRES preserves forwarding not protocols rather than a repaired LDP neighbor discovery path. The reported failure still requires this evidence: the intended interface discovers the peer and the LDP neighbor appears with an operational session.

The LDP session establishes over reachable transport addresses and peers exchange expected label bindings. That establishes LDP transport address reachability rather than a repaired LDP neighbor discovery path. The reported failure still requires this evidence: the intended interface discovers the peer and the LDP neighbor appears with an operational session.

The intended LSP is admitted on a path satisfying its bandwidth constraints without oversubscribing reserved resources. That establishes RSVP path bandwidth admission rather than a repaired LDP neighbor discovery path. The reported failure still requires this evidence: the intended interface discovers the peer and the LDP neighbor appears with an operational session.

This measurement tests GRE confidentiality limitation; it cannot distinguish success from failure for the observed GRE recursive route avoidance condition. A tunnel's transport destination must not depend on routing through that same tunnel; recursion defeats the encapsulation path.

The check is meaningful for GRE tunnel path MTU, but it does not prove that GRE recursive route avoidance was repaired. A tunnel's transport destination must not depend on routing through that same tunnel; recursion defeats the encapsulation path.

The check is meaningful for provider bridging MTU overhead, but it does not prove that GRE recursive route avoidance was repaired. A tunnel's transport destination must not depend on routing through that same tunnel; recursion defeats the encapsulation path.

Monitor exported AS paths and actual traffic after inbound-traffic-engineering changes. That ongoing check is for AS-path prepend inbound influence; it would not reliably detect recurrence of BGP local preference. LOCAL_PREF is an intradomain BGP path attribute that normally influences preferred outbound exit for routes inside the AS.

This is a useful guard against BGP next-hop reachability, but it is not scoped to the observed BGP local preference failure. An appropriate test would show that internal BGP best paths prefer the approved egress due to the intended local-preference values.

The control protects IS-IS wide metrics. It does not establish the ongoing BGP local preference behavior required in this network. LOCAL_PREF is an intradomain BGP path attribute that normally influences preferred outbound exit for routes inside the AS.

LACP aggregates only compatible negotiated member links; physical Up state alone does not prove active bundle participation. That describes LACP aggregation consistency, whereas the observed symptoms are caused by VLAN access trunk distinction; it does not predict the reported behavior.

Although MAC address learning and moves needs this consideration, the failure at issue has a different cause. Access ports and trunk ports have different VLAN tagging and membership behaviors; link-up state does not make the modes equivalent.

Virtual-switch routing instances provide separate bridge contexts; similar VLAN identifiers alone do not imply shared L2 forwarding. That describes virtual-switch instance isolation, whereas the observed symptoms are caused by VLAN access trunk distinction; it does not predict the reported behavior.

This measurement tests OSPF designated router election; it cannot distinguish success from failure for the observed RSVP PATH and RESV signaling condition. RSVP-TE establishes LSP state through forward PATH and reverse RESV processing; one-way PATH reception is insufficient.

The intended LSP is admitted on a path satisfying its bandwidth constraints without oversubscribing reserved resources. That establishes RSVP path bandwidth admission rather than a repaired RSVP PATH and RESV signaling path. The reported failure still requires this evidence: the LSP shows a completed RSVP reservation and an operational signaled path through intended hops.

The prefix SID is advertised and all ingress routers compute consistent transport label behavior for the node destination. It would validate a separate segment routing prefix SID operation, not the change needed here. Confirm instead that the LSP shows a completed RSVP reservation and an operational signaled path through intended hops.

Although GRE recursive route avoidance needs this consideration, the failure at issue has a different cause. The MPLS S bit identifies the final label in a stack; it does not describe label priority or path preference.

SR-MPLS prefix SIDs and the segment routing global block provide IGP-signaled reachability without relying on LDP for each FEC. Those conditions do not account for the specific MPLS label stack bottom bit problem reported by Moorland Carriers.

Although LDP transport address reachability needs this consideration, the failure at issue has a different cause. The MPLS S bit identifies the final label in a stack; it does not describe label priority or path preference.

Although RSTP loop protection needs this consideration, the failure at issue has a different cause. Root protection blocks acceptance of an unexpected superior root across designated boundary ports; it is not the same as BPDU edge protection.

This principle matters when troubleshooting VSTP per-VLAN root choice, but using it here mistakes a different failure mode for RSTP root protection. The relevant distinction is: root protection blocks acceptance of an unexpected superior root across designated boundary ports; it is not the same as BPDU edge protection.

Martian-address handling protects routing tables from addresses that should not be accepted as normal routable destinations. Those conditions do not account for the specific RSTP root protection problem reported by Riverbend Exchange.

This is a useful guard against MPLS label forwarding table mismatch, but it is not scoped to the observed LDP neighbor discovery failure. An appropriate test would show that the intended interface discovers the peer and the LDP neighbor appears with an operational session.

Alert when the required static route becomes hidden or its next hop stops resolving, and validate reachability before committing changes. The monitored boundary differs from LDP neighbor discovery, so the original weakness might reappear unnoticed. LDP uses discovery messages on enabled interfaces before exchanging label mappings; IGP reachability alone does not start LDP.

Confirm implicit-null advertisements and expected transport-label popping during LSP validation. The monitored boundary differs from LDP neighbor discovery, so the original weakness might reappear unnoticed. LDP uses discovery messages on enabled interfaces before exchanging label mappings; IGP reachability alone does not start LDP.

This is a useful guard against IS-IS NET and system ID, but it is not scoped to the observed IS-IS L1 and L2 reachability failure. An appropriate test would show that the Level 1 router has valid remote-area reachability through the intended L1–L2 boundary without learning the entire L2 topology.

Audit which ports are true edges and test protective action when a simulated switch sends a BPDU. That ongoing check is for RSTP edge BPDU protection; it would not reliably detect recurrence of IS-IS L1 and L2 reachability. IS-IS uses Level 1 within an area and Level 2 between areas; an L1 router needs an appropriate inter-area exit or route leak.

Capture DIS election and pseudonode observations during shared LAN commissioning and role changes. That ongoing check is for IS-IS LAN designated intermediate system; it would not reliably detect recurrence of IS-IS L1 and L2 reachability. IS-IS uses Level 1 within an area and Level 2 between areas; an L1 router needs an appropriate inter-area exit or route leak.

This measurement tests multiprotocol BGP IPv6 AFI; it cannot distinguish success from failure for the observed IPv6 over IPv4 tunnel underlay condition. An IPv6-over-IPv4 tunnel depends on the IPv4 underlay that transports encapsulated packets; overlay route presence cannot replace underlay connectivity.

The intended IPv6 destination has an active route with a resolved next hop and working egress interface. It would validate a separate IPv6 static next-hop scope operation, not the change needed here. Confirm instead that both IPv4 endpoint paths are reachable and IPv6 packets traverse the encapsulated link end to end.

The check is meaningful for generated route qualified next hop, but it does not prove that IPv6 over IPv4 tunnel underlay was repaired. An IPv6-over-IPv4 tunnel depends on the IPv4 underlay that transports encapsulated packets; overlay route presence cannot replace underlay connectivity.

This measurement tests IS-IS LSP database synchronization; it cannot distinguish success from failure for the observed VLAN access trunk distinction condition. Access ports and trunk ports have different VLAN tagging and membership behaviors; link-up state does not make the modes equivalent.

The check is meaningful for integrated routing and bridging, but it does not prove that VLAN access trunk distinction was repaired. Access ports and trunk ports have different VLAN tagging and membership behaviors; link-up state does not make the modes equivalent.

The check is meaningful for MAC address learning and moves, but it does not prove that VLAN access trunk distinction was repaired. Access ports and trunk ports have different VLAN tagging and membership behaviors; link-up state does not make the modes equivalent.