FBAP_002 practice question 13 of 15

A retail customer is designing a new application that will train an AI algorithm with metadata from purchase transactions. The customer has the…

Full set: 75 questions

Domain Implement, Migrate, and Integrate FlashArray and FlashBlade Solutions

A retail customer is designing a new application that will train an AI algorithm with metadata from purchase transactions. The customer has the following constraints: - Billions of transactions per hour - Hundreds of thousands of clients - Easily connect and disconnect from many network locations - Asymmetric encryption across a WAN - Resilience to network latency Which protocol should the architect recommend?
Answer options
A: NFS v3
B: NFS v4.1 *** Correct answer
C: SMB
D: S3
Correct Answer:
B. NFS v4.1 ***
Explanation

The scenario describes a high-performance, large-scale application operating over a Wide Area Network (WAN) with many clients, requiring latency resilience and strong security. NFSv4.1 is the most suitable protocol among the choices because it was specifically designed to address the shortcomings of earlier versions in such environments. Its key feature is the use of compound Remote Procedure Calls (RPCs), which bundle multiple operations into a single request. This significantly reduces network chattiness and improves performance over high-latency WAN links. Furthermore, NFSv4.1 is a stateful protocol, which aids in recovery from network disruptions, and it integrates robust security through Kerberos and the Generic Security Service Application Program Interface (GSS-API), meeting the encryption requirement.

Why Incorrect

A. NFS v3: This version is a stateless and "chatty" protocol, performing poorly over high-latency WANs due to the high number of required network round-trips. It also lacks integrated encryption.
C. SMB: While modern versions have improved WAN performance and security, SMB is primarily designed for and used within Windows-centric environments and is less common for large-scale, heterogeneous AI workloads.
D. S3: S3 is an object storage protocol. It would be unsuitable if the application's metadata processing requires the POSIX semantics, hierarchical directory structure, and file-locking capabilities inherent to a file system protocol.

References

1. Internet Engineering Task Force (IETF) RFC 5661: Network File System (NFS) Version 4 Minor Version 1 Protocol.

Section 1.4, "Goals": Explicitly states "Improved access over wide area networks (WANs)" and "Improved security" as primary goals for the protocol.

Section 2.10.3, "COMPOUND Procedure": Details the mechanism of compounding multiple operations into a single RPC to reduce network round-trips, which is critical for performance on high-latency networks.

2. Garth Gibson & Majd F. Sakr, Carnegie Mellon University, "15-440/640: Distributed Systems, Lecture 21: Distributed File Systems."

The courseware contrasts NFSv3 and NFSv4, explaining that NFSv4's stateful design and compound requests are direct solutions to the performance and recovery problems faced by NFSv3 over WANs. It highlights that compounding reduces latency by minimizing client-server interactions.

3. Pure Storage, "FlashBlade Implementation and Administration Guide Purity//FB 3.2.0."

Section "Managing File Systems": The documentation confirms FlashBlade's support for NFSv4.1, enabling customers to leverage its advanced features. The choice to implement and support v4.1 underscores its importance for modern, demanding workloads that require its specific capabilities over older versions.

Scroll to Top