FAAA_004 Practice Questions

The Pure Storage "Love Your Storage Guarantee" is a core component of the Evergreen//Forever™ subscription program. It provides customers with investment protection by allowing them to return their FlashArray™ or FlashBlade® system for a full refund if they are not satisfied. The official terms of this guarantee explicitly define the return window as 30 days, starting from the date of shipment. This policy underscores the company's confidence in its product performance and customer satisfaction, offering a risk-free trial period for new hardware deployments.

A. 15 days is an incorrect duration; the official guarantee provides a longer, 30-day evaluation period.

C. 60 days is double the actual return window specified in the official program terms.

D. 90 days is three times the length of the actual return window and is not offered.

1. Pure Storage Official Website, Evergreen//Forever™ Program Page: Under the section "Love Your Storage Guarantee," the terms are stated: "If you’re not happy with your Pure Storage array, you can return it within 30 days." This is the primary source defining the program's return window. (Accessed via the main Pure Storage corporate website under Solutions > Evergreen Storage).

2. Pure Storage Evergreen Storage Datasheet: This document details the components of the Evergreen program, including the "Love Your Storage Guarantee," and specifies the "30-day, no-questions-asked, money-back guarantee." (Document reference: PS-DS-EVERGREEN-0522-V10).

The Purity//FA operating environment uses an inline, five-stage data reduction process. When a write request is received, Purity generates a high-fidelity hash for the variable-sized data block. This hash is checked against an in-memory hash table. If a matching hash is found, it indicates a potential duplicate. To guarantee data integrity and prevent data loss from the rare possibility of a hash collision (where two different blocks produce the same hash), Purity performs a definitive byte-for-byte comparison between the new block and the existing block already stored on flash. Only after this comparison confirms the blocks are identical is the new block discarded and the metadata updated.

A. The next incoming block is then hashed to see if it can be deduplicated.

This is incorrect. The system must complete the verification process for the current block before proceeding to the next one in the I/O stream.

B. Deep level compression is then applied to the newly hashed block.

This is incorrect. Compression is applied to unique data blocks after the deduplication check and before they are written to flash, not to a block that is a potential duplicate.

D. Purity//FA will expand the block to see if it can deduplicate a larger dataset.

This is incorrect. "Expanding the block" is not a function of the Purity//FA deduplication engine; the system works to reduce, not expand, data.

1. Pure Storage FlashArray Architecture White Paper. In the section describing the Purity//FA write path and data reduction, the process is detailed. It explicitly states that after a hash match, a direct comparison of the data blocks is performed to verify a true duplicate before discarding the incoming data. This step is crucial for ensuring data integrity. (Typically found in sections titled "Purity Data Reduction" or "Write I/O Path").

2. Pure Storage Technical Report, "An Inside Look at the Purity FlashArray Operating Environment". This document outlines the stages of data reduction. Stage 2 is "High-performance inline deduplication." The description of this stage clarifies that a hash hit triggers a read of the original data block for a bit-for-bit comparison to confirm the duplicate, thereby preventing hash collisions from causing data corruption. (Refer to the section on "The Five Stages of Data Reduction").

The FlashArray architecture is fundamentally designed for non-disruptive operations, including upgrades. This is achieved through its dual-active, stateless controller design. During a software or hardware upgrade, one controller is taken offline and updated while the other seamlessly continues to service all I/O operations. Once the first controller is updated and brought back online, a transparent failover occurs, and the process is repeated on the second controller. This entire procedure happens without any downtime, manual intervention for multipathing, or degradation in storage performance, ensuring continuous data availability and application performance.

A. ActiveCluster: This is a business continuity feature for synchronous replication and active-active clustering between two arrays, not the mechanism for performing upgrades on a single array.

C. Right-Size Guarantee: This is a commercial program that guarantees a specific amount of effective storage capacity, not a technical feature related to the upgrade process.

D. Protection groups: These are logical constructs used to apply consistent data protection policies (like snapshot and replication schedules) to a group of volumes.

1. Pure Storage, Inc. (2020). A Look Inside the Pure Storage FlashArray//X Family.

Page 4, Section: "Non-Disruptive Upgrades": "The FlashArray was designed from the ground up to enable non-disruptive upgrades of both software and hardware... Controller hardware upgrades are also non-disruptive. Customers can upgrade to the latest-generation controllers by swapping them one at a time, while the array continues to service I/O."

2. Pure Storage, Inc. (2023). FlashArray Best Practices & Implementation Guide for VMware vSphere.

Page 10, Section: "Non-Disruptive Upgrades and Maintenance": "All tasks, from software updates to capacity and performance expansion, and even generational hardware refreshes, can be performed without downtime or noticeable performance impact."

3. Pure Storage, Inc. (2022). ActiveCluster Technical Overview.

