FlashArray-Storage-Professional Pure Storage Pure Certified FlashArray Storage Professional Free Practice Exam Questions (2026 Updated)

In the Pure Storage FlashArray GUI, granular performance metrics (Latency, IOPS, Bandwidth) are located under the Analysis > Performance tabs. When you navigate to the Volumes sub-tab and select a specific volume, Purity displays a unified line graph tracking the performance of that volume over time.

By default, the Latency graph simultaneously plots Read , Write , and Mirrored Write (for volumes participating in an ActiveCluster or synchronous replication pod) latencies. Because these lines can overlap or compress the Y-axis (especially if one metric spikes), isolating a specific metric requires interacting with the graph ' s legend.

To view the exact, un-obscured latency for standard write requests to that volume, the administrator should click on " Read " and " Mirrored Write " in the chart ' s legend. This deselects those metrics, effectively hiding their lines from the graph and automatically rescaling the view to exclusively display the host write latency.

Here is why the other options are incorrect:

Health > Network (A): The Health tab is used to check the hardware status of the physical controller ports, including link state and errors. While you might see port-level throughput or queue depth here, it does not provide volume-specific application latency.

Storage > Volumes > Details (B): The Storage tab is primarily used for provisioning and configuration management. Clicking on a volume here will show its size, data reduction ratio, snapshot policies, and connected hosts, but it does not provide detailed interactive performance graphs.

Understanding the Load Meter: The Load Meter in Pure1 and Purity represents the percentage of the array ' s performance capacity currently being utilized. It takes into account CPU cycles, back-end metadata processing, and front-end I/O. A 90% load means the controllers are nearly saturated.

The Impact of Capacity on Load: As a FlashArray fills up (specifically beyond 80% ), the Purity Operating Environment must work harder to find and organize free space. This " Garbage Collection " (GC) process becomes more intensive, which consumes more controller resources and contributes to a higher Load Meter reading.

Internal System QoS: To ensure the stability and integrity of the storage, Pure Storage uses Internal Quality of Service (QoS) . This is an " always-on " feature that prioritizes critical system processes (like metadata updates, internal health checks, and data protection) over incoming host I/O during periods of extreme resource contention.

Graceful Performance Pacing: When the load is consistently high (like the 90% described), Purity may introduce small amounts of latency to the host I/O (often seen as " Wait " or " Queue " time) to " pace " the workload. This prevents the controllers from reaching a 100% " locked " state, ensuring the array remains responsive and healthy even under heavy pressure.

Why Option C is incorrect: While the array needs to reclaim space, prioritizing Space Reclamation (a background task) during a 90% performance load would likely push the controllers to 100% load, causing significant latency spikes or instability for the host. The system must balance reclamation with active production I/O.

Purity Active/Active Architecture: Pure Storage FlashArrays use an Active/Active controller architecture. Under normal operating conditions, both controllers (CT0 and CT1) are healthy and independently serve I/O through their respective physical Fibre Channel ports.

The Scenario (Controller Failover): The output provided shows that the host initiator is seeing target WWNs associated with both CT0 and CT1, but the " Target " column indicates they are all being reached via the paths currently managed by one controller or through a specific failover mechanism.

Virtual WWNs and Transparency: In a controller failover or maintenance scenario, Pure Storage utilizes a feature where the WWNs of the " failed " or " offline " controller are logically moved to or presented by the " surviving " controller. This ensures that the host ' s MPIO (Multi-path I/O) software does not see a permanent " Path Down " error for those specific WWNs, but rather a transition.

Analyzing the Output: When you see CT1 port WWNs (e.g., 52:4A:93:78:55:2D:E3:10) appearing in the connectivity table in a way that implies they are being routed or presented through the physical infrastructure of CT0, it indicates that the array is in a state where one controller is assuming the identity/connectivity of the other. This is a key troubleshooting indicator that the array is likely undergoing a controller reboot, a Purity upgrade, or has experienced a controller hardware failure.

Why A and B are incorrect: * Option A: Multipathing software on the host handles path failures, but it wouldn ' t cause the array to report WWNs in this specific " cross-presented " manner in a connectivity log.

Option B: If there were a total outage on CT1 without this presentation mechanism, the paths would simply show as " Disconnected " or be missing from the initiator ' s view entirely.

API Evolution: Pure Storage introduced REST API 2.x to provide a more scalable, standardized, and performant way to automate FlashArray management. It uses a different authentication method (OAuth2 with API Clients) compared to the API Token-based method in 1.x.

