The question centers on the fundamental decision between block-level and file-level storage access when consolidating servers.

Block-level access is provided by a Storage Area Network (SAN). The server's operating system sees the storage as a raw, unformatted disk volume. This is required for applications that need to control the file system directly, such as database servers or hypervisors (e.g., VMware's VMFS). A traditional Network Attached Storage (NAS) device, which serves files and not blocks, cannot fulfill this requirement.

File-level access is provided by a NAS. The storage is presented to servers as a network file share (e.g., via NFS or SMB protocols). If applications only need to read and write to a pre-existing file system, NAS is a suitable and often more economical and simpler solution to implement and manage than a SAN, as it leverages standard Ethernet networking.

A. While modern NAS can offer high throughput, SANs are typically chosen for latency-sensitive, high-performance transactional workloads. The term "high throughput" is too general to make this a universally true statement for selection.

D. This statement focuses on a secondary requirement (backups) rather than the primary access method (block vs. file), which is the core decision point mentioned in the question's premise.

1. SNIA (Storage Networking Industry Association). SNIA Dictionary.

Definition of Network Attached Storage (NAS): "A term used to refer to storage devices that connect to a network and provide file access services to computer systems." This supports the reasoning that NAS is file-level.

Definition of Storage Area Network (SAN): "A network whose primary purpose is the transfer of data between computer systems and storage elements... The term SAN is usually (but not necessarily) identified with block I/O services." This supports the reasoning that SAN is for block-level access, making NAS unacceptable if block is required (Answer B).

2. Prasad, R., & S. R. (2021). Storage Networks and Data Protection. Wiley.

Chapter 2, Section 2.3 "Network-Attached Storage (NAS)": This chapter explains that NAS systems are specialized file servers that are easy to install and manage, often leveraging existing IP networks, which contributes to their cost-effectiveness compared to dedicated Fibre Channel SANs. This supports the economic argument in Answer C.

Chapter 3, Section 3.2 "Block-Level Access in SAN": This section details how SANs present storage as block devices, which is a prerequisite for servers to create and manage their own file systems (e.g., NTFS, VMFS). This reinforces why a file-serving NAS is unacceptable when block access is a requirement (Answer B).

3. Tanenbaum, A. S., & Van Steen, M. (2017). Distributed Systems: Principles and Paradigms (3rd ed.).

Chapter 11, "Distributed File Systems": This chapter discusses architectures like NFS, which are fundamental to NAS. It contrasts this with block-level services where the client machine's OS is responsible for the file system organization. This academic text confirms the fundamental architectural difference between file-level (NAS) and block-level (SAN) access. This distinction is the basis for both correct answers B and C.