FlashArray//C is the most cost-effective solution for this use case. It is specifically designed as a capacity-optimized all-flash array, utilizing higher-density QLC NAND flash to offer flash-level performance and reliability at a cost competitive with hybrid or HDD-based systems. For a video archive workload, where capacity and cost-effectiveness are prioritized over the extreme low-latency performance of Tier 1 applications, FlashArray//C provides the ideal balance. It allows the customer to modernize their multi-rack HDD environment into a smaller, more efficient all-flash footprint without the premium cost associated with performance-optimized arrays.

A. FlashArray//X: This is a performance-optimized array for Tier 1 workloads. It would be unnecessarily expensive and over-provisioned for a capacity-centric video archive, making it not the most cost-effective solution.

B. FlashArray//XL: This is the highest-performance model in the FlashArray family, designed for the most demanding Tier 0/1 applications. It is the least cost-effective option for an archive workload.

1. Pure Storage FlashArray//C™ Data Sheet: "FlashArray//C is the industry’s first capacity-optimized AFA, designed to bring consistent all-flash performance to tier-2 production and workload consolidation applications... It provides a cost-effective, capacity-oriented solution for use cases that don’t demand the extreme performance of FlashArray//X." (Page 1, "Product Overview"). This document explicitly positions FlashArray//C for Tier 2 applications like archives as a cost-effective alternative.

2. Pure Storage FlashArray Family Data Sheet: This document compares the product lines. It positions FlashArray//X and //XL for "Performance-sensitive workloads" and "Mission-critical applications," respectively. In contrast, it positions FlashArray//C for "Capacity-oriented workloads" and "Workload consolidation," directly aligning with the customer's video archive requirement. (Page 2, "FlashArray Models" table).

