Your company has a main office and a branch office.Your network contains a single Active Directory domain.
The functional level of the domain is Windows Server 2008 R2. An Active Directory site exists for eachoffice.
All servers run Windows Server 2008 R2. You plan todeploy file servers in each office.
You need to design a file sharing strategy to meet the following requirements:
Users in both offices must be able to access the same files.
Users in both offices must use the same Universal Naming Convention (UNC) path to access files.
The design must reduce the amount of bandwidth usedto access files.
Users must be able to access files even if a serverfails.
What should you include in your design?
A.
A standalone DFS namespace that uses replication.
B.
A domain-based DFS namespace that uses replication.
C.
A multisite failover cluster that contains a server located in the main office and another server located in the
branch office.
D.
A Network Load Balancing cluster that contains a server located in the main office and another server
located in the branch office.
Explanation:
DISTRIBUTED FILE SYSTEM
DFS Namespaces enables you to group shared folders that are located on different servers into one or more
logically structured namespaces. Each namespace appears to users as a single shared folder with a series of
subfolders. Domain-based DFS namespace allows to use the same UNC path to access files.
High Availabilityof DFS namespace can be achieved by
1. StandaloneDFS namespace: Created on a failover cluster by using the Cluster Administrator snap-in.
2. Domain-basedDFS namespace: Creating multiple root targets on NON-clustered file servers or on the local
storage of the nodes of server clusters. All root targets must belong to the same domain. (Moreover, at least 2
domain controllers are required to ensure high availability as the metadata of domain-based DFS namespace is
stored in the domain controller)
http://technet.microsoft.com/en-us/library/jj127250
http://technet.microsoft.com/en-us/library/hh341464(v=ws.10).aspx