Juniper JN0-364 Questions & Answers

Verify full label stack ordering and bottom-of-stack indication on the encapsulated service path. This addresses MPLS label stack bottom bit, but the reported symptoms arise from provider Q-in-Q tagging. For this case, verify instead that captured service frames show the expected outer provider tag and unchanged customer tag, with distinct customers isolated.

Set access or trunk interface mode to match the attached device and approved VLAN membership. That could help in a case involving VLAN access trunk distinction. This failure instead depends on provider Q-in-Q tagging; Q-in-Q carries an additional provider VLAN tag around customer-tagged traffic to isolate services with overlapping customer VLAN numbers.

The proposal changes virtual-switch instance isolation; that is not the failure isolated by the facts. It could leave provider Q-in-Q tagging unresolved even if its own test passed. Q-in-Q carries an additional provider VLAN tag around customer-tagged traffic to isolate services with overlapping customer VLAN numbers.

Set and test a coherent MED policy between comparable paths, acknowledging peer AS comparison behavior and upstream policies. This addresses BGP MED neighbor consideration, but the reported symptoms arise from RSTP edge BPDU protection. For this case, verify instead that an unexpected BPDU causes the intended protective state and operations receive a traceable port event.

The proposal changes VSTP per-VLAN root choice; that is not the failure isolated by the facts. It could leave RSTP edge BPDU protection unresolved even if its own test passed. Edge BPDU protection is intended for ports expected to connect to hosts, not for ordinary switch-to-switch links that exchange BPDUs. Applied here, the relevant facts are: A staff workstation port receives rogue spanning-tree control messages but remains forwarding because edge protection is missing. The question asks which focused engineering action would best correct the fault.

The proposal changes RSTP loop protection; that is not the failure isolated by the facts. It could leave RSTP edge BPDU protection unresolved even if its own test passed. Edge BPDU protection is intended for ports expected to connect to hosts, not for ordinary switch-to-switch links that exchange BPDUs.

Insert the appropriate valid adjacency SID for the required hop and verify the resolved segment list and actual forwarding path. This addresses segment routing adjacency SID, but the reported symptoms arise from LDP label binding completeness. For this case, verify instead that the forwarding table has a valid outgoing label for the selected next hop and labeled traffic reaches the intended prefix.

Enable appropriate LDP interface discovery and verify discovery hellos and eventual neighbor session state. Its normal acceptance signal would be the intended interface discovers the peer and the LDP neighbor appears with an operational session. Here the deciding check is different: the forwarding table has a valid outgoing label for the selected next hop and labeled traffic reaches the intended prefix.

Enable and inspect the relevant IS-IS IPv6 address-family reachability advertisements and verify eligible routes. Its normal acceptance signal would be IPv6 reachability TLVs are exchanged and peers install the intended IPv6 routes independently of IPv4 reachability. Here the deciding check is different: the forwarding table has a valid outgoing label for the selected next hop and labeled traffic reaches the intended prefix.

The check is meaningful for filter-based forwarding table selection, but it does not prove that IPv6 static next-hop scope was repaired. IPv6 link-local next hops are interface-scoped; a bare link-local address can be insufficient to identify the outgoing link.

The expected OSPFv3 neighbor reaches Full and IPv6 routes appear with intended next hops. It would validate a separate OSPFv3 IPv6 neighbor reachability operation, not the change needed here. Confirm instead that the intended IPv6 destination has an active route with a resolved next hop and working egress interface.

IPv6 reachability TLVs are exchanged and peers install the intended IPv6 routes independently of IPv4 reachability. It would validate a separate IS-IS IPv6 topology TLVs operation, not the change needed here. Confirm instead that the intended IPv6 destination has an active route with a resolved next hop and working egress interface.

This measurement tests BGP local preference; it cannot distinguish success from failure for the observed LDP transport address reachability condition. LDP discovery and session setup are distinct; a transport TCP connection must be reachable after hello discovery.

This measurement tests LDP neighbor discovery; it cannot distinguish success from failure for the observed LDP transport address reachability condition. LDP discovery and session setup are distinct; a transport TCP connection must be reachable after hello discovery.

The check is meaningful for penultimate hop popping, but it does not prove that LDP transport address reachability was repaired. LDP discovery and session setup are distinct; a transport TCP connection must be reachable after hello discovery.

Captured service frames show the expected outer provider tag and unchanged customer tag, with distinct customers isolated. It would validate a separate provider Q-in-Q tagging operation, not the change needed here. Confirm instead that the MAC address stabilizes on the expected interface and unicast forwarding avoids repeated flooding.