3. Pure Storage White Paper, "The Pure Storage Guide to Modern Data Protection": While focused on data protection, this paper discusses workload tiers. It describes the need for a "flash-to-flash-to-cloud" architecture where capacity-optimized flash (like FlashArray//C) serves as a tier for less active data, backups, and archives, replacing slower disk-based systems. (Section: "Modernize Your Data Protection").

FlashArray File Services provides native SMB and NFS protocol support, allowing the FlashArray to serve as a unified storage platform for both block and file workloads simultaneously. This capability is a software feature of the Purity//FA operating environment and is supported across the FlashArray family, including the FlashArray//X, //C, and //XL models. The customer's existing //X90R3 is a FlashArray//X model and is therefore fully capable of running File Services alongside their existing Oracle block volumes, provided it is running a compatible version of Purity//FA. No hardware upgrade is required to enable this functionality.

A. The customer should migrate their Windows file servers to Pure.

This option describes a potential action or sales outcome, not a technical feasibility assessment of the existing hardware, which is the core of the customer's question.

B. The customer needs to upgrade to XL to be able to use FA File.

This is incorrect. FlashArray File Services are not exclusive to the //XL models. The feature is available on all modern FlashArray//X models, including the customer's //X90R3.

---

1. Pure Storage FlashArray Data Sheet. (2023). "Unified Block and File: Consolidate every workload with a single platform for block and file." The data sheet lists FlashArray//X models (including the //X90) as part of the product line that supports unified storage. Document available via Pure Storage official website.

2. Pure Storage. (2022). FlashArray File Services: Technical Overview. "FlashArray File Services is available on all FlashArray//X, FlashArray//C, and FlashArray//XL models, providing a unified storage experience for all of your block and file workloads." (Page 3, Section: "FlashArray File Services"). This white paper explicitly confirms support on the //X series.

3. Pure Storage Purity//FA 6.1 Release Notes. (2021). The introduction of FlashArray File Services in this release specified support for FlashArray//X and FlashArray//C models, establishing the feature's availability on the hardware platform mentioned in the question. Historical release notes confirm the feature is not limited to newer or specific high-end models.

Cloud Block Store (CBS) is a software-defined storage solution that runs natively in public clouds, including Azure. It directly addresses the customer's requirements by providing enterprise-grade data reduction (deduplication and compression), which can significantly lower the actual cloud storage footprint and associated costs for the 100 TB database. As a cloud-native service procured through the Azure Marketplace, it aligns perfectly with a cloud-first strategy and requires no capital asset purchase, operating on a consumption-based model. CBS is specifically designed to deliver high-performance, resilient block storage for mission-critical applications like databases in the cloud.

A. Evergreen//Flex: This is a consumption-based ownership model for on-premises physical hardware, which contradicts the customer's cloud-first strategy and desire to avoid owning additional assets.

B. Evergreen//Forever: This is a subscription model that provides continuous software and hardware upgrades for customer-owned, on-premises FlashArray systems, requiring a capital expenditure.

D. Portworx DBaaS: This is a Database-as-a-Service platform for Kubernetes. While it operates in the cloud, its primary function is to automate database deployment and management, not to provide the underlying cost-optimized block storage itself.

1. Pure Storage Cloud Block Store for Microsoft Azure Datasheet: "Pure Cloud Block Store brings all the benefits of Pure’s enterprise-grade storage to the public cloud... With industry-leading data reduction, you’ll buy less cloud storage capacity." (Page 1, "Reduce Cloud Storage Costs" section). This document confirms CBS runs in Azure and its primary benefit is cost reduction through data efficiency.

2. Pure Storage Evergreen Subscriptions: "Evergreen//Forever™ (formerly Evergreen Gold) keeps your storage modern without disruptive migrations... Evergreen//Flex™ gives you a flexible, on-demand storage consumption model for the storage you own." (Pure Storage Official Website, Evergreen Page). This source clarifies that both Evergreen//Forever and //Flex are tied to on-premises, owned hardware.

3. Portworx Data Services Documentation: "Portworx Data Services (PDS) is a database-platform-as-a-service that you can use to deploy and manage data services such as Cassandra, Kafka, PostgreSQL, RabbitMQ, and Redis on any Kubernetes cluster." (Portworx Official Documentation, "About Portworx Data Services" section). This reference establishes PDS (DBaaS) as a management layer for databases on Kubernetes, distinct from the underlying block storage optimization provided by CBS.

The customer requires 450 TB of effective capacity. With an expected 4-to-1 data reduction, the minimum required usable capacity is calculated as 450 TB / 4 = 112.5 TB.

The workload is for a tier 2 environment where latency is not a concern, which makes the capacity-optimized Pure Storage FlashArray//C the appropriate product line. The FlashArray//X is designed for tier 1, performance-sensitive workloads.

The FlashArray//C40 is the entry-level model in the //C series. Its minimum configuration provides 247 TB of raw capacity, which yields approximately 201 TB of usable capacity. Since 201 TB is greater than the required 112.5 TB, this configuration meets the customer's needs and represents the minimum required solution.

B. FlashArray//C60R3 878 TB: This is a valid FlashArray//C configuration, but it is significantly oversized for the requirement and is not the minimum option.

C. FlashArray//X70R3 228 TB: This is an incorrect product family. FlashArray//X is designed for performance-sensitive, tier 1 workloads, not capacity-oriented tier 2 environments.

D. FlashArray//C60R3 366 TB: While this configuration would meet the capacity need, the FlashArray//C40 is a smaller, more cost-effective model that also satisfies the requirement, making it the correct minimum choice.

1. Pure Storage FlashArray//C Family Datasheet. (Document: pure-datasheet-flasharray-c.pdf).

Page 1, "Capacity for Everything": "FlashArray//C is the industry’s first capacity-optimized AFA, designed for tier 2 production and workload consolidation...". This justifies the selection of the //C family over the //X family for this use case.

Page 2, "FLASHARRAY//C SPECIFICATIONS" Table: This table specifies the "Min. Raw Capacity" for the FlashArray//C40 R3 model as 247 TB and for the FlashArray//C60 R3 as 366 TB. This confirms that option A represents the smallest available configuration in the appropriate product family that meets the calculated capacity requirement.

2. Pure Storage FlashArray Architecture White Paper. (Document: pure-wp-flasharray-architecture.pdf).

Section: "Purity Reduce": This section details how Purity's data reduction technologies (including deduplication and compression) provide an average data reduction of 5:1 across the fleet, with total efficiency of 10:1. This supports the methodology of calculating required usable capacity based on the customer's expected data reduction ratio (4-to-1).

The FlashArray//X, running the Purity//FA operating environment (version 6.0 and later), provides native, unified file and block services. This allows the customer to serve both workload types from the same array and the same global storage pool. Since the customer has 40 TB of available capacity, which is more than sufficient for the new 10 TB file workload, they can simply enable and configure file services on their existing hardware. This approach requires no additional hardware purchase, making it the most cost-effective solution and directly addressing the customer's primary constraint to spend the least amount possible.

B. FlashArray architecture is built on a single, global storage pool for all data; it does not support the creation of separate disk pools.

C. Purchasing a new FlashBlade appliance is a significant capital expenditure and is unnecessary when the existing array has the capacity and capability.

D. A Non-Disruptive Upgrade (NDU) to a larger model is a costly hardware change that is not required as the current array has ample capacity.

1. Pure Storage Documentation, "Purity//FA File Services Overview": This document states, "Purity File Services extends the industry-leading simplicity and performance of FlashArray to file-based workloads... It provides a unified storage experience, allowing you to run both block and file workloads on the same array." This confirms the technical feasibility of the recommended solution. (Reference available via Pure Storage support portal).

2. Pure Storage White Paper, "FlashArray Architecture": Section "Purity Data Services" describes how Purity provides a rich set of data services, including protocol services for block (iSCSI, FC) and file (NFS, SMB), which operate on a single, global pool of flash storage. This architecture makes the concept of adding a separate disk pool (Option B) invalid.

3. Pure Storage Data Sheet, "FlashArray//X Family": The data sheet specifies that the Purity//FA software provides "Unified Block & File" capabilities, confirming that the hardware platform is designed for this mixed-workload scenario. This supports using the existing array (Option A) over purchasing a new one (Options C and D).