FBAP_002 practice question 2 of 15

A customer has noticed their all-flash arrays are constantly running at or near 100% load and impacting application performance. They are running…

Full set: 75 questions

Domain Monitor and Troubleshoot FlashArray and FlashBlade Solutions

A customer has noticed their all-flash arrays are constantly running at or near 100% load and impacting application performance. They are running dozens of applications on the arrays and ask for help to identify some workloads that could be moved to another storage system to reduce load and improve overall performance of all applications. Which (three) workload or data characteristics should an architect look for to identify potential candidates for migration to FlashBlade? (Choose three.)
Answer options
A: Applications requiring high throughput *** Correct answer
B: Large number of simultaneous connections Correct answer
C: Applications that can use NFS or S3 *** Correct answer
D: Highly transactional application.
E: Low latency is critical to application performance. ***
Correct Answer:
A. Applications requiring high throughput ***; B. Large number of simultaneous connections; C. Applications that can use NFS or S3 ***
Explanation

The goal is to offload an overburdened all-flash block array (like FlashArray) by migrating suitable workloads to FlashBlade. FlashBlade is a Unified Fast File and Object (UFFO) platform architected for modern, unstructured data workloads. Its key strengths are massive throughput and high concurrency. Therefore, the ideal candidates for migration are applications that require high bandwidth (A), involve a large number of simultaneous clients or connections (B), and can utilize FlashBlade's native file (NFS) or object (S3) protocols (C). Moving these types of workloads leverages FlashBlade's scale-out architecture, effectively reducing the specific load they were placing on the block array and improving performance for the remaining applications.

Why Incorrect

D. Highly transactional application. This describes Online Transaction Processing (OLTP) workloads, which are the primary use case for FlashArray, not FlashBlade, due to their need for consistent, sub-millisecond latency.
E. Low latency is critical to application performance. Workloads where ultra-low, consistent latency is the most critical factor (e.g., Tier-1 databases) are best served by FlashArray. FlashBlade is optimized for throughput and parallelism, not absolute lowest latency.

References

1. Pure Storage FlashBlade Datasheet: This document emphasizes FlashBlade's design for "multi-dimensional performance" and being "massively parallel," which directly supports its suitability for high throughput (A) and high concurrency (B) workloads. It explicitly lists NFS and S3 as its core protocols (C).

Source: Pure Storage, "FlashBlade: The Platform for Modern Data," Datasheet, 2022. Section: "Key Benefits."

2. Pure Storage FlashArray Datasheet: This document highlights FlashArray's strength in providing "consistent sub-ms latency" for "mission-critical applications," confirming that workloads where low latency is critical (E) and are highly transactional (D) are its primary domain.

Source: Pure Storage, "FlashArray//X Family," Datasheet, 2023. Section: "Product Highlights."

3. Pure Storage White Paper on Architecture: Technical white papers often contrast the two architectures. FlashArray is described as a dual-controller, scale-up architecture optimized for consistent low latency for structured data. FlashBlade is described as a multi-blade, scale-out architecture optimized for parallel performance, high throughput, and metadata-heavy operations on unstructured data. This architectural difference is the basis for selecting workloads with characteristics A and B for FlashBlade.

Source: Pure Storage, "FlashArray and FlashBlade: Better Together," White Paper (WP-000133), 2021, Page 2-3.

Scroll to Top