What should you include in your plan?

Your network is configured as shown in the following diagram.

Each office contains a server that has the File Services server role installed. The servers have a shared folder named Resources. You need to plan the data availability of the Resources folder.
Your plan must meet the following requirements:

If a WAN link fails, the files in the Resources folder must be available in all of the offices.
If a single server fails, the files in the Resources folder must be available in each of the branch offices, and the users must be able to use existing drive mappings.
Your plan must minimize network traffic over the WAN links.

What should you include in your plan?

Your network is configured as shown in the following diagram.

Each office contains a server that has the File Services server role installed. The servers have a shared folder named Resources. You need to plan the data availability of the Resources folder.
Your plan must meet the following requirements:

If a WAN link fails, the files in the Resources folder must be available in all of the offices.
If a single server fails, the files in the Resources folder must be available in each of the branch offices, and the users must be able to use existing drive mappings.
Your plan must minimize network traffic over the WAN links.

What should you include in your plan?

A.
a standalone DFS namespace that uses DFS Replication in a full mesh topology

B.
a domainbased DFS namespace that uses DFS Replication in a full mesh topology

C.
a standalone DFS namespace that uses DFS Replication in a hub and spoke topology

D.
a domainbased DFS namespace that uses DFS Replication in a hub and spoke topology

Explanation:
MCITP Self-Paced Training Kit Exam 70-646 Windows Server Administration:

Distributed File System (DFS)
DFS is considerably enhanced in Windows Server 2008. It consists of two technologies, DFS Namespaces and DFS Replication, that you can use (together or independently) to provide fault-tolerant and flexible file sharing and replication services.

DFS Namespaces lets you group shared folders on different servers (and in multiple sites) into one or more logically structured namespaces. Users view each namespace as a single shared folder with a series of subfolders. The underlying shared folders structure is hidden from users, and this structure provides fault tolerance and the ability to automatically connect users to local shared folders, when available, instead of routing them over wide area network (WAN) connections.

DFS Replication provides a multimaster replication engine that lets you synchronize folders on multiple servers across local or WAN connections. It uses the Remote Differential Compression (RDC) protocol to update only those files that have changed since the last replication. You can use DFS Replication in conjunction with DFS Namespaces or by itself.

Specifying the Replication Topology

The replication topology defines the logical connections that DFSR uses to replicate files among servers. When choosing or changing a topology, remember that that two one-way connections are created between the members you choose, thus allowing data to flow in both directions. To create or change a replication topology in the DFS Management console, right-click the replication group for which you want to define a new topology and then click New Topology. The New Topology Wizard lets you choose one of the following options:

Hub And Spoke This topology requires three or more members. For each spoke member, you should choose a required hub member and an optional second hub member for redundancy. This optional hub ensures that a spoke member can still replicate if one of the hub members is unavailable. If you specify more than one hub member, the hub members will have a full-mesh topology between them.

Full Mesh In this topology, every member replicates with all the other members of the replication group. This topology works well when 10 or fewer members are in the replication group.



Leave a Reply 0

Your email address will not be published. Required fields are marked *