Pure Storage FlashArray Architect Associate FAAA_004 Exam Questions

Answer : A, D

The customer is reviewing their disaster recovery (DR) strategy and wants to replicate data to a secondary datacenter while addressing internal SLAs for RPO (Recovery Point Objective) and RTO (Recovery Time Objective) . To meet these requirements, the SE should focus on two key Pure Storage FlashArray features: FlashRecover and ActiveDR .

Why These Features?

FlashRecover:

FlashRecover is a snapshot-based replication feature that allows efficient point-in-time copies of data to be replicated to a secondary site.

It helps achieve low RPOs by enabling frequent snapshots and replication to the DR site.

This ensures minimal data loss in the event of a failure.

ActiveDR:

ActiveDR is a disaster recovery solution that provides asynchronous replication between two FlashArrays.

It is specifically designed to minimize RTO by enabling fast failover and failback capabilities.

ActiveDR ensures that the secondary site is always ready to take over with minimal downtime, meeting strict RTO requirements.

Why Not the Other Options?

B . ActiveCluster:

ActiveCluster is a synchronous replication solution for high availability across two sites. While it provides zero RPO and near-zero RTO, it requires both sites to be within synchronous distance (typically <10ms latency). Since the customer is replicating to a secondary datacenter (likely farther away), ActiveCluster is not suitable.

C . CloudSnap:

CloudSnap is a feature that offloads snapshots to cloud storage (e.g., AWS S3 or Azure Blob). While it is useful for backup and archival purposes, it does not provide the real-time replication and failover capabilities needed for DR with strict RPO and RTO SLAs.

Key Points:

FlashRecover: Enables efficient replication with low RPOs through snapshot-based replication.

ActiveDR: Provides asynchronous replication with fast failover and failback capabilities to meet RTO requirements.

SLA Alignment: Both features are designed to help customers meet their internal SLAs for RPO and RTO.

Pure Storage FlashArray Documentation: 'Disaster Recovery with FlashRecover and ActiveDR'

Pure Storage Whitepaper: 'Meeting RPO and RTO Requirements with FlashArray'

Pure Storage Knowledge Base: 'Best Practices for Disaster Recovery Planning'

Answer : C

The customer at the small regional hospital requires a storage solution for a PACS image archive with the following requirements:

More than 1 PB of storage

Latency is not a concern

Customer user shares must be on the same array

The best solution to meet these needs is FlashArray//C .

Why This Matters:

FlashArray//C:

FlashArray//C is designed for capacity-optimized workloads , making it ideal for use cases like PACS image archives that require large amounts of storage at a lower cost per GB.

It supports QLC flash technology , which provides high density and cost efficiency for less performance-intensive workloads.

With its ability to scale to over 1 PB of storage, FlashArray//C can meet the customer's capacity requirements while supporting both block and file workloads (e.g., user shares) on the same array using FA File Services .

Why Not the Other Options?

A . FlashArray//X:

FlashArray//X is optimized for high-performance workloads, such as databases and mission-critical applications. While it supports large capacities, it is more expensive and not the most cost-effective solution for latency-insensitive workloads like PACS archives.

B . FlashArray//XL:

FlashArray//XL is designed for extreme-scale workloads requiring massive performance and capacity. It is overkill for this use case and would significantly increase costs without providing proportional benefits.

Key Points:

FlashArray//C: Provides high-density storage at a low cost per GB, ideal for large-scale, latency-insensitive workloads.

Unified Storage: Supports both block and file workloads on the same array, meeting the requirement for user shares.

Cost Efficiency: Balances performance and cost, making it suitable for PACS archives and similar use cases.

Pure Storage FlashArray//C Documentation: 'Use Cases for FlashArray//C'

Pure Storage Whitepaper: 'Optimizing Storage Costs with FlashArray//C'

Pure Storage Knowledge Base: 'Choosing the Right FlashArray Model for Your Workload'

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 : B

The Pure Storage offering that can be deployed in AWS is Cloud Block Store .

Why This Matters:

Cloud Block Store:

Cloud Block Store is a cloud-native block storage solution that runs in public clouds like AWS and Azure.

It provides enterprise-grade storage features, including deduplication, compression, and thin provisioning, while seamlessly integrating with on-premises FlashArray environments.

