Question 140
A Nexus, UCS or MDS operations team encounters this issue: A rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping. What is the most appropriate remediation for these symptoms?
Explanation
Correct Answer
The root problem is that DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The selected change addresses it directly: Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths. Verify the outcome: Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.
Incorrect Answers
This action concerns ospf keychain authentication rotation, where The OSPF authentication peers are using mismatched active key IDs or validity intervals. The reported failure instead stems from DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.
This action concerns ipv6 router advertisement guard, where The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The corrective response here is “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths”; this alternative does not provide that response.
This action concerns dynamic arp inspection binding validation, where DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The stem reports a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; this control addresses a different failure condition.