220-1102 Question 29
Single answerExternal/hot-swappable driveA user works on a Windows 11 laptop and regularly backs up project files to a USB 3.2 external SSD. The user often disconnects the SSD as soon as the copy window closes. Recently, the user reports occasional file corruption and missing files on the external drive. You confirm the drive is configured as removable storage and write caching may still leave pending writes. Which action should the technician recommend to reduce the risk of data corruption when disconnecting the drive?
- A
Use the Safely Remove Hardware/Eject option before unplugging the external SSD
- B
Disable NTFS permissions on the external SSD so Windows can close files faster
- C
Convert the external SSD to FAT32 so it can be unplugged immediately after copying
- D
Run CHKDSK after every backup job, then disconnect the drive without ejecting
Show answer and explanation
Correct answer: A
Explanation
The best recommendation is to use the operating system's Safely Remove Hardware/Eject function before unplugging an external or hot-swappable drive. In Windows, removable drives may still have data in cache or open file handles even after a copy dialog closes. Ejecting the device ensures pending writes are flushed and the file system is placed in a safe state for removal, reducing the risk of corruption or incomplete files. This aligns with standard Microsoft guidance for USB storage devices and general best practices for removable media handling. While some systems and policies reduce write caching risk, safe ejection remains the most appropriate technician recommendation in a real-world support scenario.
- A. Correct.
Correct. Using Safely Remove Hardware or Eject tells Windows to flush cached writes, close open handles, and prepare the removable device for safe disconnection. This is the recommended best practice for external and hot-swappable storage when there may be pending write activity. It directly addresses the user's issue of disconnecting the drive too quickly after file operations.
- B. Incorrect.
Incorrect. NTFS permissions control access to files and folders, not whether data is still buffered for writing. Disabling permissions would not prevent corruption from unplugging a drive before cached writes are complete, and it could reduce security.
- C. Incorrect.
Incorrect. FAT32 does not solve the underlying issue of pending writes or improper removal. In addition, FAT32 has significant limitations, including a maximum file size of 4 GB, which makes it a poor choice for many modern backup scenarios. The misconception is that a simpler file system makes removal inherently safe, which is not true.
- D. Incorrect.
Incorrect. CHKDSK can help detect and repair some file system errors after a problem occurs, but it is not a preventive step for safe removal. Running CHKDSK after every backup is unnecessary and does not replace properly ejecting the drive before disconnecting it.