Question 280
During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. 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
Measure convergence intervals and route flap frequency during fault drills. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (ospf route withdrawal after failure). The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.
This alternative addresses a different issue (ospf neighbor area mismatch). The option would address: Alert on adjacency down events and area configuration drift. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.
Audit RA prefix information and host neighbor/route tables after IPv6 changes. This alternative addresses a different issue (ipv6 prefix length error). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.
The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. That points to this explanation: Monitor next-hop tracking, neighbor resolution and static route usability.