You deployed a new EX Series switch with DHCP snooping enabled and you do not see any entries in the snooping databases for an interface. Which two Juniper configurations for that interface caused…

The correct answer is A. The interface is configured as a disabled port. C. The interface is configured as a trunk port. A is correct because the interface is configured as a disabled port. A disabled port does not forward any traffic, including DHCP packets. Therefore, DHCP snooping cannot learn any MAC addresses or lease information from a disabled port. C is correct because the interface is…

Layer 2 Security

Question

You deployed a new EX Series switch with DHCP snooping enabled and you do not see any entries in the snooping databases for an interface. Which two Juniper configurations for that interface caused this issue? (Choose two.)

Options

AThe interface is configured as a disabled port.
BMAC limiting is enabled on the interface.
CThe interface is configured as a trunk port.
DDynamic ARP inspection is enabled on the interface.

How the community answered

(35 responses)

A
71% (25)
B
17% (6)
D
11% (4)

Explanation

A is correct because the interface is configured as a disabled port. A disabled port does not forward any traffic, including DHCP packets. Therefore, DHCP snooping cannot learn any MAC addresses or lease information from a disabled port. C is correct because the interface is configured as a trunk port. By default, all trunk ports on the switch are trusted for DHCP snooping. This means that DHCP snooping does not inspect or filter any DHCP packets received on a trunk port. Therefore, DHCP snooping does not add any entries to the snooping database for a trunk port.

Topics

#DHCP snooping#snooping database#trunk port#disabled port

Community Discussion

No community discussion yet for this question.

Full JN0-351 Practice