Which two statements describe Pure Storage's Right-Size Guarantee? (Select two.)
Answer : B, C
Pure Storage's Right-Size Guarantee ensures that customers can accurately predict their storage needs based on their workload characteristics. Here's an analysis of the statements:
Correct Statements:
B . Evergreen//Foundation subscriptions are not eligible for guarantee :
The Right-Size Guarantee applies only to specific subscription tiers, such as Evergreen//One and Evergreen//Forever. Evergreen//Foundation, which is a lower-tier subscription, is not eligible for this guarantee.
C . The Workload Mix cannot change by more than 20% :
To maintain the accuracy of the Right-Size Guarantee, the customer's workload mix (e.g., database, VDI, file shares) must remain relatively stable. A significant change in the workload mix (greater than 20%) could invalidate the guarantee, as it affects data reduction ratios and capacity predictions.
Incorrect Statements:
A . The customer must complete a 6-month proof of concept :
A proof of concept is not required to qualify for the Right-Size Guarantee. Instead, the guarantee is based on the initial assessment of the workload and adherence to the terms.
D . Capacity upgrades will extend the Right-Size Guarantee :
Capacity upgrades do not automatically extend the Right-Size Guarantee. The guarantee is tied to the initial assessment and workload stability, not hardware upgrades.
Final Recommendation:
The correct answers are B. Evergreen//Foundation subscriptions are not eligible for guarantee and C. The Workload Mix cannot change by more than 20% .
Pure Storage Right-Size Guarantee Overview :
Pure Storage Right-Size Guarantee
Details the terms and conditions of the Right-Size Guarantee.
Evergreen Subscription Tiers :
Pure Storage Evergreen Subscriptions
Explains the differences between Evergreen subscription tiers.
Refer to the exhibit.

