Your company has a main office, ten regional datacenters. and 100 branch offices.
You are designing the site topology for an Active Directory forest named contoso.com.
The forest will contain the following servers:
In each regional datacenter and in the main office, a domain controller that runs Windows
Server 2012
In each branch office, a file server that runs Windows Server 2012
You have a shared folder that is accessed by using the path \\contoso.com\shares\software.
The folder will be replicated to a local file server in each branch office by using Distributed
File System (DFS) replication.
You need to recommend an Active Directory site design to meet the following requirements:
Ensure that users in the branch offices will be authenticated by a domain controller in the
closest regional datacenter.
Ensure that users automatically connect to the closest file server when they access
\\contoso.com\shares\software.
How many Active Directory sites should you recommend?
A.
1
B.
10
C.
11
D.
111
Why not 11? one regional datacenter and the closet branch offices per site.
The second requirement says the users need to connect to the closest file server for \\contoso.com\… The closest file server is always in their own office. The only way to do that in this situation is to give each office its own site.
It is 111.
I think it is 11. Look at this requirement: “Ensure that users in the branch offices will be authenticated by a domain controller
in the closest regional datacenter.”
The question does not require that branch users must do logon locally, so it is not necesary to place a DC in each branch office.
I also think it is 11.
As each branch office will have its own subnet and each site will have a subnet range associated with it. The regional datacentre subnet will also fall within the scope of the site subnet range. Therefore branch office PCs will become site aware and linked with their regional datacentre via site/subnet association.
As Authentication will occur at the DC in the same site (As long as the DC is online of course) The users will authenticate at their closest regional datacentre
As DFS is site aware and has the ability to set referral ordering you can force each client to refer to its local DFS file server in its own site and as there are no file servers in the regional datacentres this means the local branch file server will be chosen
And who would want to set up 111 sites in AD anyway… seems like a bad design choice with so many configuration options that can go wrong and an administrative nightmare (subnets, site links, site link costs, site link bridges…… )
Agree with James
DFS is site aware
I think that is correct the D.
Because two observation:
1- You have a shared folder that is accessed by using the path \\contoso.com\shares\software.
2 – The folder will be replicated to a local file server in each branch office by using Distributed File System (DFS) replication.
The DFS configuration will be with name space, so we’ll have AD DC.
I think.
PS: Sorry my English.
Sorry.
The SVN is correct. The C is the correct.
Whilst my AD Design would choose Answer C, my DFS Design would go for Answer D…
Every method of DFS selection relates to AD Sites… Therefore definitely D…
DFS offers three methods of target selection: default target selection, restricted same-site target selection, and least expensive target selection (also called site-costing).
1) Default Target Selection :
By default, DFS lists referrals in the following order:
• Link or root targets in the same site as that of the client. Within this set, DFS lists the targets randomly.
• Link or root targets in sites other than that of the client. Within this set, DFS lists the targets randomly.
Essentially, the client connects to a target in its site if a target is available.
If no targets are available in the client’s site, the client connects to a random target outside its site regardless of the bandwidth cost, connection speed, or the target server’s processing load.
2) Restricted Same-site Target Selection :
By using Dfsutil.exe with the /InSite parameter, you can limit client access to only those targets that are in the same site as the client.
If no same-site targets exist, clients in that site are denied access to the data in the namespace.
3) Least Expensive Target Selection (Site-costing) :
If you create a stand-alone or domain-based DFS root on a server running Windows Server 2003, and the domain controller acting as the Intersite Topology Generator (ISTG) is also running Windows Server 2003, you can use the /SiteCosting parameter in Dfsutil.exe to enable DFS to choose an alternate target based on connection cost if no same-site targets are available.
Note : Whilst the below extract is from Windows 2003, All 2012 / 2012 R2 articles re-direct back to this article…
I know this is not exactly verified information from a trustworthy source, but…
http://serverfault.com/questions/507398/do-i-need-to-configure-active-directory-sites-if-we-have-a-high-speed-wan
Basically the comments by the people there seem to imply that creating one site for multiple physical locations is NOT best practice.
It seems like a lot of the Administration legwork is done automatically if you create a site for each physical location – IE: the nearest Site with a domain controller (lowest cost) will automatically be contacted for authentication. Also, the site’s local file server will be utilized before a remote one.
Both 11, and 111 are correct. Its a really iffy question if you ask me.
I would say 111 is correct though. It just seems easier, more sensible and streamlined.
I’d say D: 111
In each branch office, a file server that runs Windows Server 2012. Ensure that users automatically connect to the closest file server when they access
\\contoso.com\shares\software. So it replicates to each branch office and they have to get it from the nearest one so seeing as there are 100 branch offices and a file server in each office, 111 would make the most sense
Downlaod new Madden 17 Coin Glitch and Generator game!
Best Madden NFL 17 Coin Glitch aand Generator for unlimied Cash and
Coins!
DOWNLOAD LINK : Madden NFL 17 Coin Glich and Generator