Page 3, Section: "Introduction": This document defines ActiveCluster as a "multi-site active/active stretch cluster solution that provides new levels of availability for the enterprise," confirming its purpose is business continuity, not upgrades.

4. Pure Storage, Inc. (2023). Purity//FA User Guide.

Section: "Protection > Protection Groups": This section details the creation and management of protection groups for the sole purpose of "applying snapshot and replication schedules" to volumes and hosts.

The minimum useable capacity required on the FlashArray is the physical space needed after data reduction is applied to the logical data. This is calculated by dividing the logical data size by its corresponding data reduction ratio for each workload and then summing the results.

Oracle: 100 TiB (logical) / 4 (ratio) = 25 TiB (physical)

VDI: 200 TiB (logical) / 5 (ratio) = 40 TiB (physical)

The total minimum useable capacity is the sum of the physical capacity required for both workloads:

25 TiB + 40 TiB = 65 TiB.

A. 40TiB: This value represents the physical capacity required for the VDI workload only (200 TiB / 5), incorrectly omitting the capacity needed for the Oracle data.

C. 300TiB: This is the total logical capacity (100 TiB + 200 TiB) before applying any data reduction, not the required physical (useable) capacity.

D. 750TiB: This value is the result of an incorrect calculation and does not represent either the logical or the required physical capacity based on the provided ratios.

1. Pure Storage, "Purity//FA Architecture White Paper": This document explains the core data reduction technologies within the Purity Operating Environment. The concept of the Total Data Reduction ratio is defined as the ratio of logical user data stored to the physical flash space consumed. The calculation in the explanation directly applies this principle. (See section: "Purity Reduce").

2. Pure Storage, "FlashArray Best Practices for Oracle Database": This guide discusses typical data reduction rates for Oracle workloads, validating the concept of applying a specific ratio (like the 4:1 given in the question) to determine physical capacity needs from a logical data size. (See section: "Capacity Savings with FlashArray").

3. Pure Storage, "Sizing with Confidence" Technical Brief: This document outlines the methodology for sizing a FlashArray. It emphasizes calculating the required physical capacity by applying expected data reduction ratios to the source logical data sizes, which is the exact procedure required to solve the question. (See section: "Calculating Total Reduction").

The FlashArray//X architecture is fundamentally designed around a modular, common chassis that supports multiple generations of controllers. This design is a core tenet of Pure Storage's Evergreen architecture. When upgrading from an //XR2 to an //XR3 model, the existing 3U chassis, power supplies, and flash modules remain in place. The upgrade is performed by non-disruptively swapping the older //XR2 controller modules with the new //XR3 modules, one at a time. This eliminates the need for a "forklift" upgrade or data migration, dramatically simplifying the process both physically and logically.

B. InfiniBand connectivity between controllers: This is the high-speed internal interconnect for high availability in all modern FlashArray models; it is not a specific design choice that simplifies the upgrade between generations.

C. NVRAM modules in both controllers: NVRAM is a standard, critical component for write caching and power-loss protection in all FlashArray controllers, not an architectural feature that simplifies the physical upgrade process.

D. Re-use of existing HBAs to prevent WWN changes: Host Bus Adapters (HBAs) are integrated components of the controller module. Therefore, they are replaced during a controller upgrade, not re-used. The Purity software manages WWN persistence to minimize host-side changes.

1. Pure Storage, Inc. (2021). FlashArray//X Hardware Guide. Section: "FlashArray//X Chassis". This guide details the common 3U chassis used across different //X generations (R2, R3, R4), illustrating that the chassis is a persistent component while controllers are modular and swappable. The upgrade path relies on this shared physical platform.

2. Pure Storage, Inc. (2022). White Paper: An Introduction to Evergreen Storage. Page 4, Section: "Upgrade Flex". This document explicitly states, "With Upgrade Flex, you can modernize your controllers to the latest generation, any time, within the same chassis. This means no downtime, no performance impact, and no data migration." This directly supports the concept of a common chassis simplifying controller upgrades.

The customer requires a disaster recovery (DR) solution with failover and fallback capabilities between their on-premises data center and the public cloud. Pure Storage Cloud Block Store (CBS) is a software-defined version of the Purity//FA operating environment that runs natively in AWS and Azure. It can act as a replication target for an on-premise FlashArray. Using asynchronous snapshot replication, customers can replicate data to CBS, enabling the cloud to serve as a fully functional DR site. This configuration directly supports failing over operations to the cloud and subsequently failing back to the on-premises array once it is restored.

B. Purity//FA CloudSnap periodic offload of snapshots to AWS: CloudSnap is designed for cost-effective, long-term data retention and archival by sending snapshots to cloud object storage (e.g., S3), not for rapid DR with low RTO.

