Question 360
The change advisory board sees a repeat risk in this case: During a predeployment review for a public-sector campus, the team discovers this design gap: a compromised endpoint attempts ARP spoofing on the staff VLAN after DHCP snooping is enabled. An approval gate requires both a measurable acceptance check and a durable prevention control. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Maintain binding consistency for statically addressed devices and trusted uplinks. Apply the same control to the public-sector campus rollout checklist. This control targets the underlying design risk. DAI checks ARP packet bindings to reduce ARP spoofing within the Layer 2 broadcast domain. The follow-up acceptance check remains: Forged ARP replies fail validation while legitimate endpoint ARP continues to resolve. The public-sector campus acceptance record also captures this result.
Incorrect Answers
RSTP enables faster convergence than legacy 802.1D in supported topologies when port roles are correctly configured. The repeat risk here is different: DAI checks ARP packet bindings to reduce ARP spoofing within the Layer 2 broadcast domain. A directly relevant preventive control is: Maintain binding consistency for statically addressed devices and trusted uplinks. Apply the same control to the public-sector campus rollout checklist.
UDLD can detect certain unidirectional Layer 2 link conditions that simple physical carrier status misses. The repeat risk here is different: DAI checks ARP packet bindings to reduce ARP spoofing within the Layer 2 broadcast domain. A directly relevant preventive control is: Maintain binding consistency for statically addressed devices and trusted uplinks. Apply the same control to the public-sector campus rollout checklist.
Root Guard prevents a designated switch port from accepting a downstream superior-root claim. The repeat risk here is different: DAI checks ARP packet bindings to reduce ARP spoofing within the Layer 2 broadcast domain. A directly relevant preventive control is: Maintain binding consistency for statically addressed devices and trusted uplinks. Apply the same control to the public-sector campus rollout checklist.