220-1102 Question 792
Single answerRemapping network drivesA user in a Windows 10 office environment reports that their mapped drive S: no longer opens after the company migrated the shared folder to a new file server. File Explorer shows a red X on S:, and attempting to open it returns a path not found error. The user still has permission to the new shared folder \FS2\Sales. You want to restore access with the least disruption and ensure the drive reconnects after the user signs out and back in. Which action should you take?
- A
Delete the existing S: mapping and map S: to \FS2\Sales with the Reconnect at sign-in option enabled
- B
Run chkdsk on drive S: to repair the mapped drive and restore the connection to the new server
- C
Assign a static IP address to the user's workstation so the old drive mapping can resolve correctly
- D
Create a local folder named Sales on C: and change the S: drive label to match the old network share
Show answer and explanation
Correct answer: A
Explanation
In Windows, mapped network drives are associated with a specific UNC path such as \Server\Share. If the backend file server changes and the path is no longer valid, the mapping must be updated unless the environment uses an abstraction layer like Distributed File System (DFS). Best practice is to disconnect the stale mapping and recreate it using the correct UNC path, selecting the option to reconnect at sign-in if persistent access is required. In GUI terms, this can be done through File Explorer > This PC > Map network drive. From the command line, administrators commonly use commands like 'net use S: /delete' followed by 'net use S: \FS2\Sales /persistent:yes'. Microsoft documentation for mapped drives and the 'net use' command supports this approach for persistent remapping.
- A. Correct.
Correct. A mapped drive that points to an old UNC path will not automatically follow a server migration unless technologies such as DFS are specifically in use. The proper fix is to remove the stale mapping and remap the same drive letter to the new UNC path \FS2\Sales. Enabling Reconnect at sign-in ensures Windows attempts to restore the mapping for future logons, which meets the requirement for persistence with minimal disruption.
- B. Incorrect.
Incorrect. chkdsk checks file system integrity on local disks and some directly attached volumes; it does not update or repair a broken UNC path for a mapped network drive. A red X on a mapped drive after a server migration is typically a connectivity or path issue, not disk corruption.
- C. Incorrect.
Incorrect. The problem is not the workstation's IP addressing but that the mapped drive references an outdated server/share path. Giving the workstation a static IP would not change the UNC target from the old server to \FS2\Sales.
- D. Incorrect.
Incorrect. Creating a local folder and relabeling a drive does not provide access to the network share and does not preserve the user's workflow for the required network resource. This confuses local storage with a network-mapped drive.