Juniper JN0-364 Questions & Answers

This principle matters when troubleshooting IS-IS wide metrics, but using it here mistakes a different failure mode for IS-IS adjacency circuit level. The relevant distinction is: IS-IS peers must support a common adjacency level; active Ethernet transport does not compensate for a level mismatch.

IS-IS LSP sequencing and sequence-number PDUs keep link-state databases synchronized; adjacency status alone does not ensure database parity. Those conditions do not account for the specific IS-IS adjacency circuit level problem reported by Coppercrest Cloud.

OSPF neighbor formation requires compatible hello and dead timers; link-layer carrier does not override timer mismatch. That describes OSPF hello and dead timers, whereas the observed symptoms are caused by IS-IS adjacency circuit level; it does not predict the reported behavior.

Equal routing candidates do not prove the forwarding engine is using ECMP; Junos load-balancing policy and flow hashing determine installed next hops. Those conditions do not account for the specific static route next-hop resolution problem reported by Alderbrook Transit.

Although segment routing prefix SID needs this consideration, the failure at issue has a different cause. Junos installs a usable route only after next-hop resolution and route selection; a configured static statement alone does not guarantee active forwarding.

This principle matters when troubleshooting filter-based forwarding table selection, but using it here mistakes a different failure mode for static route next-hop resolution. The relevant distinction is: junos installs a usable route only after next-hop resolution and route selection; a configured static statement alone does not guarantee active forwarding.

Exercise VRRP failover and confirm virtual gateway reachability under device and link failure. The monitored boundary differs from graceful restart peer assistance, so the original weakness might reappear unnoticed. Graceful restart depends on protocol restart and helper behavior; it is not identical to copying live routing protocol state to a backup Routing Engine.

Compare advertised TLVs and learned route counts before and after IS-IS feature upgrades. That ongoing check is for IS-IS TLV reachability; it would not reliably detect recurrence of graceful restart peer assistance. Graceful restart depends on protocol restart and helper behavior; it is not identical to copying live routing protocol state to a backup Routing Engine.

The control protects LACP aggregation consistency. It does not establish the ongoing graceful restart peer assistance behavior required in this network. Graceful restart depends on protocol restart and helper behavior; it is not identical to copying live routing protocol state to a backup Routing Engine.

The forwarding table has a valid outgoing label for the selected next hop and labeled traffic reaches the intended prefix. That establishes LDP label binding completeness rather than a repaired penultimate hop popping path. The reported failure still requires this evidence: the penultimate LSR removes the expected transport label and the egress receives traffic in the planned label state.

Traces show the transport label above the service label with bottom-of-stack marked only on the last label. It would validate a separate MPLS label stack bottom bit operation, not the change needed here. Confirm instead that the penultimate LSR removes the expected transport label and the egress receives traffic in the planned label state.

This measurement tests static route next-hop resolution; it cannot distinguish success from failure for the observed penultimate hop popping condition. Penultimate-hop popping can remove an outer transport label before the egress, reducing egress label processing.

Treat the reserved or martian prefix as invalid for production routing and correct the source instead of overriding safety rejection blindly. This addresses martian source address rejection, but the reported symptoms arise from filter-based forwarding table selection. For this case, verify instead that only the selected traffic uses the inspection forwarding table while unmatched traffic follows the ordinary destination route. Applied here, the relevant facts are: A subset of source traffic should traverse a security inspection RIB, but the global destination route sends it through the ordinary transit exit. The question asks which focused engineering action would best correct the fault.

Align aggregate generation with present contributing routes and confirm the discard or reject behavior and intentional export policy. This addresses aggregate route contributor, but the reported symptoms arise from filter-based forwarding table selection. For this case, verify instead that only the selected traffic uses the inspection forwarding table while unmatched traffic follows the ordinary destination route.

Assign each OSPF router a unique stable router ID and confirm the resulting neighbor and link-state database identities. That could help in a case involving stable OSPF router identifier. This failure instead depends on filter-based forwarding table selection; filter-based forwarding selects a routing lookup table using packet classification; it does not rewrite the global best route for every packet.

Check inter-area prefix availability at each ABR after changes to area boundaries and route filters. The monitored boundary differs from VRRP virtual gateway failover, so the original weakness might reappear unnoticed. VRRP coordinates an active virtual default gateway among participating routers, unlike independent physical interface addresses.

