Question 360
During an independent network handover at the Cedar Valley branch of Dune Mesa Retail, the monitored service is student attendance for clients in 10.52.8.0/23; incident reference is DC-8705. The on-duty analyst documents this symptom before proposing any configuration: Two equal-cost routes are installed, but one large connection uses only one uplink and engineers suspect the second path is broken. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Monitor neighbor transitions and timer-related syslog events. The observed condition is: During an independent network handover at the Cedar Valley branch of Dune Mesa Retail, the monitored service is student attendance for clients in 10.52.8.0/23; incident reference is DC-8705. This alternative addresses a different issue (ospf hello/dead timer mismatch). The decisive distinction is: Track per-next-hop utilization and flow-level path imbalance.
This alternative addresses a different issue (ipv6 link-local gateway). The option would address: Monitor RA receipt, router lifetime and IPv6 default-route disappearance. The scenario instead reports: During an independent network handover at the Cedar Valley branch of Dune Mesa Retail, the monitored service is student attendance for clients in 10.52.8.0/23; incident reference is DC-8705.
Monitor default-route installation and upstream health. This alternative addresses a different issue (default route gap). The reported case is: During an independent network handover at the Cedar Valley branch of Dune Mesa Retail, the monitored service is student attendance for clients in 10.52.8.0/23; incident reference is DC-8705. The decisive distinction is: Track per-next-hop utilization and flow-level path imbalance.
During an independent network handover at the Cedar Valley branch of Dune Mesa Retail, the monitored service is student attendance for clients in 10.52.8.0/23; incident reference is DC-8705. That points to this explanation: Track per-next-hop utilization and flow-level path imbalance.