Feature Freeze on 1.x: As of Purity 6.x and beyond, Pure Storage has designated REST API 1.x as " Legacy. " While 1.x is still supported for backward compatibility to ensure older scripts don ' t break, all new Purity features (such as specialized ActiveDR commands, advanced File Services, or new hardware capabilities) are only developed and exposed via REST API 2.x .

Side-by-Side Support: Contrary to option C, both versions are supported side-by-side on the same array. An administrator can run a script using 1.x for volume creation and another script using 2.x for performance monitoring simultaneously without contacting support.

Feature Parity: REST API 2.x has long since reached and exceeded the capabilities of 1.x. It offers improved filtering, pagination, and a more consistent object model (e.g., /volumes instead of multiple nested endpoints).

Best Practice: Pure Storage strongly recommends that all new automation projects use REST API 2.x to ensure access to the full suite of Purity features and to future-proof infrastructure-as-code (IaC) workflows.

Policy-Driven Automation: Pure Protect //DRaaS (Disaster Recovery as a Service) is built on a declarative policy engine. When you define a business policy (Protection Group or similar policy-based management), the system ' s primary goal is to bring the environment into compliance with the " Desired State " defined by that policy.

Retention Enforcement: When the retention period is reduced (e.g., from 7 days down to 3 days), the Purity/Pure Protect engine identifies that any existing snapshots or backups older than the new 3-day threshold are now " out of policy. "

Immediate Reclamation: Unlike some legacy backup systems that only apply new retention settings to future backups, Pure Storage ' s policy-driven architecture typically triggers an immediate cleanup of the now-obsolete data to reclaim space on the target. This ensures the environment matches the modified policy requirements immediately upon the policy update.

SafeMode Considerations: If SafeMode is enabled on the target, these " erased " backups will actually move into the " Destroyed " (but not yet eradicated) bucket for the duration of the SafeMode timer, providing a safety net against accidental policy changes or malicious deletions. However, from the perspective of the active DR policy, they are removed.

ActiveCluster and Pod Roles: In a Pure Storage ActiveCluster or ActiveDR environment, a Pod is a management container for volumes. To move workloads or perform a planned failover between two arrays, you use the Promote and Demote commands.

The Reversal Process: When you have two pods in a replication relationship (Source and Target), data flows from the Promoted (Active/Source) pod to the Demoted (Passive/Target) pod.

When you Demote the current source, it transitions from a " read-write " state to a " read-only " (passive) state.

If the other pod in the pair is then Promoted , Purity automatically intelligently reverses the direction of replication . The array that was previously receiving data now begins sending incremental updates back to the original source.

Continuous Protection: This design ensures that you don ' t have to manually tear down and recreate replication schedules every time you switch production sites. The system tracks the metadata changes and ensures that only the delta (changed blocks) are sent in the new direction.

Why Option C is incorrect: If replication were simply paused, the two sites would quickly drift out of sync, making it impossible to fail back without a full baseline resync.

Why Option A is incorrect: Demoting a pod does not delete any data; it simply changes the access characteristics and replication role. The data remains fully intact on the storage media.

Definition of a Blackout Window: In Purity//FA, a Blackout Window is a scheduled period during which asynchronous replication is suspended. This is typically used by administrators to preserve WAN bandwidth during peak business hours or to prevent replication traffic from competing with high-priority local workloads (like a massive database batch job).

The " In-Progress " Rule: One of the most important characteristics of a blackout window is that it is non-disruptive to active transfers . If a replication job started at 7:55 AM and the blackout window begins at 8:00 AM, Purity will allow that specific transfer to continue until it finishes.

The Prevention Mechanism: Once the clock hits the start of the blackout window, the replication scheduler is effectively " paused. " No new snapshots will be queued for transfer, and no new replication sessions will be initiated until the window expires.

Why Option A is incorrect: Purity does not kill active transfers. Abruptly stopping a transfer would waste the bandwidth already consumed and require the entire delta-set to be re-calculated or re-sent later.

Why Option B is incorrect: The phrasing is logically inconsistent; you cannot prevent something that " started before " the window from being " new " during the window.

Best Practice: When configuring blackout windows, ensure that the " clear " time (the time between windows) is long enough to allow the array to catch up on the snapshots that were queued during the blackout, otherwise, you risk triggering Alert 51 (Replication Delayed) .

