The healthcare customer already has a FlashArray//X50 with 35 usable TB free and anticipates storing 15 TB of medical imaging data. Since the system load is currently 35%, they can enable FA File on the array as-is to support the new workload.
Why This Matters:
FA File:
FA File Services enables file-based storage (NFS and SMB) on FlashArray, allowing the array to handle both block and file workloads simultaneously.
With 35 TB of free capacity and only 15 TB required for medical imaging, there is sufficient space to accommodate the new workload.
The current system load of 35% indicates that the array has ample headroom to handle the additional workload without requiring upgrades.
Why Not the Other Options?
A). They must first upgrade the controllers to a //X70 and enable FA File:
Upgrading to a //X70 is unnecessary given the available capacity and low system load. The current //X50 is capable of supporting the workload.
C). Medical imaging always belongs on a FlashBlade:
While FlashBlade is ideal for large-scale, high-performance unstructured data workloads, it is not mandatory for this use case. FA File on FlashArray//X50 is sufficient for 15 TB of medical imaging data.
D). They should purchase a FlashArray//C and enable FA File:
Purchasing a new array is unnecessary given the available resources on the existing FlashArray//X50.
Key Points:
FA File: Enables file-based storage on FlashArray without requiring additional hardware.
Capacity and Load: The array has sufficient free space and performance headroom to handle the new workload.
Cost Efficiency: Avoids unnecessary upgrades or purchases, optimizing costs while meeting requirements.
Reference: Pure Storage FlashArray Documentation: "FA File Services Overview" Pure Storage Whitepaper: "Consolidating Workloads on FlashArray" Pure Storage Knowledge Base: "Supporting Multiple Workloads with FlashArray"