The scenario describes a need for multiple users to access shared files (manuals, drawings) that are relatively static but frequently used. A Network Attached Storage (NAS) system is the ideal solution as it is specifically designed for file-level access over a standard Ethernet network using protocols like NFS or SMB/CIFS. This approach provides a centralized, reliable, and reasonably fast method for sharing files without the complexity and cost of a block-level Storage Area Network (SAN). Creating a dedicated Ethernet segment for the NAS can further ensure performance by isolating storage traffic. This directly matches the need to serve files to many users.

A. FC-Arbitrated Loop is block-level storage. Access via a single server creates a bottleneck and is not a direct method for sharing files among many users.

B. Direct block-level connections to all servers require a complex clustered file system for safe file sharing, which is not a simple or standard solution for this use case.

D. A Fibre Channel SAN provides block-level access and is overly complex and expensive for a simple file-sharing requirement. It does not natively serve files to users.

---

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. These devices usually attach to an existing Ethernet network." This supports option C as the most direct method for providing file access services.

Definition of Storage Area Network (SAN): "A network whose primary purpose is the transfer of data between computer systems and storage elements... A SAN provides block-level access to storage." This clarifies why options B and D, which describe block-level SAN/direct-connect architectures, are inappropriate for a direct file-sharing need.

Reference Location: Accessible via the official SNIA website's educational resources section.

2. University of California, Berkeley. EECS Department. CS 162: Operating Systems and System Programming, Lecture 20.

Content: The lecture notes explicitly contrast NAS and SAN. It states, "NAS: Provides a file system interface (NFS, CIFS)... Clients see a file system, not raw blocks." and for SAN, "SAN: Provides block-level interface... Clients see a raw disk." This academic source confirms that for serving files, a NAS is the appropriate architecture.

Reference Location: Slide 43, "NAS vs. SAN," in the "Filesystems 3 (Cloud, Distributed)" lecture presentation.

3. SNIA Education. "Storage Networking Foundations" Tutorial.

Content: This foundational SNIA tutorial explains the fundamental differences between storage architectures. In the section comparing NAS and SAN, it highlights that NAS is optimized for file sharing and collaboration over standard IP networks, making it easy to deploy for use cases like the one described. It positions SAN as a solution for high-performance block I/O, typically for databases and application servers, which is overkill and architecturally incorrect for this scenario.

Reference Location: Section titled "Network Attached Storage (NAS)" and "Storage Area Networks (SAN)".