FAAA_004 Pure Storage FlashArray Architect Associate Free Practice Exam Questions (2025 Updated)

Given that the two FlashArrays are located in different data centers with a network link latency of35 ms, the best Purity feature to provide protection against a site failure with thelowest recovery pointisActiveDR.

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., >10 ms latency).

It provides low RPOs (typically seconds to minutes) and supports fast failover and failback capabilities, ensuring minimal data loss and downtime.

With a 35 ms latency between sites, synchronous replication (e.g., ActiveCluster) is not feasible due to the high latency impacting performance.

Why Not the Other Options?

A. ActiveCluster:

ActiveCluster requires synchronous replication, which is only suitable for sites within a low-latency range (<10 ms). At 35 ms latency, ActiveCluster would cause significant performance degradation.

C. Snapshot replication:

Snapshot replication is asynchronous but does not provide the same level of failover and failback capabilities as ActiveDR. It is better suited for backup purposes rather than disaster recovery with low RPOs.

D. Local snapshots:

Local snapshots are useful for point-in-time recovery within a single array but do not protect against site failures.

Key Points:

ActiveDR:Ideal for asynchronous replication with low RPOs and fast failover/failback.

Latency Considerations:ActiveDR supports higher latencies (e.g., 35 ms) compared to synchronous solutions like ActiveCluster.

Disaster Recovery:Ensures protection against site failures with minimal data loss and downtime.

References:

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"

During acontroller upgradeof a Pure Storage FlashArray, theactive/active controller architectureensures there will be no tangible impact on performance. This design allows both controllers to handle I/O operations simultaneously, so even if one controller is being upgraded, the other can continue processing workloads without interruption.

Why This Matters:

Active/Active Architecture:In an active/active design, both controllers share the workload equally. If one controller is taken offline for maintenance or upgrades, the remaining controller seamlessly handles all I/O operations.

This ensures continuous availability and consistent performance during upgrades, minimizing downtime and user impact.

Why Not the Other Options?

B. Stateful controller architecture:

While stateful architectures maintain session information, they do not inherently ensure no performance impact during upgrades. The key factor here is the active/active design.

C. Active/passive controller front-end ports:

In an active/passive design, only one controller is actively handling I/O at any given time. If the active controller is upgraded, the passive controller must take over, which can lead to temporary performance degradation.

D. Primary/secondary controller architecture:

Similar to active/passive, this design relies on a primary controller for all operations, making it less resilient during upgrades compared to active/active.

Key Points:

Active/Active Design:Ensures continuous I/O processing during upgrades.

Seamless Upgrades:Minimizes performance impact and downtime for users.

High Availability:Maintains consistent performance and reliability throughout the upgrade process.

References:

Pure Storage FlashArray Documentation: "Controller Upgrade Process and Best Practices"

Pure Storage Whitepaper: "Active/Active Controller Architecture"

Pure Storage Knowledge Base: "Minimizing Impact During Controller Upgrades"

When customers leverage theEvergreen//One offering, billing is based on theeffective capacity consumed.

Why This Matters:

Effective Capacity Consumed:

Evergreen//One is a subscription-based model where customers pay for thelogical capacity they consumeafter applying data reduction techniques like deduplication, compression, and pattern removal.

This ensures customers only pay for the actual usable capacity they need, aligning with Pure Storage's commitment to delivering predictable and cost-effective storage solutions.

Why Not the Other Options?

A. Total capacity installed:

Billing is not based on the total raw capacity installed in the array, as this does not reflect the actual usable capacity after data reduction.

B. Raw capacity consumed:

Raw capacity refers to the physical storage used before applying data reduction. Evergreen//One focuses on effective capacity, not raw capacity.

D. Capacity provisioned to hosts:

Provisioned capacity refers to the logical space allocated to hosts, which may include unused or overprovisioned space. Billing is based on the actual consumed capacity.

Key Points:

Effective Capacity:Reflects the logical capacity consumed after data reduction.

Subscription Model:Aligns with Evergreen//One's focus on predictable and flexible billing.

Data Reduction:Deduplication, compression, and pattern removal optimize storage efficiency, reducing costs for customers.

References:

