Your company has a main office and two branch offices. The main office is located in London. The
branch offices are located in New York and Paris. Your network consists of an Active Directory forest
that contains three domains named contoso.com, paris.contoso.com, and newyork.contoso.com. All
domain controllers run Windows Server 2008 R2 and have the DNS Server server role installed. The
domain controllers for contoso.com are located in the London office. The domain controllers for
paris.contoso.com are located in the Paris office. The domain controllers for newyork.contoso.com
are located in the New York office. A domain controller in the contoso.com domain has a standard
primary DNS zone for contoso.com. A domain controller in the paris.contoso.com domain has a
standard primary DNS zone for paris.contoso.com. A domain controller in the newyork.contoso.com
domain has a standard primary DNS zone for newyork.contoso.com. You need to plan a name
resolution strategy for the Paris office that meets the following requirements:
• If a WAN link fails, clients must be able to resolve hostnames for contoso.com.
• If a WAN link fails, clients must be able to resolve hostnames for newyork.contoso.com.
• The DNS servers in Paris must be updated when new authoritative DNS servers are added to
newyork.contoso.com.
What should you include in your plan?
A.
Configure conditional forwarding for contoso.com. Configure conditional forwarding for
newyork.contoso.com.
B.
Create a standard secondary zone for contoso.com. Create a standard secondary zone for
newyork.contoso.com.
C.
Convert the standard zone into an Active Directoryintegrated zone. Add all DNS servers in the
forest to the root hints list.
D.
Create an Active Directoryintegrated stub zone for contoso.com. Create an Active
Directoryintegrated stub zone for newyork.contoso.com.
Explanation:
http ://technet.microsoft.com/en-us/library/cc771640.aspx
http ://technet.microsoft.com/en-us/library/cc771898.aspx
Understanding Zone Delegation
Applies To: Windows Server 2008, Windows Server 2008 R2
Domain Name System (DNS) provides the option of dividing up the namespace into one or more
zones, which can then be stored, distributed, and replicated to other DNS servers. When you are
deciding whether to divide your DNS namespace to make additional zones, consider the following
reasons to use additional zones:
• You want to delegate management of part of your DNS namespace to another location or
department in your organization.
• You want to divide one large zone into smaller zones to distribute traffic loads among multiple
servers, improve DNS name resolution performance, or create a more-fault-tolerant DNS
environment.
• You want to extend the namespace by adding numerous subdomains at once, for example, to
accommodate the opening of a new branch or site.
Secondary zone
When a zone that this DNS server hosts is a secondary zone, this DNS server is a secondary source
for information about this zone. The zone at this server must be obtained from another remote DNS
server computer that also hosts the zone. This DNS server must have network access to the remote
DNS server that supplies this server with updated information about the zone. Because a secondary
zone is merely a copy of a primary zone that is hosted on another server, it cannot be stored in AD
DS.
