You need to ensure that client computers in SiteH only authenticate to DC1 or DC2 if DC8 fails

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?

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, DC5, 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.

Explanation:
To design a failover strategy to ensure the high availability of domain controllers and to ensure SiteH
only authenticate to DC1 or DC2 if DC8 fails, you need to prevent the domain controllers of all the
spoke sites from registering generic (non-site-specific) domain controller locator DNS records.
Usually 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. 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.
Section I: Hub-and-Spoke Topology
http://support.microsoft.com/kb/306602



Leave a Reply 0

Your email address will not be published. Required fields are marked *