220-1102 Question 169
Single answerMapped drivesA user in the Accounting department says the S: drive they use for shared files disappears after every sign-out on their Windows 11 laptop. The drive works if they manually browse to \fileserver\Accounting, and other users in the department keep their S: drive after rebooting. You confirm the user can access the share and has the correct permissions. Which action is the BEST way to restore the drive so it reconnects automatically at future sign-ins?
- A
Map \fileserver\Accounting to drive S: again and select Reconnect at sign-in
- B
Run chkdsk on drive S: to repair file system errors on the mapped drive
- C
Convert the mapped drive to NTFS so Windows can persist the connection
- D
Disable User Account Control so the drive mapping is retained after sign-out
Show answer and explanation
Correct answer: A
Explanation
The best answer is to remap the network share and enable persistent reconnection at sign-in. In Windows, mapped drives are client-side associations between a drive letter and a UNC path such as \server\share. If a user can still access the UNC path directly, the server, network path, and permissions are functioning, so the issue is with how the drive was mapped. Microsoft Windows includes a persistent mapping option when using File Explorer or the net use command with persistence settings. This aligns with standard support practice: verify access to the share, confirm permissions, and then recreate the mapping with automatic reconnection enabled.
- A. Correct.
Correct. A mapped network drive in Windows can be configured to persist across sign-ins by selecting the option typically labeled Reconnect at sign-in when creating the mapping. Since the user can already reach the UNC path and permissions are confirmed, the issue is persistence of the mapping, not connectivity or access. Remapping the drive with the persistent option is the most direct and appropriate fix.
- B. Incorrect.
Incorrect. CHKDSK checks and repairs local or mounted file system errors, but a mapped drive letter pointing to a network share is not repaired this way. The user can already access the network share through the UNC path, so the problem is not disk corruption. This option reflects the common misconception that a drive letter issue is always a storage problem.
- C. Incorrect.
Incorrect. Network shares are hosted on a server-side file system, and a client-side mapped drive is just a shortcut to that share. You do not convert a mapped drive to NTFS from the client to make it persistent. This distractor targets confusion between local disk formatting and network drive mapping.
- D. Incorrect.
Incorrect. User Account Control does not control whether a standard mapped network drive persists after sign-out. Although UAC can affect visibility of mapped drives between elevated and non-elevated contexts in some scenarios, disabling it is not best practice and does not address the user's stated problem of the mapping disappearing after sign-out. This is a plausible but inappropriate troubleshooting step.