Exam FAAA_004 Topic 1 Question 3 Discussion
Actual exam question for Pure Storage's FAAA_004 exam
Question #: 3
Topic #: 1
Question #: 3
Topic #: 1
A cost-conscious customer at a small regional hospital is running a PACS image archive on an NL-disk array.
The customer has the following requirements:
* More than 1 PB of storage
* Latency is not a concern
* Customer user shares must be on the same array
Which solution will meet the customer's needs?
The customer has the following requirements:
* More than 1 PB of storage
* Latency is not a concern
* Customer user shares must be on the same array
Which solution will meet the customer's needs?
Suggested Answer: C Vote an answer
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.
Reference:
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"
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.
Reference:
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"
by Clara at Jul 04, 2026, 03:19 AM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).