Pure1 and Phone Home: Pure1 is a cloud-based management and monitoring platform. For the FlashArray to communicate its health data, performance metrics, and alerts to Pure Storage, it must be able to " Phone Home. "

The Power of HTTPS: This communication is encrypted and sent via the HTTPS protocol. Consequently, the standard port for HTTPS, TCP 443 , must be opened for outbound traffic on the management network.

Firewall Configuration: The array controllers initiate an outbound connection to the Pure Storage cloud (specifically to destinations like cloud-connect.purestorage.com). Because it is an outbound-initiated connection, most stateful firewalls will allow the return traffic automatically once port 443 is permitted.

Why Option A is incorrect: Port 22 (SSH) is used for secure shell access to the array ' s CLI. While essential for local administration, it is not used for the automated Phone Home or Pure1 telemetry data stream.

Why Option B is incorrect: Port 8117 was historically used for the " Remote Assist " tunnel in older Purity versions. However, even for Remote Assist, modern Purity versions have transitioned to using port 443 to simplify firewall rules for customers. It is not the standard port for the general Phone Home/Pure1 logging service.

Verification: An administrator can verify connectivity by running the purearray test phonehome command in the CLI. If port 443 is blocked, the test will fail with a connection timeout.

In the Pure Storage Purity operating environment, a volume can only be a member of one Volume Group at a time .

When an administrator navigates to a Volume Group in the GUI and clicks to add members, the system filters the inventory and only displays volumes that are currently " unassigned " (not belonging to any Volume Group). If a volume is already residing inside another Volume Group, Purity intentionally hides it from this available list to prevent conflicting overlapping memberships. To resolve this, the administrator must first navigate to the volume ' s current Volume Group, remove the volume from that group, and then it will become available to add to the new one.

Here is why the other options are incorrect:

It is already part of a Protection Group (B): Protection Groups (pgroups) manage snapshot and replication schedules. A volume can absolutely be a standalone member of a Protection Group while simultaneously being added to a Volume Group. Being in a pgroup does not hide it from the vgroup selection list.

It is protected by SafeMode (C): SafeMode is a ransomware protection feature that prevents the manual eradication of destroyed volumes and snapshots before their retention timer expires. It does not dictate or restrict logical organizational containers like Volume Groups.

ActiveCluster Connectivity Models: In an ActiveCluster environment, hosts can connect to the arrays using either a Uniform or Non-Uniform access model. In a Uniform model, the host has active paths to both FlashArrays in the cluster.

The Failover Scenario: When the replication network between the two arrays fails (a " split-brain " scenario), the Mediator decides which array keeps the pod online (the winner) and which array takes it offline (the loser) to ensure data consistency.

Analyzing the Symptoms:

The pod failed over, meaning one array is now the exclusive servicer for that pod.

Most volumes in that pod stayed online for the host. This proves that the host is correctly registered in Purity (ruling out Option C) and that the general ActiveCluster/Pod logic is functioning.

Only one specific volume lost connectivity.

The Root Cause (Zoning/Access): If a single volume loses connectivity while others do not, it indicates a pathing issue specific to that volume ' s visibility. In an ActiveCluster failover, if the " winning " array does not have a physical path to the host for that specific volume (due to missing FC Zoning or Ethernet VLAN tagging on the switches), the host will lose access once the " losing " array drops its paths.

Why Option A is unlikely: If " Uniform access " (the ability to see both arrays) was the issue, it would typically affect all volumes in the pod equally during a failover, not just a single outlier. The fact that the rest of the volumes remained available suggests the host is configured for uniform access, but the specific network plumbing (zoning) for that one volume ' s path to the surviving array is missing.

!

Analyzing the Graph: The provided capacity graph shows a sharp, vertical drop in Unique and Shared space (the teal/green sections) at approximately 10:45. Simultaneously, there is a massive spike in System space (the grey shaded area).

The " System " Space Spike: In Purity, when a volume is deleted and eradicated, the data isn ' t physically wiped from the flash modules instantly. Instead, the logical references are removed, and the blocks are moved into a " Pending Reclamation " state. In older versions of Purity reporting (or specific views), this pending work is often categorized under System space until the background Garbage Collection (GC) process can physically reclaim it.

The Decay Curve: Notice the grey " System " area gradually tapers down over the following hours (from 11:00 to 14:00). This is the visual representation of the array ' s Garbage Collection engine working in the background to physically free up those blocks.