Why Not the Other Options?

A . ObjectEngine:

ObjectEngine is a backup and recovery solution designed for rapid restores and backups. It is not a storage solution that can be deployed in AWS.

C . CloudSnap:

CloudSnap is a feature that offloads snapshots to cloud storage (e.g., AWS S3 or Azure Blob). It is not a standalone storage solution but rather a feature of FlashArray.

Key Points:

Cloud Block Store: Provides block storage in AWS with enterprise-grade features.

Integration: Seamlessly integrates with on-premises FlashArray environments for hybrid cloud architectures.

Scalability: Enables scalable and cost-effective storage in the cloud.

Pure Storage Cloud Block Store Documentation: 'Deploying Cloud Block Store in AWS'

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

Pure Storage Knowledge Base: 'Cloud Block Store Use Cases and Deployment'

Answer : A

For an ActiveCluster solution with Uniform Configuration , the architect should recommend dual connections from each controller through two fabrics to ensure high availability and redundancy in Fibre Channel connectivity.

Why This Matters:

Dual Connections:

Each controller should have dual connections to provide redundancy and fault tolerance. If one connection fails, the other ensures uninterrupted communication between the host and the array.

Two Fabrics:

Using two independent Fibre Channel fabrics (e.g., Fabric A and Fabric B) ensures that there is no single point of failure in the network infrastructure. This aligns with best practices for ActiveCluster deployments.

Why Not the Other Options?

B . A single connection from each controller through two fabrics:

A single connection per controller does not provide sufficient redundancy. If the connection fails, the host may lose access to the array.

C . Crossed connections from each controller through a single fabric:

Using a single fabric introduces a single point of failure. Additionally, 'crossed connections' are not a standard or recommended configuration for ActiveCluster.

D . A single connection from each controller through a single fabric:

This configuration lacks both redundancy at the connection level and at the fabric level, making it highly vulnerable to failures.

Key Points:

Redundancy: Dual connections and two fabrics ensure fault tolerance and high availability.

Best Practices: Aligns with Pure Storage's recommendations for ActiveCluster deployments.

Uniform Configuration: Ensures consistent and reliable connectivity across all hosts in the cluster.

Pure Storage FlashArray Documentation: 'ActiveCluster Best Practices for Fibre Channel Connectivity'

Pure Storage Whitepaper: 'Designing High-Availability Solutions with ActiveCluster'

Pure Storage Knowledge Base: 'Configuring Host Connections for ActiveCluster'

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'

Answer : A

To meet the customer's requirement for 450 TB of block storage with a 4:1 data reduction ratio, we need to calculate the effective usable capacity required and select the appropriate array configuration.

Step-by-Step Calculation:

Effective Usable Capacity Needed :

The workload requires 450 TB of logical storage.

With a 4:1 data reduction ratio, the physical storage required is:

Array Selection :

The selected array must provide at least 112.5 TB of usable capacity after accounting for overhead and RAID protection.

Let's evaluate the options:

A . FlashArray//C40R3 247 TB :

The FlashArray//C40R3 provides 247 TB of raw capacity. After accounting for overhead (typically ~20%), the usable capacity is approximately:UsableCapacity=247TB0.8=197.6TB.

This exceeds the required 112.5 TB , making it a valid option.

B . FlashArray//C60R3 878 TB :

The FlashArray//C60R3 provides 878 TB of raw capacity, which is significantly larger than needed. While it meets the requirement, it is not the minimum configuration.

C . FlashArray//X70R3 228 TB :

The FlashArray//X70R3 provides 228 TB of raw capacity. After overhead, the usable capacity is approximately:UsableCapacity=228TB0.8=182.4TB.

While this also meets the requirement, it is more expensive than the C40R3.

D . FlashArray//C60R3 366 TB :

The FlashArray//C60R3 with 366 TB of raw capacity is overkill for this requirement and not cost-effective.

Recommendation :

The FlashArray//C40R3 247 TB provides the minimum required usable capacity while meeting the customer's needs.

Final Recommendation:

The correct answer is A. FlashArray//C40R3 247 TB .

FlashArray//C Series Product Overview :

FlashArray//C Series

Details the capacity and use cases for FlashArray//C models.

Capacity Planning Guide :

Pure Storage Capacity Planning

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