Question 20
During an independent network handover at the Coastal Haven branch of Boreal Industrial Supply, the monitored service is video collaboration for clients in 172.18.14.0/24; incident reference is DC-8127. The on-duty analyst documents this symptom before proposing any configuration: Two hosts in the same VLAN have correct subnet masks, but one cannot forward IPv4 packets because its neighbor entry resolves to an old hardware address. 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
Audit assigned prefixes against IPAM and track unexpected ARP for off-subnet destinations. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Two hosts in the same VLAN have correct subnet masks, but one cannot forward IPv4 packets because its neighbor entry resolves to an old hardware address. This alternative addresses a different issue (subnet mask and on-link decision).
This alternative addresses a different issue (ip versus mac forwarding boundary). The option would address: Watch wrong-gateway complaints, local neighbor failures and route-versus-MAC misconceptions in change review. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Two hosts in the same VLAN have correct subnet masks, but one cannot forward IPv4 packets because its neighbor entry resolves to an old hardware address.
Measure service-specific synthetic checks alongside latency, loss and ICMP reachability. This alternative addresses a different issue (icmp diagnostic scope). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Two hosts in the same VLAN have correct subnet masks, but one cannot forward IPv4 packets because its neighbor entry resolves to an old hardware address. The decisive distinction is: Watch ARP entry churn, duplicate-address alerts and IP-to-MAC changes for the segment.
The on-duty analyst documents this symptom before proposing any configuration: Two hosts in the same VLAN have correct subnet masks, but one cannot forward IPv4 packets because its neighbor entry resolves to an old hardware address. That points to this explanation: Watch ARP entry churn, duplicate-address alerts and IP-to-MAC changes for the segment.