The check is meaningful for IS-IS NET and system ID, but it does not prove that MAC address learning and moves was repaired. Ethernet bridges learn destination forwarding from observed source MAC addresses; unstable topology can continually invalidate learned ports.

The correct single- and double-tagged service units receive traffic matching their configured VLAN identifiers. It would validate a separate flexible VLAN encapsulation alignment operation, not the change needed here. Confirm instead that the MAC address stabilizes on the expected interface and unicast forwarding avoids repeated flooding.

Review tunnel transport security requirements and verify encryption rather than accepting GRE setup as proof of privacy. The monitored boundary differs from GRE endpoint underlay routing, so the original weakness might reappear unnoticed. GRE encapsulates packets between outer IP endpoints; the underlay must route the outer destination before inner traffic can succeed.

Exercise VRRP failover and confirm virtual gateway reachability under device and link failure. The monitored boundary differs from GRE endpoint underlay routing, so the original weakness might reappear unnoticed. GRE encapsulates packets between outer IP endpoints; the underlay must route the outer destination before inner traffic can succeed.

The control protects GRE recursive route avoidance. It does not establish the ongoing GRE endpoint underlay routing behavior required in this network. GRE encapsulates packets between outer IP endpoints; the underlay must route the outer destination before inner traffic can succeed. Applied here, the relevant facts are: A GRE tunnel interface shows configured addresses but no traffic passes after the remote outer IP endpoint loses reachability. The question asks which ongoing control would most directly detect or prevent the same failure from recurring.

IS-IS uses TLVs inside its PDUs to encode prefix and protocol capabilities; adjacency alone is not proof of expected reachability advertisements. Those conditions do not account for the specific IS-IS LAN designated intermediate system problem reported by Brookstone Communications.

Although OSPF external route export needs this consideration, the failure at issue has a different cause. On an IS-IS broadcast LAN the DIS originates pseudonode LSPs and may be re-elected when priority changes; the process differs from OSPF DR behavior.

IS-IS peers must support a common adjacency level; active Ethernet transport does not compensate for a level mismatch. That describes IS-IS adjacency circuit level, whereas the observed symptoms are caused by IS-IS LAN designated intermediate system; it does not predict the reported behavior.

The outer GRE endpoint resolves to an underlay interface while only intended inner destinations use the tunnel. It would validate a separate GRE recursive route avoidance operation, not the change needed here. Confirm instead that an underlay capture cannot read protected payload content and transport still reaches the required tunnel endpoints.

The check is meaningful for GRE endpoint underlay routing, but it does not prove that GRE confidentiality limitation was repaired. GRE provides encapsulation and protocol carriage but does not inherently supply confidentiality or cryptographic integrity.

Adjacent devices report matching MST region configuration and VLANs map to the same intended instances. It would validate a separate MSTP region consistency operation, not the change needed here. Confirm instead that an underlay capture cannot read protected payload content and transport still reaches the required tunnel endpoints.

Monitor LACP partner IDs, actor keys, member state, and bundle bandwidth after changes. The monitored boundary differs from GRES preserves forwarding not protocols, so the original weakness might reappear unnoticed. GRES preserves forwarding and kernel state but does not by itself preserve all routing or bridging state; NSB targets bridge continuity and NSR or graceful restart addresses routing continuity.

The control protects martian source address rejection. It does not establish the ongoing GRES preserves forwarding not protocols behavior required in this network. GRES preserves forwarding and kernel state but does not by itself preserve all routing or bridging state; NSB targets bridge continuity and NSR or graceful restart addresses routing continuity.

Test BFD session negotiation and routing reaction times during controlled failures. The monitored boundary differs from GRES preserves forwarding not protocols, so the original weakness might reappear unnoticed. GRES preserves forwarding and kernel state but does not by itself preserve all routing or bridging state; NSB targets bridge continuity and NSR or graceful restart addresses routing continuity.

During a controlled routing restart, participating neighbors retain forwarding state only for the permitted grace interval and then converge correctly. That establishes graceful restart peer assistance rather than a repaired LACP aggregation consistency path. The reported failure still requires this evidence: every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior.

The same virtual gateway remains reachable when the active VRRP router is failed in a controlled test. It would validate a separate VRRP virtual gateway failover operation, not the change needed here. Confirm instead that every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior.

The Level 1 router has valid remote-area reachability through the intended L1–L2 boundary without learning the entire L2 topology. It would validate a separate IS-IS L1 and L2 reachability operation, not the change needed here. Confirm instead that every intended member joins the same aggregation and distributes frames according to the approved LAG hash behavior.