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
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
for me the simplest solution is to add SRV records in site definitions of branch offices in DNS. Records contain DCs’ addresses from London site but the priority is greater than priority SRV records of site DCs’.
But from the other hand we can change priority in _tcp and _udp zones in DNS and change priority in SRV records. The London DCs have less value of priority than branch offices DSs. If branch offices DC downs the services addresses are fetched from the _tcp and _udp zones.
The second solution makes less administrative effort then the first.
So, the answer should be D.
@Wojtek just wondering if you would be responding to any other post. Seen a few I wasn’t sure about and seen where you have commented on a few
http://windowsitpro.com/networking/how-can-i-prevent-my-branch-office-domain-controllers-dcs-registering-generic-dns-service
A is correct
https://social.technet.microsoft.com/Forums/windowsserver/en-US/77bc547f-4d0d-4a0c-b463-359b1c771a81/how-to-control-sequence-of-domain-controllers-a-client-computer-logging-on?forum=winserverDS
A is correct.
It appears that altering the SRV DNS records are an older method to address this issue. Windows 2008 has improved the DC Locator function to address these issues.