Pure Storage FlashArray Architect Associate FAAA_004 Exam Questions

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'

Answer : A

To achieve 100 Gbps of consistent raw network throughput between the FlashArray and the dedicated SAN switches, while ensuring resiliency , 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 to 25 Gbps connectivity per port , the calculation is as follows:

Throughput Requirement:

The customer requires 100 Gbps of raw throughput.

Each Ethernet port provides 25 Gbps of bandwidth.

Number of Ports Needed:

To meet the 100 Gbps requirement:

Resiliency Requirement:

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

Therefore, the total number of ports required is:42=8ports.

Why Not the Other Options?

B . 2:

Two ports would only provide 50 Gbps of 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.

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'

Answer : A

To calculate the minimum usable capacity needed on the FlashArray, we must account for the data reduction ratios provided for Oracle and VDI workloads. Here's the step-by-step calculation:

Given Data:

Oracle data: 100 TiB with a 4:1 data reduction ratio.

VDI data: 200 TiB with a 5:1 data reduction ratio.

Calculation:

Oracle Data Reduction :

Effective capacity after reduction = 100 TiB 4 = 25 TiB .

VDI Data Reduction :

Effective capacity after reduction = 200 TiB 5 = 40 TiB .

Total Usable Capacity Needed :

Total effective capacity = 25 TiB (Oracle) + 40 TiB (VDI) = 65 TiB .

Recommendation:

The minimum usable capacity needed on the FlashArray is 65 TiB . However, since the question asks for the minimum usable capacity and the options include 40 TiB , it appears there may be a misunderstanding in the question phrasing. Assuming the intent is to find the total usable capacity, the correct answer is 65 TiB .

Pure Storage Data Reduction Overview :

Pure Storage Data Reduction

Explains how data reduction ratios impact storage capacity planning.

FlashArray Capacity Planning Guide :

FlashArray Capacity Planning

Provides guidance on calculating usable capacity based on data reduction ratios.

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 :

Provisioning Best Practices

Explains the differences between thick and thin provisioning.

Answer : A

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 the logical capacity provisioned or consumed after applying data reduction techniques (e.g., deduplication and compression). However, the question specifically asks for the usable storage space consumed , which excludes logical space savings.

C . 1.22 T:

This value might represent the raw capacity of 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.

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?'

Answer : C

The value77.24 Tin the context of Pure Storage FlashArray representsC . The guaranteed capacity.

Detailed Explanation:

Guaranteed Capacityis a feature of Pure Storage's Evergreen subscription model. It reflects the effective capacity Pure Storage commits to the customerbased on their typical data reduction ratios(deduplication, compression, and pattern removal). This value is calculated as:

GuaranteedCapacity=PhysicalRawCapacityDataReductionFactor(DRF)GuaranteedCapacity=PhysicalRawCapacityDataReductionFactor(DRF)

Pure typically guarantees a minimum DRF (e.g., 3:1 for many workloads), but actual savings often exceed this.

Why Not the Other Options?

A . Total usable space: This would include the total logical capacity after data reduction and overheads (RAID-HD, metadata), which is usuallylargerthan the guaranteed capacity.

B . Total raw space: This refers to the physical capacity of drives (e.g., 100TB raw). The value shown (77.24T) is smaller than raw, so this is incorrect.

D . Total deduplicated space: Pure Storage combines dedupe, compression, and pattern removal into a single 'data reduction' metric. Deduplication alone is not isolated in capacity reporting.

Official Reference:

Pure Storage documentation explicitly definesGuaranteed Capacityas the 'logical capacity Pure commits to deliver, factoring in data reduction.' This aligns with the Evergreen//Forever subscription model, where customers pay for usable capacity, not raw storage.

Answer : A

A protection group in a stretched pod should be used for integrating ActiveCluster with asynchronous snapshot replication . This combination allows for synchronous replication within the stretched pod (using ActiveCluster) while also enabling asynchronous replication to a third site for additional disaster recovery protection.

Why This Matters:

ActiveCluster: Provides synchronous replication between two sites within a stretched pod, ensuring zero RPO and near-zero RTO for high availability.

Async Snapshot Replication: Extends the disaster recovery strategy by replicating snapshots asynchronously to a third site, providing an additional layer of protection against regional failures.

Combining these features ensures both local high availability and remote disaster recovery.

Why Not the Other Options?

B . Using CloudSnap to offload to a third-site target:

CloudSnap is used to offload snapshots to cloud storage (e.g., AWS S3 or Azure Blob). While it is useful for backup purposes, it does not integrate with ActiveCluster for synchronous replication.

C . Initiating ActiveDR failover/failback in a test scenario:

ActiveDR is designed for asynchronous replication and failover/failback scenarios but does not integrate with ActiveCluster in a stretched pod configuration.

D . Configuring fan-out async snapshot replication:

Fan-out replication involves sending snapshots to multiple targets asynchronously. However, this does not align with the use case of integrating ActiveCluster with async replication for a stretched pod.

Key Points:

Stretched Pod: Enables synchronous replication across two sites using ActiveCluster.

Async Replication: Adds a third-site replication target for comprehensive disaster recovery.

Integrated Protection: Combines high availability and disaster recovery into a single solution.

Pure Storage FlashArray Documentation: 'ActiveCluster with Async Replication'

Pure Storage Whitepaper: 'Disaster Recovery Strategies with FlashArray'

Pure Storage Knowledge Base: 'Using Protection Groups in Stretched Pods'