Your company has a main office and nine branch offices. Each office is configured as a separate
TCP/IP subnet. You plan to deploy Active Directory domain controllers in all offices. You install the
first domain controller for the forest in the main office. You need to prepare the environment for the
deployment of domain controllers in all offices. The solution must ensure that users always
authenticate to a domain controller in their local office, unless it is unavailable. What should you do?
A.
Create 10 subnet objects and one site object. Link all subnet objects to the site. Install domain
controllers in all offices.
B.
Create a subnet object and a site object for each office. Link each subnet object to its respective
site. Install domain controllers in all offices.
C.
Install domain controllers in all offices. Create 10 subnet objects and one site object. Link all
subnet objects to the site.
D.
Install domain controllers in all offices. Create a subnet object and a site object for each office.
Link each subnet object to its respective site.
Explanation:
To prepare the environment for the deployment of domain controllers in all offices and that the
users should always authenticate to their local domain controllers in their local office, unless the
domain controller in their local offices is unavailable, you need to create a subnet object and a site
object for each office and then link each subnet object to its respective site and then install domain
controllers in all offices. You should create sites for all locations in which you plan to place domain
controllers and create subnet objects in AD DS for every IP subnet and subnet mask associated with
each location. Subnet objects are used to represent all the IP addresses within the site. A welldesigned site topology helps an organization to optimize the ability of client computers to locate the
nearest resources, such as domain controllers and Distributed File System (DFS) servers. This helps
client computers to authenticate to their nearest domain controllers. Domain controllers use site
information to inform Active Directory clients about domain controllers present within the closest
site as the client. The domain controller also informs the client whether the chosen domain
controller is the closest one to it. By finding a domain controller in the same site, the client avoidscommunications over WAN links. If no domain controllers are located at the client site, a domain
controller that has the lowest cost connections relative to other connected sites advertises itself in
the site that does not have a domain controller. The domain controllers that are published in DNS
are those from the closest site as defined by the site topology. This process ensures that every site
has a preferred domain controller for authentication.
Creating a Site Design Deciding which locations will become sites
http://technet2.microsoft.com/windowsserver2008/en/library/5ed8b9ca-e88a-4e06-a203-
83d37b54d9bb1033.mspx?mfr=true
Site Functions
http://technet2.microsoft.com/windowsserver2008/en/library/5ed8b9ca-e88a-4e06-a203-
83d37b54d9bb1033.mspx?mfr=true