FlashArray Storage Professional Certification Exam Guide + Practice Questions Updated 2026

Explanation:
Similar to the previous question regarding directory services, Pure Storage Purity OS handles Role-Based Access Control (RBAC) overlaps by granting the most permissive role available to the user.
When configuring LDAP or Active Directory authentication on a FlashArray, administrators map directory groups to specific FlashArray roles (Array Admin, Storage Admin, Ops Admin, Read Only). If a user happens to be a member of multiple LDAP groups that are mapped to different roles on the array, Purity evaluates all mapped roles and automatically assigns the user the highest level of privilege during their session.
Since "Array Admin" has full administrative rights over the entire array (including hardware management, directory services configuration, and firmware upgrades) and sits higher in the hierarchy than "Storage Admin" (which is restricted to provisioning and managing storage objects like volumes and hosts), the system will seamlessly grant the user Array Admin permissions.
Here is why the other options are incorrect:
User will not be able to login (B): Purity is designed to handle this exact scenario smoothly. It resolves the conflict by defaulting to the higher privilege, rather than throwing an error or denying access.
User will have Storage Admin permissions (C): The system does not default to the lowest privilege or restrict access when a higher-level group membership is present and valid.

Explanation:
The ActiveCluster Mediator (whether it is the Pure1 Cloud Mediator or the On-Premises VM) is a
lightweight tie-breaker that communicates continuously with the management interfaces of both FlashArrays. If it was previously online and suddenly reports as "unreachable" from both arrays simultaneously, the issue is almost always caused by a network interruption or firewall rule change blocking the required communication ports between the arrays' management IP addresses and the Mediator VM.
If a network firewall is suddenly configured to drop or deny outbound TCP traffic (such as port 80/443 depending on the specific HTTP/HTTPS discovery and heartbeat configuration) from the FlashArrays to the ESXi-hosted Mediator, the arrays will fail to send their heartbeats, causing the mediator status to drop to "unreachable."
Here is why the other options are incorrect:
Fibre Channel (FC) zoning or network access has not been created properly for the host (A): The Mediator is completely independent of the front-end host storage fabric (Fibre Channel or iSCSI). Host zoning issues would prevent the ESXi server from seeing its volumes, but it would not cause the FlashArrays to lose management network connectivity to the Mediator.
The mediator does not reside within a Pure datastore (B): This is actually a strict best practice and requirement. Pure Storage explicitly states that the On-Premises Mediator VM must be deployed in a separate (third) failure domain. It should not reside on the ActiveCluster mirrored datastore, because a site-wide SAN failure would take the mediator offline exactly when it is needed most. Therefore, not residing on a Pure datastore is the correct setup, not a cause for an outage.

Explanation:
Edge Services and Gateways: Pure Storage FlashArray uses Edge Services (often associated with FA File or cloud integrations) to manage communication between the array and external services. The Gateway is the component that facilitates this secure connection.
Update Policy Control: To prevent unplanned outages or changes to the environment, Purity includes a safety toggle for Gateway updates. When the status shows "Eligible (updates disallowed)", it means a newer version of the agent is available on the Pure Storage back-end, but the array's local policy is currently set to prevent automatic or manual "one-click" updates.
GUI Authorization: This is a security and administrative control. An administrator with Array Admin privileges must navigate to the Edge Services/Gateway configuration section in the Purity GUI and explicitly change the setting to "Allow Updates". Once this toggle is enabled, the status will change to "Eligible," and the update can be initiated.
Why Option A is incorrect: While the CLI is used for many advanced support functions, the puresupport
namespace is generally reserved for Pure Storage Support technicians and requires a challenge-response session key. Standard agent updates are handled via the administrative GUI.
Why Option B is incorrect: Removing and re-installing the agent is an unnecessary and disruptive process. The "disallowed" status is simply a policy setting, not a corruption of the agent itself.

Explanation:
In Pure Storage FlashArray File Services (Purity//FA), administrators can apply Quota Policies to managed directories to control and monitor capacity consumption. When configuring the rules for these quotas, the limits are categorized into two specific types: Enforced and Unenforced.
Enforced Quotas (Hard Limits): When a quota rule is set with the --enforced flag set to True, it acts as a hard boundary. If the users or applications writing to that managed directory hit the specified capacity limit, the FlashArray will actively block any further write operations, ensuring the directory cannot exceed its allocated space.
Unenforced Quotas (Soft Limits): When a quota rule is unenforced (the flag is set to False), it acts purely as a monitoring and alerting threshold. Users can continue to write data and organically grow the directory past the specified limit without application disruption, but the system will track the overage and trigger administrative notifications.
Here is why the other options are incorrect:
File and Block (A): This describes the two underlying storage protocols/architectures the unified FlashArray serves, not the types of capacity quota limits for directories.
Limited and Unlimited (B): While you can theoretically leave a file system to grow "unlimited" up to the size of the array, the specific technical parameters in the Purity quota policy engine are defined as enforced vs. unenforced.

Explanation:
The Analysis Tab: In the Pure Storage FlashArray GUI, the Analysis tab is the primary location for deep-dive performance troubleshooting and historical data visualization. While the Storage tab provides a real-time "at-a-glance" view of a volume, the Analysis tab allows for granular filtering of specific metrics.
Granular Metric Filtering: When troubleshooting latency, it is critical to distinguish between Read and Write operations, as they interact with the Purity operating environment differently (e.g., writes hitting NVRAM vs. reads hitting the Flash modules).
External vs. Internal Latency: Pure Storage differentiates between "Array Latency" (internal processing) and "External Latency" (the time seen by the host). By navigating to Analysis > Performance, an administrator can drill down into the Volumes sub-tab.
Selecting the Volume and Operations: Once a specific volume is selected, the chart typically defaults to a combined view. To isolate "external latency for write requests," the administrator must use the legend/filters to select "Write" while deselecting "Read" and "Mirrored Write" (which refers to synchronous replication traffic in ActiveCluster environments). This provides a clean graph of the round-trip write latency specifically for that volume's host I/O.
Why other options are incorrect: Option B refers to physical port health and hardware status, not volume-level performance.
Option C provides basic volume metadata and real-time total latency, but lacks the granular historical filtering (selecting/deselecting specific I/O types) required for detailed performance analysis.