DRAG DROP
Your network contains an Active Directory forest named contoso.com.
Your company merges with another company that has an Active Directory forest named litwareinc.com.
Each forest has one domain.
You establish a two-way forest trust between the forests.
The network contains three servers. The servers are configured as shown in the following table.

You confirm that the client computers in each forest can resolve the names of the client computers in
both forests.
On dc1.litwareinc.com, you create a zone named GlobalNames.
You need to recommend changes in both forests to ensure that the users in both forests can resolve
single-label names by using the GlobalNames zone in litwareinc.com.
Which changes should you recommend?
To answer, drag the appropriate configuration to the correct server in the answer area. Each
configuration may be used once, more than once, or not at all. Additionally, you may need to drag the
split bar between panes or scroll to view content.

Answer:

Explanation:
Deploying a GlobalNames zone
The specific steps for deploying a GlobalNames zone can vary somewhat, depending on the AD DS
topology of your network.
Step 1: Create the GlobalNames zone
Step 2(Box 1, box 3) : Enable GlobalNames zone support
The GlobalNames zone is not available to provide name resolution until GlobalNames zone support is
explicitly enabled by using the following command on every authoritative DNS server in the forest:
dnscmd <ServerName> /config /enableglobalnamessupport 1
Step 3:Replicate the GlobalNames zone
Step 4: Populate the GlobalNames zone
Step 5 (box 2) : Publish the location of the GlobalNames zone in other forests
If you want DNS clients in other forests to use the GlobalNames zone for resolving names, add service
location (SRV) resource records to the forest-wide DNS application partition, using the service name
_globalnames._msdcs and specifying the FQDN of the DNS server that hosts the GlobalNames zone.
Deploying a GlobalNames Zone
http://technet.microsoft.com/en-us/library/cc731744.aspx