A Cisco Catalyst switch that is prone to reboots continues to rebuild the DHCP snooping database. What is the solution to avoid the snooping database from being rebuilt after every device reboot?

A Cisco Catalyst switch that is prone to reboots continues to rebuild the DHCP snooping database. What is the solution to avoid the snooping database from being rebuilt after every device reboot? 

A. A DHCP snooping database agent should be configured. 
B. Enable DHCP snooping for all VLANs that are associated with the switch. 
C. Disable Option 82 for DHCP data insertion. 
D. Use IP Source Guard to protect the DHCP binding table entries from being lost upon rebooting. 
E. Apply ip dhcp snooping trust on all interfaces with dynamic addresses. 

Correct Answer: A 
Explanation 
Explanation/Reference: 
Minimum DHCP Snooping Configuration 
The minimum configuration steps for the DHCP snooping feature are as follows: 
1.Define and configure the DHCP server. 
2. Enable DHCP snooping on at least one VLAN. 
By default, DHCP snooping is inactive on all VLANs. 
3.Ensure that DHCP server is connected through a trusted interface. By default, the trust state of all interfaces is untrusted. 
4.Configure the DHCP snooping database agent. This step ensures that database entries are restored after a restart or switchover. 
5.Enable DHCP snooping globally. The feature is not active until you complete this step.