Facing rapid data expansion due to diverse scientific resear…

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?

Scenario Overview:An existing Customer is adding a new workl…

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 customer is modernizing its distributed…

Scenario Overview:A customer is modernizing its distributed Enterprise Resource Planning (ERP) system environment that supports operations across multiple North American regions. The current storage landscape includes read-heavy workloads located at core sites and smaller replication workloads at regional offices. The company is moving to a subscription-based storage model to simplify infrastructure management and reduce upfront costs.The IT team has shared current performance and capacity requirements, and they expect the solution to handle read-intensive transactional loads, and provide replication between select sites for resilience. Site performance fluctuates with project lifecycles. No Pure-based replication (ActiveDR, ActiveCluster, or async) will be implemented. Workloads will be hosted on multiple sites as identified in the scenario above. You have been asked to determine a right-sized Pure Storage FlashArray configuration that meets both performance and capacity needs while accounting for: 5% yearly growth for core sites and 3% yearly growth for regional offices Read-intensive workload profiles with 32KiB average IO size Lightweight replication at secondary sites Workload-specific data reduction estimates using Sizer guidance Customer Requirements: Workload 1 (Site 1) – ERP:Dataset size: 85.49 TiBEstimated average read IOPS: 30,000Estimated read bandwidth: 937.5 MiB/sExpected DRR: 2.8Workload 2 (Site 2) – ERP:Dataset size: 97.32 TiBEstimated average read IOPS: 30,000Estimated read bandwidth: 937.5 MiB/sExpected DRR: 2.8Workload 3 (Site 3) – Replication (S1 Replication):Dataset size: 203.73 TiBEstimated average read IOPS: 2,000Estimated read bandwidth: 62.5 MiB/sExpected DRR: 1.2Workload 4 (Site 4) – Replication (S2 Replication):Dataset size: 215.55 TiBEstimated average read IOPS: 2,000Estimated read bandwidth: 62.5 MiB/sExpected DRR: 1.2Candidate Instructions:Using Sizer, identify the “Evergreen//One” section of the Results tab, taking note of the Minimum Quote Recommendation, sizing inputs, and SLA guarantee. Please answer the following questions for Site 2 (Workload 2).In the box below, paste in the Tier for Site 2 (Workload 2).Example answer format: //Unified Block & File – CapacityIn the box below, paste in the EUC Reserve(TiB) for Site 2 (Workload 2).Example answer format: 150.08Be 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 N…

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”.

An educational institution has implemented SafeMode on their…

An educational institution has implemented SafeMode on their FlashArray to protect research data. Their policy mandates offline storage of systems compromised by malware, eliminating them from recovery use. What additional step is needed for enhanced malware protection and quick data access without using compromised systems?