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 information 1 .  This database is used to filter and validate DHCP messages from untrusted sources 1 .

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 attacks 1 . 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 database 1 .  The DHCP snooping feature relies on monitoring DHCP messages to build its database 1 , 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 database 1 , and Dynamic ARP inspection (DAI) uses the information stored in the DHCP snooping binding database but does not prevent entries from being created 1 .

According to the Juniper documentation1, a native VLAN is a VLAN that carries untagged traffic on a trunk port. A Wi-Fi access point may need a native VLAN to associate untagged traffic with a specific VLAN, such as the management VLAN. On Juniper EX Series switches, you can enable a native VLAN on a switch port by setting the interface-mode to trunk and specifying a native-vlan-id. For example, the following configuration enables a native VLAN with ID 1 on the switch port ge-0/0/12:

set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode trunk

set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members all

set interfaces ge-0/0/1 unit 0 family ethernet-switching native-vlan-id 1

The other options are not correct because they do not address the requirement of untagged traffic. VLAN tagging is the process of adding a VLAN identifier to a frame, which is not needed for untagged traffic. Flexible VLAN tagging is a feature that allows multiple VLAN tags on a single interface, which is not relevant for this scenario. Voice VLAN is a feature that allows voice traffic to be separated from data traffic on a switch port, which is not related to untagged traffic or Wi-Fi access points. References: Understanding Native VLANs on Trunks | Junos OS, Configuring a Native VLAN on a Trunk Port | Junos OS

Default BGP keepalive timer in Junos is 30 seconds

The default keepalive time for BGP is 30 seconds, which means that BGP peers send keepalive messages to each other every 30 seconds to verify the liveness of the BGP session. If no keepalive message is received from a peer within the hold time, which is 90 seconds by default, the peer is considered to be unavailable and the BGP session is closed. The keepalive time and the hold time can be configured manually for each BGP peer or peer group, but they must match on both ends of the BGP session. The keepalive time should be one third of the hold time for optimal performance. Therefore, option C is correct and the other options are incorrect. References:  BGP keepalive messages and hold time - Juniper Networks