Your network consists of one Active Directory domain.
All domain controllers run Windows Server 2008 R2 and are configured as global catalog servers. The relevant portion of the network is configured as shown in the exhibit. (Click the Exhibit button.)
The Bridge all site links option is enabled.
You are designing a failover strategy for domain controller availability.
You need to ensure that client computers in SiteH only authenticate to DC1 or DC2 if DC8 fails.
What should you do?
A. Change the B-H site link cost to 50.
B. Remove the global catalog server attribute from DC3, DC4, DCS, DC6, DC7, and DC8.
C. Disable the Bridge all site links option. In SiteB, install a new writable domain controller that runs Windows Server 2008 R2.
D. Prevent DC3, DC4, DC5, DC6, DC7, and DC8 from registering generic (non-site-specific) domain controller locator DNS records.
Correct Answer: D
Explanation/Reference:
The following recommendations are based on the assumptions that in the hub-and-spoke topology, it is preferable that if all domain controllers/global catalogs in a satellite site become unavailable, a client that is searching for a domain controller/global catalog in that site will fail over to a domain controller/global catalog in a central hub and not in another satellite site. This solution is suitable not only for the topology with a single hub site, but also for the topologies with multiple central hubs in case it is irrelevant to which central site a satellite client will fail over.
To achieve this behavior, the domain controllers/global catalogs in the satellite offices should not register generic (non-site-specific) domain controller locator DNS records. These records are registered only by the domain controllers/global catalogs in the central hub. When clients cannot locate the domain controllers/global catalogs serving their site, they attempt to locate any domain controllers/global catalogs using these generic (non- site-specific) domain controller locator DNS records.
The following records should not be registered by the domain controllers/global catalogs in the satellite sites:
Windows Server 2003-based domain controllers
Windows 2000-based domain controllers with Service Pack 2 (SP2) or later installed, or with the hotfix that is specified in the KB article Q267855.
http://support.microsoft.com/kb/306602