Why Option C is incorrect: If SafeMode were enabled, the space would not move into " System " space in this manner; it would remain locked in the Snapshots or Destroyed bucket for the duration of the retention period, preventing the graph from dropping at all.

Why Option A is incorrect: If space reclamation stopped working, the grey " System " area would stay flat and would not decay over time. The fact that it is trending downward proves that reclamation is actively processing the deleted volume.

SNMP Capabilities on FlashArray: Pure Storage FlashArrays support SNMP (Simple Network Management Protocol) versions v2c and v3. The primary use case for SNMP on the FlashArray is for integration with third-party monitoring tools (like SolarWinds, Nagios, or Zabbix) to provide a real-time health and performance heartbeat.

Performance Metrics (MIBs): The Pure Storage Management Information Base (MIB) specifically exposes high-level array performance metrics. These include the " Big Three " of storage performance: Latency (response time in microseconds), Bandwidth (throughput in bytes per second), and IOPS (I/O operations per second).

Scope of Monitoring: While the FlashArray GUI and CLI provide deep granularity (per host, per volume, or per pod), standard SNMP queries typically focus on array-wide performance and health status. Detailed " Host and volume performance " (Option B) is generally more effectively monitored via the Pure Storage REST API or the Pure1 VM Analytics, as SNMP is less efficient for pulling large tables of per-object data.

Capacity vs. Performance: While SNMP can report on capacity (Option C) through specific OIDs, the question specifically asks about performance statistics . In the context of Pure Storage monitoring documentation, the core performance metrics provided via SNMP traps and polling are latency, bandwidth, and IOPS.

Command Purpose: The purehost monitor command is the primary tool in the Pure Storage CLI for observing real-time performance and connectivity health from the perspective of the hosts connected to the FlashArray.

