You need to prepare the environment for the installation of Active Directory domain controllers in the branch offices

Your company has a main office and five branch offices. Each office contains servers that run
Windows Server 2008 R2. You need to prepare the environment for the installation of Active
Directory domain controllers in the branch offices. The solution must meet the following
requirements:
• Ensure that the minimum amount of replication traffic is sent between offices.
• Ensure that users always attempt to authenticate to a domain controller in their local office, unless
it is unavailable.
You install the first domain controller on the network in the main office. What should you do next?

Your company has a main office and five branch offices. Each office contains servers that run
Windows Server 2008 R2. You need to prepare the environment for the installation of Active
Directory domain controllers in the branch offices. The solution must meet the following
requirements:
• Ensure that the minimum amount of replication traffic is sent between offices.
• Ensure that users always attempt to authenticate to a domain controller in their local office, unless
it is unavailable.
You install the first domain controller on the network in the main office. What should you do next?

A.
Disable the Bridge all site links option.

B.
Enable Universal Group Membership Caching.

C.
Create a site link and a site link bridge for each office.

D.
Create a subnet object and a site object for each office.

Explanation:
To ensure that the minimum amount of replication traffic is sent between 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. 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 well-designed
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 avoids

communications 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. Within sites, replication is optimized for
speed—data updates trigger replication, and the data is sent without the overhead required by data
compression. Conversely, replication between sites is compressed to minimize the cost of
transmission over wide area network (WAN) links. When replication occurs between sites, a single
domain controller per domain at each site collects and stores the directory changes and
communicates them at a scheduled time to a domain controller in another site.
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



Leave a Reply 0

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