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 each office.

All servers run Windows Server 2008 R2. You plan to deploy 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 used to access files.
– Users must be able to access files even if a server fails.

What should you include in your design?

A.
A standalone DFS namespace that uses replication.

B.
A domainbased 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:
MCITP Self-Paced Training Kit Exam 70-646 Windows Server Administration:

Domain-Based Namespaces
You can create domain-based namespaces on one or more member servers or DCs in the same domain. Metadata for a domain-based namespaces is stored by AD DS. Each server must contain an NTFS volume to host the namespace. Multiple namespace servers increase the availability of the namespace and ensure failover protection. A domain-based namespace cannot be a clustered resource in a failover cluster. However, you can locate the namespace on a server that is also a node in a failover cluster provided that you configure the namespace to use only local resources on that server. A domain-based namespace in Windows Server 2008 mode supports access-based enumeration. Windows Server 2008 mode is discussed later in this lesson.

You choose a domain-based namespace if you want to use multiple namespace servers to ensure the availability of the namespace, or if you want to make the name of the namespace server invisible to users. When users do not need to know the UNC path to a namespace folder it is easier to replace the namespace server or migrate the namespace to another server.

If, for example, a stand-alone namespace called \\Glasgow\Books needed to be transferred to a server called Brisbane, it would become \\Brisbane\Books. However, if it were a domain-based namespace (assuming Brisbane and Glasgow are both in the Contoso.internal domain), it would be \\Contoso.internal\Books no matter which server hosted it, and it could be transferred from one server to the other without this transfer being apparent to the user, who would continue to use \\Contoso.internal\Books to access it.