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 configure the Try Next Closest Site Group Policy Object (GPO) setting in a GPO that is linked to Site1.
Does this meet the goal?
- A. Yes
- B. No Correct
Explanation
No. The Try Next Closest Site setting only changes how a client picks a domain controller when none is available in its own site: it then tries the next closest site based on site-link cost instead of any DC in the domain. It does not make Site1 the primary authentication site. In addition, a GPO linked to Site1 applies only to computers whose IP subnet belongs to Site1, so the branch-office clients would not even receive the setting.
To meet the goal, associate the branch office's IP subnet with Site1 (or create a new site for the branch office and connect it to Site1 through a site link with a lower cost than the links to Site2 and Site3) so that the DC Locator sends the clients to the Site1 domain controllers.
