Question 250
During an independent network handover at the Willow Shore branch of Galen Peak Software, the monitored service is engineering build server for clients in 10.41.16.0/24; incident reference is DC-8518. The on-duty analyst documents this symptom before proposing any configuration: A device configured with a /28 mask cannot reach an address thought to belong to its local subnet because it lies in the adjacent /28 block. 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 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 device configured with a /28 mask cannot reach an address thought to belong to its local subnet because it lies in the adjacent /28 block. The decisive distinction is: Audit IPAM allocations, address overlaps and host route table changes.
The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: A device configured with a /28 mask cannot reach an address thought to belong to its local subnet because it lies in the adjacent /28 block. Audit IPAM allocations, address overlaps and host route table changes.
Monitor next-hop tracking, neighbor resolution and static route usability. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A device configured with a /28 mask cannot reach an address thought to belong to its local subnet because it lies in the adjacent /28 block. This alternative addresses a different issue (static route next-hop validation). The decisive distinction is: Audit IPAM allocations, address overlaps and host route table changes.
This alternative addresses a different issue (ipv4 arp versus routing decision). The option would address: Detect ARP requests for nonlocal addresses and route prefix drift. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A device configured with a /28 mask cannot reach an address thought to belong to its local subnet because it lies in the adjacent /28 block.