Your network consists of a single Active Directory domain. All servers run Windows Server 2008 R2. All client computers run Windows 7. Users store all of their files in their Documents folder.
Many users store large files.

You plan to implement roaming user profiles for all users by using Group Policy. You need to recommend a solution that minimizes the amount of time it takes users to log on and log off of the computers that use the roaming user profiles.

What should you recommend?

A.
Modify the Group Policy object (GPO) to include folder redirection.

B.
Modify the Group Policy object (GPO) to include Background Intelligent Transfer Service (BITS) settings.

C.
On the server that hosts the roaming user profiles, enable caching on the profiles share.

D.
On any server, install and configure the Background Intelligent Transfer Service (BITS) server extensions.

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

Planning and Managing Group Policy

Planning your Group Policy is in part planning your organizational structure. If you have a huge number of OUssome inheriting policies, others blocking inheritance, several OUs linking to the same GPO, and several GPOs linking to the same OUyou have a recipe for disaster. While too few OUs and GPOs is also a mistake, most of us err on the side of having too many. Keep your structures simple. Do not link OUs and GPOs across site boundaries. Give your OUs and GPOs meaningful names.

When you are planning Group Policy you need to be aware of the Group Policy settings that are provided with Windows Server 2008. These are numerous and it is not practical to memorize all of them, but you should know what the various categories are. Even if you do not edit any policies, exploring the Group Policy structure in Group Policy Management Editor is worthwhile. You will develop a feel for what is available and whether you need to generate custom policies by creating ADMX files.

You also need a good understanding of how Group Policy is processed at the client. This happens in the following two phases:

Core processingWhen a client begins to process Group Policy, it must determine whether it can reach a DC, whether any GPOs have been changed, and what policy settings must be processed. The core Group Policy engine performs the processing of this in the initial phase.
Client-side extension (CSE) processingIn this phase, Group Policy settings are placed in various categories, such as Administrative Templates, Security Settings,Folder Redirection, Disk Quota, and Software Installation. A specific

CSE processes the settings in each category, and each CSE has its own rules for processing settings. The core Group Policy engine calls the CSEs that are required to process the settings that apply to the client.

CSEs cannot begin processing until core Group Policy processing is completed. It is therefore important to plan your Group Policy and your domain structure so that this happens as quickly and reliably as possible. The troubleshooting section later in this lesson discusses some of the problems that can delay or prevent core Group Policy processing.