PrepAway - Latest Free Exam Questions & Answers

What should you include in the recommendation?

Your company has a main office and four branch offices. The main office is located in
London.
The network contains an Active Directory domain named contoso.com. Each office contains
one domain controller that runs Windows Server 2012. The Active Directory site topology is
configured as shown in the exhibit. (Click the Exhibit button.)
You discover that when a domain controller in a branch office is offline for maintenance,
users in that branch office are authenticated by using the domain controllers in any of the
sites.
You need to recommend changes to Active Directory to ensure that when a domain
controller in a branch office is offline, the users in that branch office are authenticated by the
domain controllers in London.
What should you include in the recommendation?
Exhibit

PrepAway - Latest Free Exam Questions & Answers

A.
Modify the DC Locator DNS Records settings.

B.
Disable site link bridging.

C.
Modify the site link costs.

D.
Modify the service location (SRV) records in DNS.

Explanation:
After having read several articles on the subject, I would say the correct answer for this
question would be modifying the DC locator DNS record. Though I have never used it in any
environment I worked in. But I am not sure. If anyone can clarify this one, mail me at
badmuts13(a)gmail.com

2 Comments on “What should you include in the recommendation?

  1. Massimo says:

    Correct answer is A; site links are only used for *replication*, not for *authentication*.
    Locating a DC for authentication is based on DNS SRV records, and all domain controllers have a default behavior of registering themselves as available for authentication in *all* sites; if you instead only want them to perform authentication for *their* site (and possibly for immediately-adiacent sites), you need to tell them which sites they should cover; that’s done by editing the group policy settings controlling DC Locator DNS settings: https://support.microsoft.com/en-us/kb/306602.




    0



    0

Leave a Reply