Pure Storage Evergreen//One Documentation: "Understanding Billing Metrics"

Pure Storage Whitepaper: "Maximizing Value with Evergreen Subscriptions"

Pure Storage Knowledge Base: "How Evergreen//One Billing Works"

The offering thatdiscounts controller upgrades with a purchase of qualifying storage capacityisLove 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.

References:

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"

The customer currently has aFlashArray//Xwith 40 TB of available block storage and needs to add 10 TB of file workloads while minimizing infrastructure costs. Let's analyze the options:

Analysis of Options:

A. Run both workloads on the current FlashArray:

Pure Storage FlashArray supports both block and file workloads using thePurity File Servicesfeature, which allows customers to run file workloads directly on their FlashArray.

Since the FlashArray already has 40 TB of available storage, adding 10 TB of file workloads is feasible without requiring additional hardware. This is the most cost-effective solution.

B. Add another disk pool for file storage to their current FlashArray:

Adding a separate disk pool for file storage is unnecessary because Purity File Services can handle both block and file workloads on the same array.

C. Purchase an entry-level FlashBlade for the file workload:

WhileFlashBladeis designed for file and object workloads, purchasing a new FlashBlade would be significantly more expensive than leveraging the existing FlashArray. This option does not align with the customer's goal of minimizing costs.

D. NDU the FlashArray //X to a //XL and run both workloads there:

Upgrading the FlashArray//X to a FlashArray//XL via a Non-Disruptive Upgrade (NDU) is unnecessary for this use case. The current FlashArray//X has sufficient capacity to handle both workloads, and upgrading to a higher-tier array would increase costs unnecessarily.

Recommendation:

The most cost-effective solution isA. Run both workloads on the current FlashArray, leveraging Purity File Services to support the file workload.

References:

Purity File Services Documentation:

Purity File Services

Explains how to configure and use file services on FlashArray.

FlashArray Use Cases:

FlashArray Use Cases

Highlights the versatility of FlashArray for both block and file workloads.

To determine the raw capacity required to meet the customer's needs for 3 years, we need to account for the current workload, data reduction ratio (DRR), growth rate, and headroom.

Step-by-Step Calculation:

Current Logical Workload:

The customer's current workload is50 TB.

Expected Growth Over 3 Years:

The workload grows at a predictable rate of25% per year.

After 3 years, the logical workload will be:

A white paper with black text AI-generated content may be incorrect.

A screenshot of a document AI-generated content may be incorrect.

To gain more insight and control over their Pure Storage FlashArray and VMware environment from a single user interface, the customer should configure theFlashArray Management Pack for vRealize Operations Manager (vROps). Here's why:

Analysis of Options:

A. Ensure all VMware API for Array Integration (VAAI) primitives are enabled:

VAAI is a set of APIs that offloads storage tasks from the ESXi host to the storage array, improving performance and efficiency. However, it does not provide a unified interface for managing both FlashArray and VMware environments.

B. Log in to the FlashArray GUI and install the plugin for vSphere Client:

While the FlashArray plugin for vSphere Client provides some integration, such as provisioning and monitoring FlashArray volumes directly from the vSphere Client, it does not offer comprehensive visibility and control over both environments from a single interface.

C. Configure FlashArray Management Pack for vRealize Operations Manager:

TheFlashArray Management Pack for vROpsintegrates Pure Storage FlashArray with VMware vRealize Operations Manager, enabling centralized monitoring, analytics, and management of both environments from a single pane of glass.

This solution provides deep insights into storage performance, capacity utilization, and health metrics, making it the ideal choice for the customer's requirement.

D. Install Pure Storage SRA for VMware Site Recovery Manager (SRM):

The Pure Storage Storage Replication Adapter (SRA) is used for disaster recovery orchestration with VMware SRM. It does not provide a unified interface for managing FlashArray and VMware environments.

Recommendation:

The correct answer isC. Configure FlashArray Management Pack for vRealize Operations Manager, as it fulfills the customer's need for a single user interface to manage both FlashArray and VMware environments.

References:

Pure Storage FlashArray Management Pack for vROps Documentation:

FlashArray Management Pack for vROps

