You need to configure the adatum.com zone to support Name Protection

Your network contains an Active Directory domain named contoso.com. The domain contains a
domain controller named DC1 that runs Windows Server 2012 R2. DC1 has the DNS Server server
role installed.
The network contains client computers that run either Linux, Windows 7, or Windows 8.
You have a zone named adatum.com as shown in the exhibit. (Click the Exhibit button.)

You plan to configure Name Protection on all of the DHCP servers.
You need to configure the adatum.com zone to support Name Protection.
What should you do?

A.
Change the zone type.

B.
Sign the zone.

C.
Add a DNSKEY record.

D.
Configure Dynamic updates.

Explanation:
Name protection requires secure update to work. Without name protection DNS names may be
hijacked.
You can use the following procedures to allow only secure dynamic updates for a zone. Secure
dynamic update is supported only for Active Directory–integrated zones. If the zone type is

configured differently, you must change the zone type and directory-integrate the zone before
securing it for Domain Name System (DNS) dynamic updates.
Enable secure dynamic updates:

DHCP: Secure DNS updates should be configured if Name Protection is enabled on any IPv4 scope
http://technet.microsoft.com/en-us/library/ee941152(v=ws.10).aspx