Study Storage Devices, Interfaces and RAID Basics for A+ Core 1 (220-1201)
Separate drive types, form factors, interfaces, file systems, and RAID trade-offs the way A+ Core 1 expects.
Storage questions on Core 1 often hide the real answer inside terminology. The exam wants you to keep drive technology, physical form factor, connector style, file system choice, and redundancy model separate in your head.
NVMe: Non-Volatile Memory Express, a storage protocol designed for fast solid-state storage over PCIe.
SMART: Self-Monitoring, Analysis and Reporting Technology, the health-reporting system many drives use to surface warning signs.
What CompTIA is really testing
CompTIA usually wants you to:
- distinguish HDD, SATA SSD, and NVMe SSD behavior
- know that
M.2andNVMeare not the same thing - understand the most common RAID trade-offs at a support level
Fast storage chooser
| If the requirement is… | Stronger answer |
|---|---|
| lowest cost bulk storage | HDD |
| general laptop or desktop upgrade | SATA SSD or NVMe SSD depending on support |
| highest client performance with proper support | NVMe over PCIe |
| redundancy with two disks | RAID 1 |
| redundancy and stronger performance with more disks | RAID 10 |
Form factor, interface, and protocol are not the same thing
| Question type | What it is really asking |
|---|---|
| form factor | physical size or shape such as 2.5-inch or M.2 |
| interface | how the device connects, such as SATA or PCIe |
| protocol | how storage commands are spoken, such as NVMe |
That distinction is one of the easiest ways to eliminate wrong answers quickly.
File-system fit still matters
| File system | A+ support-level use |
|---|---|
NTFS | common Windows choice with permissions and larger feature set |
exFAT | good cross-device removable-media option |
FAT32 | older or compatibility-focused use, but with real size limits |
Small evidence example
1diskpart
2list disk
3select disk 1
4detail disk
What to notice:
- detection comes before formatting
- a missing disk is not the same problem as an uninitialized disk
- support questions often separate hardware visibility from file-system readiness
Commonly confused ideas
| Pair | Distinction |
|---|---|
M.2 vs NVMe | M.2 is the form factor; NVMe is the protocol |
SATA vs NVMe | both can be SSD paths, but NVMe is usually much faster |
| snapshot vs backup | snapshot is short-term state; backup is safer recovery protection |
SMART and failure thinking
A+ wants you to react sanely to drive-failure indicators:
- preserve data first
- back up before experimenting
- replace failing storage rather than trusting it
Harder scenario question
A laptop owner wants “the fastest upgrade possible” and buys an M.2 drive, but the system firmware never detects it. The stem also hints that the laptop documentation supports only a SATA-based M.2 slot.
The strong answer usually notices that:
- the physical slot existing is not enough
M.2does not guaranteeNVMe- compatibility beats raw speed claims
What strong answers usually do
- verify what the motherboard or laptop actually supports
- keep file system and hardware decisions separate
- understand that faster is not the only requirement if compatibility is missing
- preserve user data before trying risky fixes on a questionable drive