A customer using Evergreen//Foundation wants to consolidate their 48.2TB DFMs into 75TB DFMs for rack space efficiency, but they are unable to use the standard Capacity Consolidation process.   What is the reason for this?

Scenario Overview:An existing Customer is adding a new workload for Archive in their Block Storage estate. They require a new array that will provide the most cost effective approach for this workload.You have been asked to determine a Pure FlashArray configuration that meets both performance and capacity needs while accounting for: Estimating a 2% annual growth rate7-day retention period for snapshotsSnapshot change rate of 1%3-year storage growth  Use the most economical FlashArray modelYour job is to use Pure Storage’s FlashArray Sizer to recommend the most appropriate Capex configuration.Customer Requirements:Workload – Archive (Block): Dataset size: 2,900 TiB2.1 : 1 Data Reduction rate Estimated average read IOPS: 15,000 Estimated read bandwidth: 468.75 MiB/s Candidate Instructions:Using Sizer, set the DRR to Expected. Then, identify the “Recommended CapEx Array” configuration, making sure that it meets required customer needs, including required effective capacity and expected IOPS, etc.In the box below, paste in “Recommended CapEx Array” configuration that is highlighted as “Best Fit” in FlashArray Sizer.Example answer format: C20 | 148TB | 8×18.6TB Be sure to check your work before you submit. You will NOT be able to return to this page after you click “Next”.

Scenario Overview:A prospective customer is looking for an NFS based storage platform that can cater for scale out operations. They are concerned with metadata operations and need something that will handle thousands of concurrent connections. Cost is important but the performance needs are the priority.The customer has provided estimates of workload size and current performance expectation, but they are relying on you to project the solution sizing based on the supplied variables. Sizing variables: Estimating a 5% annual growth rate14-day retention period for snapshotsDaily snapshot change rate of 1%5-year storage growthYour job is to use Pure Storage’s Sizer to recommend the most appropriate traditional purchase configuration.Customer Requirements:Workload – Distributed CMS (NFS): Dataset size: 981 TiBCompressible dataEstimated average read IOPS: 150,000Estimated read bandwidth: 2.6 GiB/s  Estimated average write IOPS: 35,000 Estimated write IO Size: 16 KiB Candidate Instructions:Use Sizer. Then, identify a configuration making sure that it meets required customer needs, including required effective capacity and expected IOPS, etc. The solution should be the most inexpensive entry point for this workload while staying under 100% Capacity Fullness.In the box below, paste in “Recommended CapEx Array” configuration that is highlighted as “Best Fit” in FlashArray Sizer.Example answer format: S500R2 | 525TB | 37DFMC | 1C | 7B2D-37.5TB Be sure to check your work before you submit. You will NOT be able to return to this page after you click “Next”.

When solutioning for Evergreen//One, why is it inappropriate to use the total projected EUC as the initial Reserve Commit?

With aerobic training, the lactate threshold moves up to a higher % VO2max.   

An existing customer needs to expand capacity and performance. The SE must provide a baseline Evergreen//One configuration with service tier alignment using common workload assumptions.   Which tool is best suited for this situation?

Which unique benefit of Evergreen//Flex would allow customers to redistribute storage capacity between their arrays and locations?

”   During discovery, a customer shares that they track depreciation over a seven-year asset lifecycle and have security protocols that require them to physically own infrastructure. However, their CIO wants adopt a consumption-based model. Which subscription model allows Pure Storage to meet the CIO’s goals while meeting asset ownership requirements? “

Facing rapid data expansion due to diverse scientific research projects, a research institution seeks a scalable storage solution that upholds data integrity and enables swift access for both current and future initiatives.   How can FlashArray meet the institution’s needs for an expandable, dependable, and readily accessible storage system?

A customer with an Evergreen//Foundation subscription is evaluating upgrade options. They want to: Upgrade controllers non-disruptively as performance needs grow Avoid overprovisioning while maintaining predictable budget planning Adjust storage purchases over time as requirements evolve What should the SE recommend to support these goals?