CompTIA Server+ guideStudy & preparation
CompTIA Server+ NAS vs SAN: Choose File or Block Storage
Short answer
Choose from what the host must access: shared files point to a file-storage protocol such as NFS, while shared SCSI logical units over TCP/IP point to iSCSI. RFC 7530 defines NFS as a distributed file-system protocol, and RFC 7143 defines iSCSI as SCSI transport over TCP. A virtualization workload or the word shared alone does not settle the choice; the required storage interface and permitted transport do.
What must the server see: files or a SCSI logical unit?
Choose shared file storage when the requirement is access to files; choose iSCSI when it explicitly requires shared SCSI logical units over TCP/IP. The defining distinction comes from the protocol specifications: RFC 7530 describes NFS as a distributed file-system protocol, while RFC 7143 describes iSCSI as a transport for SCSI over TCP.
For this comparison, a logical unit is the SCSI storage presented to the host: the scenario asks the host to access a disk through SCSI operations. An NFS export instead gives the client file-system access. Start with that difference before trying to match a product name.
CompTIA's SK0-005 objectives, document version 7.0, checked November 11, 2026, list NAS with NFS/CIFS and SAN with iSCSI/Fibre Channel/FCoE under objective 1.2. Those names establish the study scope. They do not mean every storage question is answered by remembering two acronym lists. For the wider objective map, see what is on the CompTIA Server+ exam. Objective 1.2 sits in Server Hardware Installation and Management, and 108 questions on that domain are planned for full CompTIA Server+ prep.
When you read a scenario, finish this sentence first: “The client must access ___.” Write files or SCSI logical units only when the wording supports it; otherwise, mark the interface as unknown.
Which protocol matches the stated network constraint?
After identifying the interface, read the transport requirement. RFC 7143's definition makes iSCSI a match for a stated need to carry SCSI operations over TCP/IP. It does not make every IP-based shared-storage requirement an iSCSI requirement: NFS provides shared file-system access.
Use this editorial decision table to separate the two clues:
| Requirement in the scenario | What it establishes | Supported conclusion |
|---|---|---|
| Clients must access an NFS file export | File-system access is explicitly required | NFS fits the stated interface |
| Hosts must access shared SCSI logical units over TCP/IP | Both the SCSI interface and transport are specified | iSCSI fits those requirements |
| Several hosts need shared storage on an IP network | Sharing and network context are known; the interface is missing | Ask whether the hosts require files or SCSI logical units |
| A virtualization platform needs shared storage | The workload is identified; its storage interface is not | Check the platform's stated storage requirement before selecting a protocol |
Do not substitute “networked” for “SAN.” CompTIA lists several SAN technologies, including iSCSI, so SAN does not mean Fibre Channel exclusively. Equally, the presence of an IP network does not tell you which storage interface the host needs. For protocol names you want at quick recall, short recall cards sorted by SK0-005 domain are planned for full CompTIA Server+ prep.
Your next step is to underline one interface clue and one transport clue. If you cannot find both, identify the missing requirement instead of supplying one from memory.
Why does a virtualization scenario not automatically mean SAN?
The words “virtual machines need shared storage” identify a workload and a sharing requirement; they do not specify files or SCSI logical units. Read the platform requirements before selecting a protocol. A scenario must supply enough detail to establish the required interface.
Compare these two hypothetical requirements. For each invented example, assume that the platform supports the stated configuration:
- “The platform is configured to use an NFS datastore.” This specifies file-system access through NFS.
- “The platform requires shared SCSI logical units over the existing TCP/IP network.” This specifies the interface and transport that iSCSI provides.
The deciding words are the requirements following “platform,” not the fact that the platform runs virtual machines. Do not infer that one option is always faster or that choosing either protocol alone establishes high availability. A claim about either property needs evidence about the actual design.
In study notes, replace “virtualization means SAN” with a question: “What does this host need the storage service to present?”
How do three different requirement sets change the answer?
These are invented study scenarios with declared assumptions, not recalled exam questions or observed lab results. Each asks for the interface choice only; none supplies enough information for a full production design.
Scenario 1: a shared file collection. A document-processing server must read and write files in an existing NFS export. The client supports NFS, and the assignment is to use that export. Choose NFS: the requirement already specifies file-system access. Choosing iSCSI would replace the requested interface with SCSI logical units. The decisive evidence is the named export, not the number of files or clients.
Scenario 2: shared SCSI storage on TCP/IP. A supplied platform specification requires shared SCSI logical units and names TCP/IP as the transport. Compatible iSCSI endpoints are available in this fictional setup. Choose iSCSI because both parts of the requirement match its protocol definition. This answers the protocol-selection question; it does not establish whether any particular platform configuration is complete or supported.
Scenario 3: an incomplete request. A team asks for “reliable shared storage for virtual machines on our IP network.” It does not say whether the platform needs an NFS datastore or SCSI logical units. Do not choose NAS or SAN yet. Ask what interface the platform requires and what evidence will demonstrate the requested reliability. “Shared,” “virtual machines,” and “IP” leave the interface unresolved.
To check your reasoning, change one requirement in a scenario and explain whether the answer changes. Changing Scenario 1 from an NFS export to shared SCSI logical units over TCP/IP changes the interface requirement and therefore the protocol choice. Every question planned for full CompTIA Server+ prep explains why each option fits or fails, which is a useful check on this one-change test.
What should you verify before choosing storage?
Use a short decision record for each practice case:
- Required access: copy the words that establish files or SCSI logical units.
- Transport: record the stated network constraint without inventing additional equipment.
- Protocol match: explain how the chosen protocol satisfies both requirements.
- Missing evidence: list any unresolved compatibility, performance or availability requirement.
- Decision boundary: state what your answer settles and what still needs checking.
For a hands-on exercise, the small Server+ home-lab guide helps you define a contained setup and evidence checkpoints. If storage is already configured and the issue is a sudden write slowdown, the separate RAID cache troubleshooting guide addresses that diagnostic task.
Try the 20 free Server+ practice questions, then add any unresolved storage distinction to your free Server+ study plan. For the next review session, write one complete requirement that supports NFS, one that supports iSCSI, and one that still needs clarification. Explain the deciding words in each before naming the answer.
Trust the source
Official sources
Exam policies can change. Use these primary sources for the most current details.