Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your network contains an Active Directory Domain Services (AD DS) forest. The forest contains three Active Directory sites named Site1, Site2, and Site3. Each site contains two domain controllers. The sites are connected by using DEFAULTIPSITELINK.
You open a new branch office that contains only client computers.
You need to ensure that the client computers in the new office are primarily authenticated by the domain controllers in Site1.
Solution: You create an organization unit (OU) that contains the client computers in the branch office. You configure the Try Next Closest Site Group Policy Object
(GPO) setting in a GPO that is linked to the new OU.
Does this meet the goal?
- A. Yes
- B. No Correct
Explanation
The solution does not meet the goal. Clients choose a domain controller by using their Active Directory site, and that site is determined by which AD subnet object contains the client's IP address. The new branch office subnet is not defined in AD DS, so the clients belong to no site and are authenticated by any domain controller the DC Locator returns. The Try Next Closest Site Group Policy setting only lets a client fall back to the next closest site (by site link cost) when no domain controller in its own site is available. It cannot make clients prefer Site1, and all three sites share DEFAULTIPSITELINK with the same cost anyway. To meet the goal, create a subnet object for the branch office and associate it with Site1.
