Your company has a main office and three branch offices. The network consists of a single Active Directory domain. Each office contains an Active Directory domain controller.

You need to create a DNS infrastructure for the network that meets the following requirements:

– The DNS infrastructure must allow the client computers in each office to register DNS names within their respective offices.
– The client computers must be able to resolve names for hosts in all offices.

What should you do?

A.
Create an Active Directoryintegrated zone at the main office site.

B.
Create a standard primary zone at the main office site and at each branch office site.

C.
Create a standard primary zone at the main office site. Create a secondary zone at each branch office site.

D.
Create a standard primary zone at the main office site. Create an Active Directoryintegrated stub zone at each branch office site.

Explanation:
http://searchwindowsserver.techtarget.com/tip/DNS-Primer-Tips-for-understanding-Active-Directory-integrated-zone-design-and-configuration
http://technet.microsoft.com/en-us/library/cc772101.aspx

In an ADI primary zone, rather than keeping the old zone file on a disk, the DNS records are stored in the AD, and Active Directory replication is used rather than the old problematic zone transfer. If all DNS servers were to die or become inaccessible, you could simply install DNS on any domain controller (DC) in the domain. The records would be automatically populated and your DNS server would be up without the messy import/export tasks of standard DNS zone files.

Windows 2000 and 2003 allow you to put a standard secondary zone (read only) on a member server and use one of the ADI primary servers as the master.