220-1102 Question 13
Single answerResilient File System (ReFS)A technician is preparing a Windows workstation that stores large engineering files on a secondary data volume. Management wants the volume to be more resilient to corruption and to handle large files efficiently. The technician is considering formatting the data volume with Resilient File System (ReFS). Which limitation should the technician identify before making this change?
- A
ReFS cannot be used for the Windows boot/system volume on typical client installations.
- B
ReFS does not support storing large files, so it is unsuitable for engineering data.
- C
ReFS requires the volume to be compressed before Windows can read and write to it.
- D
ReFS can only be used on removable USB drives and not on internal disks.
Show answer and explanation
Correct answer: A
Explanation
The best answer is that ReFS is generally not used as the Windows boot/system volume on typical client installations. In practice, technicians use NTFS for the OS partition and may use ReFS for secondary data volumes when resilience and scalability are priorities. ReFS is intended to improve integrity, detect corruption, and work well with large data sets, which makes it a practical choice for file storage workloads. However, it does not replace NTFS in every scenario. Microsoft documentation and Windows deployment guidance consistently position ReFS as a file system optimized for data volumes rather than standard client boot volumes. For A+ Core 2, the key practical takeaway is to recognize where ReFS fits best: resilient data storage, not the primary Windows installation partition.
- A. Correct.
Correct. ReFS is designed for data resilience and scalability, but on Windows client systems it is generally intended for data volumes rather than the boot/system volume. In a real deployment, this is an important planning limitation: a technician might choose ReFS for a secondary storage volume, but not as a replacement for the main Windows OS partition.
- B. Incorrect.
Incorrect. This is the opposite of one of ReFS's strengths. ReFS was built to support very large volumes and files, making it appropriate for large data sets such as engineering files, virtual disks, and other high-capacity storage scenarios.
- C. Incorrect.
Incorrect. ReFS does not require compression in order to function. In fact, a common misconception is that advanced file systems must depend on features like compression or encryption to be usable. ReFS can be used without compression, and some NTFS features such as file system compression are not supported in the same way on ReFS.
- D. Incorrect.
Incorrect. ReFS is not limited to removable media. It is used primarily for resilient data storage on supported Windows editions and environments, especially on internal disks and storage pools. The misconception here is confusing file system support with a device-type restriction that does not exist.