220-1102 Question 386
Single answerAssigning log-in scriptA technician needs to make sure every user in the Sales organizational unit automatically maps drive S: to \FS1\Sales each time they sign in to their Windows domain account. The company wants the setting applied consistently without manually touching each PC. Which action should the technician take?
- A
Create a logon script such as "net use S: \FS1\Sales" and assign it to the Sales users through Active Directory
- B
Create a local startup script on each workstation so the drive maps before any user signs in
- C
Add the command to each user's desktop shortcut target so it runs when Windows loads
- D
Edit the HOSTS file on each workstation to point FS1 to the file server share
Show answer and explanation
Correct answer: A
Explanation
The best answer is to assign a logon script that maps the network drive when the user authenticates. In Windows domain environments, logon scripts are a standard way to configure per-user resources such as mapped drives and printers. This fits the requirement to apply the setting consistently to users in a specific group or organizational unit without manually configuring every workstation. Microsoft best practices for Active Directory environments favor centralized management through user properties or Group Policy rather than local manual changes. Startup scripts are computer-focused, not ideal for user-specific drive mappings. HOSTS files only affect name resolution, and shortcuts do not provide automated, centrally managed logon behavior.
- A. Correct.
Correct. A logon script is designed to run when a user signs in and can map network drives for that user context. In an Active Directory environment, assigning the script to the appropriate users or through Group Policy is the standard centralized method. The command "net use S: \FS1\Sales" is a valid example for mapping a drive during logon.
- B. Incorrect.
Incorrect. A startup script runs at computer startup, typically before the user signs in, and is associated with the computer account rather than the individual user session. This is not the best choice for mapping a user-specific drive letter that should appear when a user logs in, especially when the requirement is to target Sales users rather than all machines.
- C. Incorrect.
Incorrect. A desktop shortcut target does not provide centralized, automatic drive mapping at sign-in. It would require per-user or per-PC manual configuration and would only run if the user launches the shortcut. This does not meet the requirement for consistent automatic application at logon.
- D. Incorrect.
Incorrect. The HOSTS file only resolves hostnames to IP addresses; it does not map shared folders or assign drive letters. Someone might choose this because the file server name FS1 is involved, but name resolution and drive mapping are separate tasks.