C. ActiveCluster FC replication between a FlashArray on site and Evergreen//One: ActiveCluster is a synchronous, active-active replication solution for business continuity (zero RPO/RTO), not typically used for long-distance on-prem-to-cloud DR. Also, FC is not the transport for cloud replication.

1. Pure Storage Official Documentation, "Disaster Recovery to the Cloud with Pure Cloud Block Store" Solution Brief.

Reference: Page 2, "Solution Overview" section states, "Pure Cloud Block Store™ enables disaster recovery (DR) to the cloud by providing seamless data mobility between on-premises FlashArray™ devices and the public cloud... You can use asynchronous replication to fail over to the cloud and fail back to on-premises when ready." This directly supports using snapshot replication between FlashArray and CBS for DR.

2. Pure Storage Official Documentation, "Purity//FA User Guide".

Reference: In the section on "Protection," CloudSnap is described as a feature to "offload snapshots to a cloud namespace for archival purposes." This differentiates its use case from the active DR scenario required by the question.

3. Pure Storage Official Documentation, "ActiveCluster" White Paper.

Reference: The "Overview" section describes ActiveCluster as a "multi-site active-active stretch cluster solution that provides synchronous replication." This confirms it is for business continuity with zero recovery time, a different use case than DR to the cloud, and it typically uses Fibre Channel or IP for shorter, metro distances.

The Ever Agile program, a component of Pure Storage's Evergreen//Forever™ subscription, provides customers with a trade-in credit for their existing controllers when they choose to upgrade to newer, more powerful models. This upgrade is not restricted to a fixed timeline and is often performed when a customer expands their storage capacity. By purchasing additional capacity, a customer might also need more powerful controllers to manage the increased workload and performance demands. The Ever Agile program facilitates this by offering a credit (a discount) on the new controllers, directly linking the controller upgrade to the evolving needs of the storage environment, which frequently includes capacity expansion.

A. Love Your Storage: This is a 30-day satisfaction guarantee that allows customers to return the array if they are not satisfied; it is not a hardware upgrade program.

B. Right-Size Guarantee: This program guarantees a specific amount of effective capacity for a customer's workload, addressing capacity planning and assurance, not controller discounts.

C. Capacity Consolidation: This program focuses on upgrading the storage media (flash modules) to newer, denser versions and provides trade-in credit for the old media, not the controllers.

1. Pure Storage Official Documentation, "Evergreen//Forever Subscription Datasheet": This document explicitly details the components of the Evergreen subscription.

Section: Ever Agile: "Upgrade your controllers to any larger model within the product family, or to the next generation, whenever you want. You’ll receive a trade-in credit for your existing controllers, which you can apply to the upgrade." This confirms that Ever Agile provides the discount (trade-in credit) for controller upgrades.

Section: Love Your Storage Guarantee: "We’re so confident you’ll love your Pure Storage experience that we’re backing it with a 30-day money-back guarantee." This defines it as a satisfaction guarantee, distinct from hardware upgrades.

2. Pure Storage Official Documentation, "The Pure Storage Evergreen™ Architecture" White Paper: This white paper provides an architectural overview of the Evergreen model.

Page 5, "Upgrade Flex and Ever Agile": The document explains that Ever Agile allows for flexible, on-demand controller upgrades with trade-in credits. It contrasts this with the time-based "Free Every Three" program, highlighting that Ever Agile is for upgrades driven by changing business needs, such as performance requirements from capacity growth.

3. Pure Storage Official Blog, "Evergreen Storage: The Subscription That Keeps Getting Better": Blog posts from official sources often clarify program benefits.

This post details the value proposition, stating, "With our Ever Agile program, you can upgrade your controllers at any time and receive full trade-in credit for your existing hardware." This reinforces the mechanism of discounting controller upgrades through trade-in credits.

The exhibit displays the rear of a FlashArray chassis with two controllers. The top controller is physically labeled CT1, and the bottom controller is labeled CT0. This is the standard hardware configuration.

While Option C incorrectly reverses the positions of the controllers, it is the only option that correctly identifies the two controllers by their designated names (CT0 and CT1). The other options are fundamentally incorrect: Option A introduces a non-existent controller (CT2), and Option B refers to logical roles instead of the physical labels shown. Therefore, Option C is the most plausible intended answer, despite the positional error in its description.

A. Top: CT1, Bottom: CT2

This is incorrect because FlashArray systems use controllers designated CT0 and CT1. A controller labeled CT2 does not exist in this architecture.

B. Top: Primary, Bottom: Secondary

This is incorrect because "Primary" and "Secondary" describe the logical, high-availability roles of the controllers, not the physical hardware labels shown in the exhibit.

1. Pure Storage, Inc. (2023). FlashArray//X R4 Hardware Guide.

