BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Juniper Exam JN0-351 Topic 1 Question 33 Discussion

Actual exam question for Juniper's JN0-351 exam
Question #: 33
Topic #: 1
[All JN0-351 Questions]

You have DHCP snooping enabled but no entries are automatically created in the snooping database for an interface on your EX Series switch. What are two reasons for the problem? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

The DHCP snooping feature in Juniper Networks' EX Series switches works by building a binding database that maps the IP address, MAC address, lease time, binding type, VLAN number, and interface information1.This database is used to filter and validate DHCP messages from untrusted sources1.

However, there are certain conditions that could prevent entries from being automatically created in the snooping database for an interface:

MAC limiting: If MAC limiting is enabled on the interface, it could potentially interfere with the operation of DHCP snooping.MAC limiting restricts the number of MAC addresses that can be learned on a physical interface to prevent MAC flooding attacks1. This could inadvertently limit the number of DHCP clients that can be learned on an interface, thus preventing new entries from being added to the DHCP snooping database.

Static IP address: If the device connected to the interface is configured with a static IP address, it will not go through the DHCP process and therefore will not have an entry in the DHCP snooping database1.The DHCP snooping feature relies on monitoring DHCP messages to build its database1, so devices with static IP addresses that do not send DHCP messages will not have their information added.

Therefore, options B and C are correct.Options A and D are not correct because performing a DHCPRELEASE would simply remove an existing entry from the database1, and Dynamic ARP inspection (DAI) uses the information stored in the DHCP snooping binding database but does not prevent entries from being created1.


Contribute your Thoughts:

Skye
5 days ago
Hmm, I was leaning towards A and C, but B makes sense too. This is a tricky one!
upvoted 0 times
...
Nathalie
18 days ago
I agree with you, that could be one reason. Another reason might be that MAC limiting is enabled on the interface.
upvoted 0 times
...
Lyda
18 days ago
I think the correct answers are B and C. If MAC limiting is enabled, DHCP snooping won't create any entries, and a device with a static IP address won't trigger DHCP snooping either.
upvoted 0 times
Ashton
2 hours ago
If both are true, then DHCP snooping won't create any entries.
upvoted 0 times
...
Casie
2 hours ago
So, the correct answers are B and C then.
upvoted 0 times
...
Devora
2 days ago
Also, verify if the device connected has a static IP address.
upvoted 0 times
...
Goldie
4 days ago
Make sure to check if MAC limiting is enabled on the interface.
upvoted 0 times
...
Bernadine
6 days ago
I agree, B and C are the correct answers.
upvoted 0 times
...
Ma
9 days ago
That's true, a device with a static IP address won't trigger DHCP snooping either.
upvoted 0 times
...
Carman
10 days ago
I agree, MAC limiting can prevent DHCP snooping entries from being created.
upvoted 0 times
...
...
Ronald
19 days ago
I think the reason could be that the device has a static IP address.
upvoted 0 times
...

Save Cancel