Question 380
During an independent network handover at the Fox River branch of Pineview Hospitality, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-8739. The on-duty analyst documents this symptom before proposing any configuration: A router repeatedly ARPs for a distant remote subnet destination on a directly connected interface instead of using the configured next-hop router. 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 unexpected OSPF hellos on edge segments and route presence on legitimate neighbors. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A router repeatedly ARPs for a distant remote subnet destination on a directly connected interface instead of using the configured next-hop router. This alternative addresses a different issue (ospf passive lan interface). The decisive distinction is: Detect ARP requests for nonlocal addresses and route prefix drift.
This alternative addresses a different issue (ipv6 prefix length error). The option would address: Audit RA prefix information and host neighbor/route tables after IPv6 changes. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A router repeatedly ARPs for a distant remote subnet destination on a directly connected interface instead of using the configured next-hop router.
Alert on adjacency down events and area configuration drift. This alternative addresses a different issue (ospf neighbor area mismatch). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A router repeatedly ARPs for a distant remote subnet destination on a directly connected interface instead of using the configured next-hop router. The decisive distinction is: Detect ARP requests for nonlocal addresses and route prefix drift.
The on-duty analyst documents this symptom before proposing any configuration: A router repeatedly ARPs for a distant remote subnet destination on a directly connected interface instead of using the configured next-hop router. That points to this explanation: Detect ARP requests for nonlocal addresses and route prefix drift.