A customer is assessing the health of their FlashArray.
What should the customer discuss with their SE based on this information?
Answer : B
Based on the exhibit (referenced via the link), the customer should discuss adding a second shelf of NVMe DirectFlash modules with their SE. This recommendation is based on the assumption that the exhibit indicates the array is nearing its capacity limits or requires additional storage to accommodate future growth.
Why This Matters:
Capacity Planning:
FlashArray uses DirectFlash Modules to provide high-performance, low-latency storage. If the array is approaching its physical capacity, adding a second shelf of NVMe modules is the most effective way to expand storage without requiring a full hardware upgrade.
This approach ensures the array can continue to meet the customer's growing storage needs while maintaining performance and reliability.
Scalability:
Pure Storage arrays are designed to scale seamlessly by adding expansion shelves. This allows customers to increase capacity without disrupting operations or replacing existing hardware.
Why Not the Other Options?
A . Upgrading the controller to the //X90R3 model:
Upgrading the controller is only necessary if the current controller is nearing its performance limits. The exhibit does not indicate performance bottlenecks, so this step is likely unnecessary.
C . Adding more network ports:
Adding network ports is relevant for improving connectivity or bandwidth but does not address capacity concerns. If the array is running out of storage space, adding network ports will not resolve the issue.
Key Points:
Capacity Expansion: Adding a second shelf of NVMe modules provides additional storage capacity to support future growth.
Non-Disruptive Scaling: Expansion shelves can be added without downtime, ensuring continuous availability.
Cost Efficiency: Avoids unnecessary upgrades or replacements, optimizing costs while meeting capacity requirements.
Pure Storage FlashArray Documentation: 'Expanding FlashArray Capacity with DirectFlash Modules'
Pure Storage Whitepaper: 'Scaling Storage with FlashArray Expansion Shelves'
Pure Storage Knowledge Base: 'Best Practices for Capacity Planning and Expansion'
What causes a disruption to Pure FlashArray stateless controller operations or performance, if there is a single array?
Answer : B
Among the listed options, physically relocating an array is the action most likely to cause a disruption to Pure FlashArray stateless controller operations or performance.
Why This Matters:
Physical Relocation:
Moving a FlashArray involves powering down the system, disconnecting cables, and transporting the hardware to a new location. This process inherently disrupts operations and performance until the array is reinstalled and brought back online.
Even with proper planning, physical relocation introduces downtime and potential risks (e.g., hardware damage during transport).
Why Not the Other Options?
A . Replacing a controller I/O module:
FlashArray controllers are designed with redundancy and hot-swappable components. Replacing an I/O module typically does not cause significant disruptions, as the other controller continues to handle operations.
C . Moving from a SAS- to NVMe-based shelf:
Transitioning to NVMe-based shelves is a planned upgrade that does not inherently disrupt operations. The array can continue functioning during the transition, though performance may vary temporarily.
D . Upgrade Purity//FA code:
Upgrading Purity//FA (the operating system for FlashArray) is a non-disruptive process. FlashArray supports rolling upgrades, ensuring continuous availability and performance during the update.
Key Points:
Physical Relocation: Causes unavoidable downtime and operational disruption.
Redundancy and Non-Disruptive Operations: FlashArray is designed to minimize disruptions for tasks like module replacement and software upgrades.
Planning Required: Physical relocation requires careful planning to minimize risks and downtime.
Pure Storage FlashArray Documentation: 'Maintenance and Relocation Best Practices'
Pure Storage Whitepaper: 'Non-Disruptive Operations with FlashArray'
Pure Storage Knowledge Base: 'Minimizing Disruptions During Array Maintenance'
A customer wants to add capacity to support a new Oracle workload. It has been determined that the application needs 398 TB of thick-provisioned storage from the host. The customer wants to purchase the minimum storage capacity to handle this workload.
How much capacity should the SE propose, assuming DRR is 3:1?
Answer : A
To calculate the minimum storage capacity required to handle the Oracle workload, we need to account for the thick-provisioned storage requirement and the expected data reduction ratio (DRR).
Step-by-Step Calculation:
Logical Storage Requirement :
The application requires 398 TB of thick-provisioned storage from the host.
Data Reduction Ratio (DRR) :
The DRR is 3:1 , meaning the physical storage required is:

