Question 630
At the Northbridge managed-network provider, a malicious endpoint sends DHCP decline messages about leases held by other access ports. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The architectural weakness is that dHCP snooping can reject invalid host lease messages that do not match binding ownership. It can be addressed through the controlled change to apply DHCP snooping validation on the proper untrusted port boundary.
Incorrect Answers
The offered principle is: High-rate unwanted multicast can consume shared switch forwarding capacity. In the source material it is associated with: High-rate unwanted multicast can consume shared switch forwarding capacity. This case has a different controlling cause: DHCP snooping can reject invalid host lease messages that do not match binding ownership. Its keyed mechanism is: DHCP snooping can reject invalid host lease messages that do not match binding ownership.
The offered principle is: 802.1X authentication relies on successful exchange with its configured identity server. In the source material it is associated with: 802.1X authentication relies on successful exchange with its configured identity server. This case has a different controlling cause: DHCP snooping can reject invalid host lease messages that do not match binding ownership. Its keyed mechanism is: DHCP snooping can reject invalid host lease messages that do not match binding ownership.
Although overbroad ACL scope can deny unrelated applications sharing the same switch, the presented symptoms do not support that as the primary cause; they indicate that dHCP snooping can reject invalid host lease messages that do not match binding ownership. For the Northbridge managed-network provider, the direct corrective action is to apply DHCP snooping validation on the proper untrusted port boundary.