Explains how to integrate FlashArray with vROps for unified monitoring and management.

Pure Storage VMware Integration Overview:

Pure Storage VMware Integration

Provides an overview of Pure Storage's VMware integration solutions.

SE should recommend adding the 10 TB test/dev workload to the array while advising the admin to monitor performance and capacity. This recommendation assumes that the array has sufficient resources (e.g., available capacity, performance headroom) to handle the additional workload without requiring immediate upgrades or changes.

Why This Matters:

Current Array Capacity and Performance:

Pure Storage FlashArray is designed to efficiently handle workloads with advanced data reduction techniques (deduplication, compression, etc.) and high-performance NVMe storage.

If the array has sufficient unused capacity and performance headroom, adding a 10 TB test/dev workload is feasible without requiring hardware upgrades.

Monitoring:

After adding the workload, it is critical to monitor bothperformance metrics(e.g., latency, IOPS, throughput) andcapacity utilizationto ensure the array continues to meet SLAs and does not exceed its limits.

Why Not the Other Options?

A. Upgrade the controller to an //X90R3 to handle the additional workload:

Upgrading the controller is unnecessary unless the current controller is nearing its performance limits. Test/dev workloads are typically less demanding than production workloads, so this step would likely be premature.

B. Add more DirectFlash NVMe modules to the expansion shelf to handle the additional capacity:

Adding more NVMe modules is only necessary if the array is running out of physical capacity. If the array already has sufficient capacity, this step is not required.

C. Upgrade the 22 TB DirectFlash NVMe modules to a higher capacity to handle the additional workload:

Upgrading the NVMe modules to higher-capacity ones is a significant investment and is only justified if the array is consistently running out of capacity. For a 10 TB workload, this step is likely excessive.

Key Points:

Feasibility of Adding Workload:The array can likely handle the additional 10 TB workload without immediate upgrades.

Monitoring:Continuous monitoring ensures that performance and capacity remain within acceptable limits.

Cost Efficiency:Avoiding unnecessary upgrades or changes helps optimize costs while meeting the customer's needs.

References:

Pure Storage FlashArray Documentation: "Capacity Planning and Workload Sizing"

Pure Storage Whitepaper: "Best Practices for Managing Test/Dev Workloads"

Pure Storage Knowledge Base: "Adding Workloads to FlashArray Without Disruption"

To achieve100 Gbps of consistent raw network throughputbetween the FlashArray and the dedicated SAN switches, while ensuringresiliency, the customer must connect a sufficient number of Ethernet ports from the FlashArray to the SAN switches. Given that the dedicated SAN switches support up to25 Gbps connectivity per port, the calculation is as follows:

Throughput Requirement:

The customer requires100 Gbpsof raw throughput.

Each Ethernet port provides25 Gbpsof bandwidth.

Number of Ports Needed:

To meet the 100 Gbps requirement:

A close up of a text AI-generated content may be incorrect.

Resiliency Requirement:

Resiliency ensures that the solution can tolerate failures (e.g., switch or link failures). To achieve this, the customer mustdouble the number of portsto provide redundant paths.

Therefore, the total number of ports required is:4×2=8ports.

Why Not the Other Options?

B. 2:

Two ports would only provide50 Gbpsof raw throughput (2 × 25 Gbps), which does not meet the 100 Gbps requirement. Additionally, there would be no redundancy, violating the resiliency requirement.

C. 4:

Four ports would meet the 100 Gbps throughput requirement but would lack redundancy, making the solution vulnerable to failures.

D. 16:

Sixteen ports would exceed the required throughput and redundancy, resulting in unnecessary costs and complexity.

Key Points:

Throughput Calculation:Ensure the total bandwidth meets the 100 Gbps requirement.

Resiliency:Double the number of ports to provide redundant paths for high availability.

Optimization:Use the minimum number of ports that satisfy both throughput and resiliency requirements.

References:

Pure Storage FlashArray Documentation: "Network Design and Configuration Best Practices"

Pure Storage Whitepaper: "NVMe-TCP Connectivity and Performance Optimization"

Pure Storage Knowledge Base: "Calculating Required Network Ports for FlashArray"