Reference: Page 12, Figure 4, "FlashArray//X R4 Chassis Rear View". The diagram explicitly shows the bottom controller slot as "Controller 0 (CT0)" and the top controller slot as "Controller 1 (CT1)". This official document confirms the standard physical layout seen in the exhibit.

2. Pure Storage, Inc. (2023). FlashArray//C R4 Hardware Guide.

Reference: Page 12, Figure 4, "FlashArray//C R4 Chassis Rear View". This guide for a different FlashArray model also confirms the consistent labeling and positioning convention: CT0 is the bottom controller and CT1 is the top controller. This validates that the information in the exhibit is standard across the product line.

Pure Storage's Right-Size Guarantee is a written assurance to the customer that they will receive a specific amount of effective capacity for their intended workload. Pure calculates this based on a pre-agreed data reduction rate. If the array fails to deliver the guaranteed effective capacity during the first year, Pure Storage will provide the necessary additional flash storage to meet the guaranteed capacity at no cost. This program is designed to eliminate the customer's risk associated with capacity planning and sizing an all-flash array.

A. The performance of the FlashArray model is incorrect. The Right-Size Guarantee is focused on storage capacity, not performance metrics like IOPS, throughput, or latency.

C. The Data Reduction Rate by workload is incorrect. While a data reduction rate is guaranteed, it is the mechanism used to deliver the ultimate promise, which is the final effective capacity.

D. The customer's Total Efficiency Ratio is incorrect. Total Efficiency is a broader metric that includes thin provisioning. The guarantee is specifically on the effective capacity achieved through data reduction.

1. Pure Storage, Inc. (2023). FlashArray//X Datasheet.

Reference: Page 2, under "Evergreen Storage" section. The document states, "Get a written guarantee of effective capacity with our Right-Size Guarantee." This directly supports that the promise is for effective capacity.

2. Pure Storage, Inc. (2022). Why Pure Storage for Mission-Critical Applications White Paper.

Reference: Page 5, Section "Right-Size Guarantee". The text reads: "The Right-Size Guarantee provides a guaranteed effective capacity in writing. If we don’t meet the guarantee, we’ll make it right with free flash, as-needed." This explicitly confirms the guarantee is on effective capacity.

3. Pure Storage, Inc. (n.d.). Right-Size Guarantee. Official Web Page.

Reference: The main headline and description state: "The Right-Size Guarantee ensures you’ll get the effective capacity you need, with a written guarantee of your data reduction rate for your specific workload." This shows that while the data reduction rate is part of the agreement, the primary promise and outcome for the customer is the effective capacity.

Portworx by Pure Storage is the company's strategic, enterprise-grade Kubernetes Data Services Platform. It is specifically designed to provide a rich, software-defined storage layer for cloud-native applications. Portworx delivers essential services beyond basic storage provisioning, including high availability, application-aware data protection, disaster recovery, data security, and automated capacity management. While a direct CSI driver exists, Portworx represents Pure's most comprehensive and feature-rich solution, making the FlashArray platform highly suitable for running mission-critical, stateful applications in containerized environments.

A. This is incorrect. Pure Storage provides robust, first-class support for Kubernetes and containerized workloads on FlashArray through multiple integration methods.

B. While a CSI (Container Storage Interface) provider for FlashArray does exist, it offers foundational persistent volume provisioning. It is less comprehensive than the Portworx platform, which provides the advanced data services typically required by enterprise cloud-native applications.

D. This is incorrect. FlashArray is a SAN (Storage Area Network) device, not DAS (Direct-Attached Storage). The statement misrepresents the storage architecture.

1. Portworx by Pure Storage, "The Kubernetes Data Services Platform": The official product documentation describes Portworx as the solution for running mission-critical applications on Kubernetes, highlighting features like PX-DR for disaster recovery and PX-Secure for security, which are not inherent to a basic CSI driver. (Source: Portworx by Pure Storage official website, "Products" section).

2. Pure Storage Blog, "Portworx vs. CSI: What’s the Difference?": This official source explicitly contrasts the two technologies. It states, "While CSI drivers are great for providing basic connectivity between external storage systems and Kubernetes, they lack the enterprise features that organizations need to run mission-critical stateful applications in production... Portworx provides a whole host of enterprise data services..." This supports why Portworx (C) is a more complete answer than the CSI provider (B) for a "cloud-native application." (Source: Pure Storage Official Blog).

3. Pure Storage, "Pure Service Orchestrator" Documentation: The documentation for Pure's CSI driver details its function as providing "storage-as-a-service" by connecting Kubernetes to FlashArray and FlashBlade. This confirms the existence of the CSI driver (making option B technically plausible but incomplete) but also frames its capabilities around provisioning, which is a subset of the Portworx platform's functionality. (Source: Pure Storage technical documentation for the Pure CSI Driver).