220-1102 Question 388
Single answerAssigning home foldersA technician is configuring accounts for several users in a small Windows domain. Management wants each user to automatically receive a private network location for storing personal work files whenever they sign in from any company PC. The technician has already created a shared folder on a file server. Which action should the technician take next to meet this requirement most directly?
- A
Edit each user's account properties in Active Directory Users and Computers and configure a Home folder path such as H: mapped to \FileServer\Users%username%
- B
Create a local folder named C:\Home on every workstation and manually set NTFS permissions for each user
- C
Configure a mandatory profile for each user so Documents is redirected to the file server automatically
- D
Add a logon banner that instructs users to browse to the shared folder and create their own personal subfolder
Show answer and explanation
Correct answer: A
Explanation
The best answer is to configure the Home folder setting on each user's domain account so the user receives a mapped drive to a server-based personal folder at logon. In Windows domain environments, this is commonly done in Active Directory Users and Computers by opening the user properties and specifying a drive letter and UNC path. Using a variable such as %username% helps create a per-user path without manually entering each folder name. This approach is consistent with Microsoft best practices for centrally managed user storage and is more appropriate than relying on local folders, mandatory profiles, or user-created directories. Administrators should also ensure the file share and NTFS permissions are configured correctly so each user can access only their own home folder.
- A. Correct.
Correct. In a Windows domain, the standard way to assign home folders is through the user's account properties in Active Directory Users and Computers. The administrator can specify a drive letter and UNC path, commonly using an environment variable such as %username% so each user gets an individual folder. This provides a consistent mapped location at sign-in from any domain-joined PC and aligns with common administrative practice for home directories.
- B. Incorrect.
Incorrect. A local folder on each workstation does not provide the same storage location from any company PC. It also creates unnecessary administrative overhead and fails the requirement for a network-based personal storage location. This option reflects a common misunderstanding between local profile storage and centrally assigned home folders.
- C. Incorrect.
Incorrect. Mandatory profiles control the user environment and prevent profile changes from being saved, but they are not the primary mechanism for assigning a personal network home folder. Folder redirection is a separate configuration, usually managed through Group Policy, and even then it is not the most direct answer to assigning a home folder on the user account.
- D. Incorrect.
Incorrect. Asking users to manually browse to a share and create folders is not secure or scalable. It does not automatically assign a private personal storage location at sign-in, and users may create folders with incorrect permissions or naming. This fails the requirement for automatic assignment and proper administration.