When a controller generates a hash for an incoming write request and finds that the hash already exists in the hash table, the next step is tocompare the new block to the existing block to confirm they are duplicates.

Why This Matters:

Hash Collision Handling:

Hash functions can sometimes produce the same hash value for different data blocks (a "hash collision"). To ensure data integrity, the system must verify that the new block is identical to the existing block before deduplication occurs.

Data Integrity:

Comparing the blocks ensures that only true duplicates are deduplicated, preventing data corruption or loss due to hash collisions.

Why Not the Other Options?

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

Hashing the next block is unnecessary at this stage. The focus is on verifying whether the current block is a duplicate.

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

Compression is a separate process from deduplication and does not occur immediately after hashing.

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

Expanding the block is not part of the deduplication process. Deduplication operates on individual blocks, not larger datasets.

Key Points:

Hash Table Lookup:Identifies potential duplicates based on hash values.

Block Comparison:Confirms that the new block matches the existing block to ensure data integrity.

Deduplication:Eliminates redundant data to optimize storage efficiency.

References:

Pure Storage FlashArray Documentation: "Understanding Deduplication in Purity//FA"

Pure Storage Whitepaper: "Data Reduction Techniques in FlashArray"

Pure Storage Knowledge Base: "How Deduplication Works in FlashArray"

The System Administrator requires anoffsite backup solutionthat is cost-effective, stores data in a different location from the current FlashArray, and does not prioritize restore times. The best solution to recommend isCloudSnap to a public cloud provider.

Why This Matters:

CloudSnap:

CloudSnap is a feature that offloads snapshots to cloud storage providers like AWS S3 or Azure Blob.

It is highly cost-effective because customers only pay for the cloud storage they use, and it eliminates the need for additional on-premises hardware.

Since restore times are not a concern, CloudSnap's slower restore process compared to on-premises solutions is acceptable.

Why Not the Other Options?

A. ActiveCluster to a FlashArray//C60:

ActiveCluster provides synchronous replication for high availability but does not meet the requirement for an offsite backup solution. Additionally, it is more expensive than CloudSnap.

B. ActiveDR to a FlashArray//C60:

