For CompTIA A+ 220-1202 (Core 2), Domain 1.0 (Operating Systems), Objective 1.1 asks you to recognize common filesystem types and choose the right one for the job. A filesystem is the set of rules an operating system uses to store data on a drive, give files names and folder paths, track free space, and apply protections such as permissions and access control. If you mix up filesystems, you can hit size limits, lose security features, or run into compatibility problems.
This post compares NTFS, ReFS, FAT32, exFAT, ext4, XFS, and APFS in plain terms. You'll see what each one is designed to do, where it's commonly used (Windows, Linux, macOS, or removable media), and which quick limits are easiest to remember for the exam. You'll also learn which features matter most in practice, such as permissions, journaling, encryption support, and how well a filesystem handles large files and large volumes.
For example, copying a 6 GB video to a USB drive often works until you format the drive as FAT32, then the transfer fails because of the file-size cap. Knowing when to choose exFAT instead, or when NTFS is better for permissions, is the kind of decision Objective 1.1 tests.
What a filesystem really controls (and the terms you must know)
A filesystem does more than "store files." It defines how the drive tracks where data lives, what each file is called, who can access it, and what happens after a sudden shutdown. In other words, it's the rulebook that connects raw disk space to folders you can browse.
A few terms show up across Windows, Linux, and macOS, even when the file formats differ:
- Volume: A usable storage area the OS can mount (often a partition, sometimes a whole disk).
- Metadata: Data about data, such as file name, timestamps, size, and permissions.
- Allocation: How the filesystem assigns blocks or clusters to files and keeps track of free space.
Once you know what a filesystem controls, common "mystery errors" start to look predictable.
Size limits and compatibility, why your USB drive sometimes fails
The most common USB headache is simple: FAT32 can't store a single file larger than 4 GB. So a 6 GB video copy fails even though the drive has plenty of free space. The filesystem is not running out of capacity, it's hitting a per-file limit built into FAT32's design.
In contrast, exFAT and NTFS support much larger files, which is why they work better for modern media and backups. exFAT was designed for removable storage, so it often serves as the "big files, broad support" option. NTFS adds stronger security features, although some non-Windows devices only read it.
Compatibility is the other half of the problem. Many TVs, game consoles, and car stereos only read certain formats because vendors pick what they can license, validate, and support. As a result, a drive that works in your laptop might show up as "unsupported" in a console.
A quick way to remember the tradeoff is this:
FAT32 is "old but everywhere," exFAT is "USB-friendly for big files," and NTFS is "Windows-first with security."
If you want a simple memory hook, repeat: "FAT32 fails at 4, exFAT fits, NTFS locks." It's not perfect, but it's good under pressure.
Journaling and copy-on-write, the basics of crash protection
A filesystem also decides how to handle interruptions, such as power loss, a forced restart, or a system crash. Two ideas matter most: journaling and copy-on-write.
Journaling means the filesystem keeps a log of changes it plans to make. If the system crashes mid-write, the OS can use the journal to replay or roll back incomplete operations. This reduces the chance of ending up with a broken directory or "lost" space that needs repair. For CompTIA-style thinking, the key point is that journaling focuses on recovering consistent metadata and filesystem structure after a failure.
Windows NTFS uses journaling, which is one reason it handles abrupt shutdowns better than older FAT variants. Many modern Linux filesystems also use journaling. For example, ext4 is widely taught and widely deployed partly because it balances performance with solid recovery behavior.
Copy-on-write (CoW) takes a different approach. Instead of overwriting existing data in place, the filesystem writes the new version somewhere else first. Then it "switches over" to the new version when the write completes. If the system crashes before the switch, the old data still exists, which can reduce corruption risk.
macOS APFS uses copy-on-write. The practical takeaway is straightforward: journaling and CoW both try to prevent half-finished updates from leaving the drive in a confusing state, but they do it in different ways.
Permissions and encryption, how filesystems can control access
Security features live partly in the operating system, but the filesystem must support them. That's why "format choice" can affect real access control, especially in workplaces.
At a basic level, a filesystem can store ownership information (which user account owns a file) and permissions (who can read, write, or run it). Many systems also use ACLs (Access Control Lists), which allow more detailed rules than simple allow or deny for "everyone." Think of an ACL as a list of named entries, each one granting or denying a specific action to a user or group.
In Windows business settings, NTFS permissions matter because they support strong, granular access control for shared folders, mapped drives, and multi-user PCs. This helps enforce least privilege, meaning users get only the access they need for their role. On a shared PC, that can prevent one user from reading another user's files. On a work laptop, it can help protect sensitive project data from casual browsing.
Encryption often connects to the filesystem choice as well. In many Windows setups, features like EFS (Encrypting File System) and common BitLocker workflows expect NTFS on internal drives because the OS relies on NTFS features for stable policy enforcement and file handling. The key practical point is simple: if you format a drive with a filesystem that lacks the needed security features, Windows can't "add them later" in the same way.
When you choose a filesystem, you are also choosing what security rules the storage can reliably enforce.
Windows filesystems you'll see on the A+ exam: NTFS, ReFS, FAT32, exFAT
For CompTIA A+ 220-1202 (Core 2), Domain 1.0 (Operating Systems), Objective 1.1 expects you to recognize Windows filesystems and pick the right one for the situation. In practice, this comes down to three questions: Do you need strong permissions, do you need protection against corruption, and do you need broad device compatibility? The four names below show up constantly on PCs, USB drives, and external storage, so you should know what each one does best.
NTFS: the default for Windows system drives
Windows uses NTFS for internal drives because it supports the features modern PCs depend on. The biggest advantage is permissions. NTFS stores ownership and ACLs (Access Control Lists), so Windows can enforce detailed rules for users and groups. That matters for shared folders, user profiles, and any business setting where you can't treat everyone as "full access."
NTFS also improves reliability because it uses journaling. If the system loses power mid-write, the journal helps Windows recover consistent filesystem metadata. In other words, NTFS is less likely to leave the "table of contents" for the drive in a broken state. In addition, NTFS handles large files and large volumes well, which is why it fits today's backups, virtual machines, and media libraries.
Several NTFS features show up in real troubleshooting and on the exam:
- Compression: NTFS can compress files and folders to save space (useful, but it can add CPU overhead).
- Disk quotas: Admins can limit how much space a user consumes on a volume.
- Support for Windows security and management features: Many enterprise workflows assume NTFS behavior and metadata.
On the job, NTFS often means you will manage access, not just storage. Common tasks include setting folder permissions in the Security tab, using icacls for permission changes, or fixing access problems by changing ownership.
A few actions come up repeatedly in support tickets:
- Set folder permissions to match least privilege (read-only vs modify).
- Take ownership when a user loses access after a reinstall or profile change.
- Use BitLocker on NTFS volumes for drive encryption workflows, especially on internal drives where policy and recovery keys matter.
Exam tip: If a scenario mentions ACL permissions, ownership, quotas, or compression, NTFS is usually the expected answer.
One warning is worth remembering. NTFS on removable media can perform worse on some devices, especially low-end flash controllers. Also, macOS may read NTFS but often can't write to it without extra tools, which can surprise users who move drives between Windows and Macs.
ReFS: built for data integrity in certain Windows editions
ReFS (Resilient File System) focuses on data integrity. Think of it as a filesystem that puts correctness first, especially when storage gets large and complex.