Which statement about NFS and CIFS is true regarding statelessness in traditional discussions?

• A. NFS is stateless and CIFS is stateless
• B. NFS is stateless
• C. CIFS is stateless
• D. NFS is stateful

Answer: (B)

Statelessness in traditional discussions centers on how the server handles client interactions. NFS is described as stateless because the server does not keep per-client session information between requests. Each NFS operation—like reading or writing—contains all the necessary context, and the server relies on the file handle to identify the target file or directory. If the server crashes and comes back up, it doesn't need to reconstruct a long-lived client session; it can start fresh and still process requests, as long as the client provides the needed handles and context.

CIFS (SMB), in contrast, is treated as stateful. When a client connects, a session is established and the server maintains ongoing state about that session—who the user is, which files are open, locks on files, and other per-session data. This stateful model supports features like locking and persistent sessions, but it also means the server bears more complexity in tracking and coordinating that state.

So the statement that NFS is stateless aligns with the traditional view, making it the true one in this context.