ActiveDR provides asynchronous replication for disaster recovery but requires additional hardware (FlashArray//C60), which increases costs. It is less cost-effective than CloudSnap for backup purposes.

Key Points:

Cost Efficiency:CloudSnap leverages cloud storage, minimizing upfront and ongoing costs.

Offsite Storage:Ensures backups are stored in a different location from the primary FlashArray.

Restore Times:CloudSnap's slower restore process is acceptable given the customer's requirements.

References:

Pure Storage FlashArray Documentation: "CloudSnap for Offsite Backups"

Pure Storage Whitepaper: "Cost-Effective Backup Strategies with FlashArray"

Pure Storage Knowledge Base: "Choosing the Right Backup Solution for Your Workload"

Why This Matters:

Usable Storage Space Consumed:

The "usable storage space consumed" refers to the actual physical capacity used on the array after accounting for RAID overhead but before applying data reduction techniques like deduplication and compression.

This value represents the raw space utilized by the data stored on the array, excluding any logical space savings from data reduction.

Why Not the Other Options?

B. 5.58 T:

This value likely represents thelogical capacityprovisioned or consumed after applying data reduction techniques (e.g., deduplication and compression). However, the question specifically asks for theusable storage space consumed, which excludes logical space savings.

C. 1.22 T:

This value might represent theraw capacityof the drives or some other metric unrelated to the usable storage space consumed. It does not align with the definition of usable storage space.

D. 4.36 T:

This value could represent an intermediate calculation or another metric, but it does not match the usable storage space consumed as shown in the exhibit.

Key Points:

Usable Storage Space Consumed:Represents the physical capacity used on the array after RAID overhead but before data reduction.

Logical vs. Physical Capacity:Logical capacity reflects space savings from deduplication and compression, while usable storage space reflects the actual physical usage.

Exhibit Analysis:Carefully interpret the metrics provided in the exhibit to identify the correct value.

References:

Pure Storage FlashArray Documentation: "Understanding Array Capacity Metrics"

Pure Storage Whitepaper: "Capacity Management and Data Reduction"

Pure Storage Knowledge Base: "What is Usable Space vs. Raw Space?"

Pure Storage'sRight-Size Guaranteepromises theeffective capacity of the FlashArray, ensuring that customers receive the logical capacity they expect based on their workload's data reduction profile.

Why This Matters:

Effective Capacity:

Effective capacity refers to the logical capacity available after applying data reduction techniques like deduplication, compression, and pattern removal.

The Right-Size Guarantee ensures that customers achieve the expected effective capacity for their workloads, aligning with Pure Storage's commitment to delivering predictable and reliable storage solutions.

Customer Assurance:

If the actual effective capacity does not meet expectations, the customer can work with their SE to address the issue, potentially adjusting their subscription or configuration.

Why Not the Other Options?

A. The performance of the FlashArray model:

The Right-Size Guarantee does not specifically address performance metrics like latency or IOPS. It focuses on capacity-related assurances.

C. The Data Reduction Rate by workload:

While data reduction contributes to effective capacity, the guarantee is not tied to a specific data reduction rate. Instead, it ensures the overall effective capacity meets expectations.

D. The customer's Total Efficiency Ratio:

The Total Efficiency Ratio combines data reduction and other factors but is not the focus of the Right-Size Guarantee.

Key Points:

Effective Capacity:The guarantee ensures customers receive the expected logical capacity based on data reduction.

Data Reduction Techniques:Deduplication, compression, and pattern removal contribute to effective capacity.

Customer Support:Customers can collaborate with their SE if the guaranteed capacity is not achieved.

References:

Pure Storage Evergreen//Forever Documentation: "Understanding the Right-Size Guarantee"

Pure Storage Whitepaper: "Maximizing Data Reduction with FlashArray"

Pure Storage Knowledge Base: "Right-Size Guarantee Terms and Conditions"

The customer requires a disaster recovery (DR) solution that allows them to replicate data from their on-premises environment to the public cloud. They also need failover and fallback capabilities, meaning they must be able to switch operations to the cloud during a disaster and revert back to on-premises once the issue is resolved.

Snapshot replication between a FlashArray on-premises and Cloud Block Store (CBS)is the best solution for this use case. CBS integrates seamlessly with on-premises FlashArrays, enabling efficient replication of snapshots to the cloud. This feature supports failover and fallback operations, ensuring business continuity in the event of a disaster.

Why Not the Other Options?

B. Purity//FA CloudSnap periodic offload of snapshots to AWS:While CloudSnap allows periodic offloading of snapshots to AWS S3 for backup purposes, it does not provide the real-time replication and failover/fallback capabilities required for DR.

C. ActiveCluster FC replication between a FlashArray on site and Evergreen//One:ActiveCluster is designed for synchronous replication between two FlashArrays in different locations, but it does not support replication to the public cloud.

Key Points:

Snapshot Replication:Enables efficient and reliable replication of data between on-premises FlashArrays and Cloud Block Store.

Failover and Fallback:CBS supports these capabilities, ensuring minimal downtime during a disaster.

Integration with FlashArray:CBS is specifically designed to work with FlashArray, providing a seamless DR solution.

References:

Pure Storage Cloud Block Store Documentation: "Disaster Recovery with Cloud Block Store"

Pure Storage Best Practices Guide: "Replication and Failover in Hybrid Cloud Environments"

Pure Storage Whitepaper: "Hybrid Cloud Architectures with FlashArray and Cloud Block Store"

TheEvergreen//Foreverprogram is Pure Storage's premium subscription offering, providing continuous upgrades and enhancements to ensure customers always have access to the latest technology. In contrast,Evergreen//Foundationis a lower-tier subscription with limited benefits. Here's an analysis of the features:

Correct Features:

A. Controller Upgrades:

Controller upgrades are a key feature of Evergreen//Forever, allowing customers to upgrade their FlashArray controllers non-disruptively to newer generations.

This feature isnot includedin Evergreen//Foundation.

D. Upgrade Always:

"Upgrade Always" ensures that customers can continuously upgrade their hardware and software without additional costs.

This is a hallmark of Evergreen//Forever and isnot availablein Evergreen//Foundation.

Incorrect Features:

B. Pro Deployment:

Pro Deployment services are available across all Evergreen tiers, including Evergreen//Foundation.

Therefore, this is not specific to Evergreen//Forever.

C. Capacity Consolidation:

Capacity consolidation is a general benefit of Pure Storage arrays and is not exclusive to Evergreen//Forever.

It is also available in Evergreen//Foundation.

Final Recommendation:

The correct answers areA. Controller UpgradesandD. Upgrade Always, as these are specific to Evergreen//Forever and not included in Evergreen//Foundation.

References:

Evergreen//Forever Program Overview:

Evergreen//Forever

Explains the benefits and features of Evergreen//Forever.

Evergreen Subscription Tiers Comparison:

Evergreen Tiers

Compares the features of Evergreen//Forever and Evergreen//Foundation.

TheSE should respond that the customer can use their current FlashArray for Windows file sharesalongside their existing Oracle workloads. Pure Storage FlashArray is a versatile platform capable of supporting multiple workloads, including block storage for databases (e.g., Oracle) and file services for Windows file shares.

Why This Matters:

FlashArray Versatility:

Pure Storage FlashArray supports both block and file workloads through its integrated architecture. While FlashArray is primarily known for block storage, it can also support file workloads usingFA File Services, which provides NFS and SMB protocols for file sharing.

The customer does not need to migrate their Windows file servers or upgrade their hardware unless there are specific capacity or performance constraints.

Current Array Feasibility:

Assuming the existing //X90R3 array has sufficient capacity and performance headroom, it can handle the additional workload without requiring upgrades.

Why Not the Other Options?

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

While migrating file servers to Pure Storage can provide benefits like simplified management and improved performance, it is not a requirement. The customer can continue using their existing file servers while leveraging FlashArray for block storage.

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

Upgrading to a higher-end model like FlashArray//XL is unnecessary unless the current array lacks the required capacity or performance for the additional workload. The //X90R3 is fully capable of supporting FA File Services.

Key Points:

Versatility:FlashArray can support both block and file workloads simultaneously.

No Immediate Upgrades Needed:The current array can likely handle the additional workload without requiring hardware changes.

Workload Consolidation:Using a single platform for multiple workloads simplifies infrastructure and reduces costs.

References:

Pure Storage FlashArray Documentation: "FA File Services Overview"

Pure Storage Whitepaper: "Consolidating Workloads on FlashArray"

Pure Storage Knowledge Base: "Supporting Multiple Workloads with FlashArray"

To achieve the lowest RPO (Recovery Point Objective) disaster recovery strategy between two data centers located 30 miles apart with a round-trip latency of 4ms,Purity Snapshot Replicationis the best choice. Here's why:

Analysis of Options:

A. Purity Snapshot Replication:

Snapshot Replication is an asynchronous replication method that periodically replicates snapshots of volumes to a remote FlashArray.

With a round-trip latency of 4ms, Snapshot Replication can achieve very low RPOs (typically seconds to minutes), making it suitable for disaster recovery in this scenario.

B. Purity ActiveCluster:

ActiveCluster is a synchronous replication solution that provides active-active high availability across two arrays.

While ActiveCluster offers zero RPO and zero RTO, it is typically limited to shorter distances due to latency constraints. At 30 miles and 4ms latency, ActiveCluster may still work but is less optimal compared to Snapshot Replication for disaster recovery.

C. Pure1 Manage:

Pure1 Manage is a cloud-based monitoring and management platform for Pure Storage arrays. It does not provide replication or disaster recovery capabilities.

D. Purity Snapshots:

Snapshots are point-in-time copies of data stored locally on the FlashArray. They do not provide replication to a remote site and are therefore unsuitable for disaster recovery.

Recommendation:

The correct answer isA. Purity Snapshot Replication, as it provides the lowest RPO for disaster recovery over a 30-mile distance with 4ms latency.

References:

Purity Snapshot Replication Documentation:

Purity Snapshot Replication

Explains how Snapshot Replication works and its use cases.

Purity ActiveCluster Documentation:

Purity ActiveCluster

Details the capabilities and limitations of ActiveCluster.