Recommendation :
The SE should propose 132 TB of physical storage, as it meets the requirement after accounting for data reduction.
Final Recommendation:
The correct answer is A. 132 TB .
Capacity Planning Guide :
Pure Storage Capacity Planning
Provides guidance on calculating usable capacity based on data reduction ratios.
Thick vs. Thin Provisioning :
Explains the differences between thick and thin provisioning.
Which offering discounts controller upgrades with a purchase of qualifying storage capacity?
Answer : A
The offering that discounts controller upgrades with a purchase of qualifying storage capacity is Love Your Storage .
Why This Matters:
Love Your Storage:
This program is part of Pure Storage's Evergreen//Forever subscription model. It allows customers to upgrade their controllers at a discounted rate when they purchase additional qualifying storage capacity.
The goal is to ensure that customers can modernize their infrastructure without incurring excessive costs, aligning with Pure Storage's commitment to providing flexible and future-proof solutions.
Why Not the Other Options?
B . Right-Size Guarantee:
The Right-Size Guarantee allows customers to trade in existing shelves for higher-capacity ones while only paying for the incremental capacity increase. It does not involve discounts on controller upgrades.
C . Capacity Consolidation:
Capacity Consolidation refers to the ability to consolidate workloads onto fewer arrays or shelves but does not include discounts on controller upgrades.
D . Ever Agile:
Ever Agile is a subscription model that provides flexibility in scaling storage and compute resources but does not specifically discount controller upgrades tied to storage purchases.
Key Points:
Love Your Storage: Discounts controller upgrades when purchasing qualifying storage capacity.
Evergreen Benefits: Ensures customers can modernize their infrastructure cost-effectively.
Future-Proofing: Aligns with Pure Storage's commitment to delivering long-term value.
Pure Storage Evergreen//Forever Documentation: 'Understanding Love Your Storage'
Pure Storage Whitepaper: 'Maximizing Value with Evergreen Subscriptions'
Pure Storage Knowledge Base: 'How Love Your Storage Works'
A customer is unsatisfied because the level of data reduction on their FlashArray is NOT as high as expected. What two statements should the SE make to the customer? (Choose two.)
Answer : B, D
If a customer is unsatisfied with the level of data reduction on their FlashArray, the SE should make the following two statements:
FlashArray's deduplication effectiveness will usually increase as the data quantity grows:
Deduplication relies on identifying and eliminating duplicate data blocks. As more data is written to the array, the likelihood of finding duplicates increases, improving the overall deduplication ratio.
Customers should expect better data reduction results over time as their dataset grows.
The Right-Size Guarantee means that the customer can work with their SE if necessary:
Pure Storage's Right-Size Guarantee ensures that customers receive the expected effective capacity based on their workload's data reduction profile. If the actual data reduction does not meet expectations, the customer can collaborate with their SE to address the issue and potentially adjust their subscription or configuration.
Why Not the Other Options?
A . A FlashArray's compression and deduplication will need to be tuned for data subsets:
FlashArray's data reduction techniques (compression and deduplication) are automatic and do not require manual tuning. This statement is misleading.
C . FlashArray data reduction needs to be tuned to increase its effectiveness:
Similar to Option A, FlashArray's data reduction mechanisms are fully automated and do not require manual intervention.
Key Points:
Data Growth: Deduplication effectiveness improves as more data is written to the array.
Right-Size Guarantee: Provides assurance that customers can work with their SE to address data reduction concerns.
Automatic Optimization: FlashArray's data reduction features are self-optimizing and do not require manual tuning.
Pure Storage FlashArray Documentation: 'Understanding Data Reduction and Capacity Planning'
Pure Storage Whitepaper: 'Maximizing Data Reduction with FlashArray'
Pure Storage Knowledge Base: 'Right-Size Guarantee Terms and Conditions'
A customer has two data centers: one in North America and one in England. The customer wants to replicate their production data across data centers, with as low an RPO as possible.
What Pure Storage feature meets their requirements?
Answer : B
The customer wants to replicate production data across two data centers (North America and England) with as low an RPO as possible . The best Pure Storage feature to meet this requirement is ActiveDR .
Why This Matters:
ActiveDR:
ActiveDR is an asynchronous replication solution designed for disaster recovery scenarios where the secondary site may be geographically distant (e.g., across continents).
It provides low RPOs , typically in the range of seconds to minutes , depending on network conditions and workload characteristics.
ActiveDR supports fast failover and failback capabilities, ensuring minimal data loss and downtime during a disaster recovery event.
Why Not the Other Options?
A . ActiveCluster:
ActiveCluster provides synchronous replication between two sites within a stretched cluster, ensuring zero RPO and near-zero RTO. However, it requires both sites to be within a low-latency range (typically <10 ms). Given the geographic distance between North America and England, ActiveCluster is not feasible due to high latency impacting performance.
C . Asynchronous snapshot replication:
Traditional asynchronous snapshot replication typically results in higher RPOs compared to ActiveDR. It does not provide the same level of optimization for low RPOs as ActiveDR.
Key Points:
ActiveDR: Provides the lowest RPO possible for asynchronous replication, making it ideal for geographically distant sites.
Network Latency: ActiveDR is designed to work efficiently over longer distances and higher latencies compared to synchronous solutions like ActiveCluster.
Disaster Recovery: Ensures protection against site failures with minimal data loss and downtime.
Pure Storage FlashArray Documentation: 'ActiveDR for Disaster Recovery'
Pure Storage Whitepaper: 'Meeting RPO and RTO Requirements with FlashArray'
Pure Storage Knowledge Base: 'Choosing the Right Replication Solution for High Latency'