The --balance Flag: When the --balance flag is added, the output shifts from general performance (IOPS, bandwidth, latency) to showing how I/O is distributed across the available paths (controllers and ports). This is critical for identifying " unbalanced " loads, which usually point to misconfigured MPIO (Multi-Path I/O) on the host side (e.g., a host only using one controller ' s ports).

Interval vs. Repeat:

The --interval flag specifies the time in seconds between each sample. In option C, --interval 15 tells the array to refresh the data every 15 seconds.

The --repeat flag (seen in option A) is used to limit the total number of samples taken before the command exits. However, in standard troubleshooting, the administrator typically wants a consistent stream of data until manually stopped (Ctrl+C).

--resample (seen in option B) is not a valid flag for the purehost monitor command in Purity.

Best Practice: When troubleshooting multipathing, Pure Storage recommends monitoring the balance to ensure that the " Relative I/O " percentage is roughly equal across all active paths. Large discrepancies often indicate that the host ' s MPIO policy is set to " Failover Only " instead of the recommended " Round Robin " or " Least Queue Depth. "

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.

Protocol Compatibility: While NVMe-over-Fabrics (NVMe-oF) is the future of high-performance storage, support for it within specific hypervisor ecosystems varies. In the context of Microsoft Hyper-V , especially in older or standard Ethernet-switched environments, iSCSI remains the most mature, widely supported, and native protocol for block storage.

Ethernet Constraints: The question specifies an Ethernet-switched environment . This immediately rules out NVMe/FC (NVMe over Fibre Channel), as that requires dedicated Fibre Channel switching infrastructure and HBAs, not standard Ethernet.

NVMe/RoCE vs. iSCSI: While NVMe/RoCE (RDMA over Converged Ethernet) runs on Ethernet, it requires specialized NICs (RDMA-capable) and a specific switch configuration (PFC/LFC) to ensure a lossless fabric. Hyper-V has specific requirements for RoCE (often tied to SMB Direct for File services), but for general block storage volumes in a standard Ethernet environment, iSCSI is the " best suited " due to its ease of deployment, native Windows initiator support, and lack of requirement for specialized lossless hardware.

Pure Storage Best Practices: Pure Storage FlashArrays provide industry-leading iSCSI performance. When using iSCSI with Hyper-V, Pure recommends using the native Windows MPIO (Multi-Path I/O) with the " Least Queue Depth " policy to ensure optimal load balancing across the Ethernet fabric.

On a Pure Storage FlashArray, Role-Based Access Control (RBAC) allows administrators to integrate with Directory Services (like Active Directory or OpenLDAP) to control user access. Purity uses a specific hierarchy for its administrative roles, which from highest to lowest privilege are: Array Admin , Storage Admin , Ops Admin , and Read Only .

When a user logs in and is found to be a member of multiple Active Directory or LDAP groups that are mapped to different roles on the FlashArray, Purity ' s behavior is designed to grant the user the highest level of permissions among those conflicting group mappings. Because the Array Admin role is higher in the hierarchy than the Storage Admin role, the user will successfully log in and be granted full Array Admin permissions.

Here is why the other options are incorrect:

Inability to login (A): Purity handles overlapping group memberships gracefully by defaulting to the highest privilege. It does not lock the user out or cause a login failure.

Storage Admin permissions (B): Because the system grants the highest available mapped privilege, the user will not be restricted to the lower-tier Storage Admin role when they also possess group membership for the Array Admin role.

Definition of Unified Storage: In the storage industry, " Unified Storage " refers to a platform that can natively serve both Block-level storage (accessed via protocols like Fibre Channel, iSCSI, or NVMe-oF) and File-level storage (accessed via protocols like NFS or SMB) from a single pool of capacity and under a single management interface.

Pure Storage Implementation (FA File): Pure Storage achieved unified storage on the FlashArray through the introduction of Purity//FA File Services . Unlike traditional unified storage that often required a " gateway " or separate hardware " heads, " Pure’s implementation runs natively on the FlashArray controllers.

Shared Resources: On a unified FlashArray, the global storage pool is shared between volumes (Block) and file systems (File). All of Pure’s core data services—such as deduplication, compression, and SafeMode snapshots —apply globally across both block and file data.

Protocol Diversity: While Option A mentions NFS and SMB, those are strictly File protocols. Option C mentions iSCSI and FC, which are strictly Block protocols. Only Option B correctly identifies the combination of Block and File , which defines the " Unified " architecture of the FlashArray.

ActiveCluster Mediator Logic: In an ActiveCluster setup, the Mediator is a lightweight component (an " arbiter " ) that resides at a third site (failure domain). Its job is to break the tie in a " split-brain " scenario (when arrays lose connectivity with each other) to determine which array stays online.

Default Behavior: By default, every FlashArray is configured to use the Pure1 Cloud Mediator . This is a managed service provided by Pure Storage that requires no local infrastructure other than internet access from the array controllers.

On-Premises Mediator Deployment: Organizations that cannot use the Cloud Mediator (due to " dark site " security requirements or lack of reliable internet) can deploy the Pure Storage On-Premises Mediator as a small OVF/VM template.

Configuration at the Pod Level: Simply deploying the On-Premises Mediator VM and connecting the arrays to it at the array level is not enough for existing or new pods to switch automatically. In Purity, the mediator preference is a per-pod attribute .

When a pod is created or stretched, it inherits the default (Cloud).

To use the local mediator, the administrator must explicitly configure the pod to point to the On-Premises Mediator’s IP or DNS name. This is done via the CLI using purepod setattr --mediator < address > < pod-name > or through the Pod settings in the GUI.

Why Option C is incorrect: While an A record is necessary for DNS resolution, the prompt implies the mediator is already " deployed " and available. The most common reason it isn ' t being used is simply that the pod hasn ' t been told to look there instead of the default Cloud option.

In policy-driven data protection and disaster recovery architectures like Pure Protect //DRaaS, a " Business Policy " dictates the critical Service Level Agreements (SLAs) for your environment, such as your Recovery Point Objective (RPO), replication frequency, and retention schedules. These policies are then assigned to " Application Groups, " which act as logical containers for the specific virtual machines being protected and replicated to AWS.

As a fundamental safety mechanism built into the platform to prevent accidental exposure and SLA breaches, the system places a hard dependency lock on actively used policies. An administrator cannot delete a Business Policy if there are still Application Groups actively relying on it for their DR scheduling. To successfully delete the policy, the administrator must first modify all associated Application Groups and assign them to a different Business Policy, or completely remove the protection from those groups.

Here is why the other options are incorrect:

The administrator also needs DRaaS Cloud Admin access (C): The scenario explicitly states the user already has " DRaaS Global Admin access. " In the Pure Protect //DRaaS Role-Based Access Control (RBAC) model, Global Admin is the highest tier of privilege and has full rights to manage and delete policies. A lack of permissions is not the issue here.

The Business Policy is marked as the Primary Policy (B): While a policy might be a default or primary template, the actual hard restriction that prevents deletion in the software is active resource assignment (the Application Groups), not just a " Primary " label.