Check negotiated restart capabilities, grace timers, and stale-route expiration in resilience drills. The monitored boundary differs from VRRP virtual gateway failover, so the original weakness might reappear unnoticed. VRRP coordinates an active virtual default gateway among participating routers, unlike independent physical interface addresses.

This is a useful guard against BFD fast failure detection, but it is not scoped to the observed VRRP virtual gateway failover failure. An appropriate test would show that the same virtual gateway remains reachable when the active VRRP router is failed in a controlled test. Applied here, the relevant facts are: A customer subnet loses its default gateway after the active router fails because the backup never assumes the virtual IP role. The question asks which ongoing control would most directly detect or prevent the same failure from recurring.

This is a useful guard against provider Q-in-Q tagging, but it is not scoped to the observed integrated routing and bridging failure. An appropriate test would show that hosts reach the expected IRB gateway and traffic between approved subnets is routed rather than bridged blindly.

This is a useful guard against LDP label binding completeness, but it is not scoped to the observed integrated routing and bridging failure. An appropriate test would show that hosts reach the expected IRB gateway and traffic between approved subnets is routed rather than bridged blindly.

Include tagged and untagged frame tests in trunk turn-up and template drift checks. The monitored boundary differs from integrated routing and bridging, so the original weakness might reappear unnoticed. IRB provides an L3 interface for a Layer 2 VLAN bridge domain; MAC learning alone cannot perform inter-subnet routing.

Ensure a healthy Level 1–Level 2 boundary and appropriate reachable exit or leaked route for the remote destination. Its normal acceptance signal would be the Level 1 router has valid remote-area reachability through the intended L1–L2 boundary without learning the entire L2 topology. Here the deciding check is different: the best route's cumulative OSPF cost selects the approved path and changes predictably when the alternative fails.

Configure the same intended OSPF area and compatible interface parameters on both ends of the link. Its normal acceptance signal would be the pair establishes the expected OSPF adjacency with matching area assignment and reachable learned prefixes. Here the deciding check is different: the best route's cumulative OSPF cost selects the approved path and changes predictably when the alternative fails.

The proposal changes OSPF point-to-point topology; that is not the failure isolated by the facts. It could leave OSPF interface metric selection unresolved even if its own test passed. OSPF chooses lowest-cost paths computed from link-state topology; a Full adjacency alone does not guarantee the desired route preference.

This measurement tests segment routing prefix SID; it cannot distinguish success from failure for the observed MPLS label push swap pop condition. MPLS forwards using labels: ingress commonly pushes labels, intermediate LSRs swap them, and the egress removes the remaining label.

The check is meaningful for OSPF designated router election, but it does not prove that MPLS label push swap pop was repaired. MPLS forwards using labels: ingress commonly pushes labels, intermediate LSRs swap them, and the egress removes the remaining label.

This measurement tests penultimate hop popping; it cannot distinguish success from failure for the observed MPLS label push swap pop condition. MPLS forwards using labels: ingress commonly pushes labels, intermediate LSRs swap them, and the egress removes the remaining label.

This measurement tests IS-IS route redistribution policy; it cannot distinguish success from failure for the observed IS-IS NET and system ID condition. The IS-IS NET encodes area membership and system identity, which must be consistent with the planned level and unique per node.

The check is meaningful for IS-IS wide metrics, but it does not prove that IS-IS NET and system ID was repaired. The IS-IS NET encodes area membership and system identity, which must be consistent with the planned level and unique per node.

The check is meaningful for GRE endpoint underlay routing, but it does not prove that IS-IS NET and system ID was repaired. The IS-IS NET encodes area membership and system identity, which must be consistent with the planned level and unique per node.

The proposal changes OSPF MTU negotiation; that is not the failure isolated by the facts. It could leave OSPF hello and dead timers unresolved even if its own test passed. OSPF neighbor formation requires compatible hello and dead timers; link-layer carrier does not override timer mismatch.

Set an end-to-end MTU that accounts for required additional Ethernet tags and verify supported hardware limits. This addresses provider bridging MTU overhead, but the reported symptoms arise from OSPF hello and dead timers. For this case, verify instead that the adjacency remains Full over successive dead intervals without periodic neighbor expiration.

Verify ABR inter-area advertisement policy and the presence of the appropriate summary reachability in the receiving area. This addresses OSPF area LSA propagation, but the reported symptoms arise from OSPF hello and dead timers. For this case, verify instead that the adjacency remains Full over successive dead intervals without periodic neighbor expiration.