Pure Storage FlashArray-Storage-Professional Practice Test Questions Answers

In any NVMe-based storage fabric (including NVMe/TCP, NVMe/FC, and NVMe/RoCE), the standard method for identifying endpoints and enforcing device-level access control is the NQN (NVMe Qualified Name) .

The NQN serves the exact same purpose in the NVMe protocol as an IQN (iSCSI Qualified Name) does in an iSCSI environment, or a WWPN (World Wide Port Name) does in a Fibre Channel environment. It is a unique identifier assigned to both the host (initiator) and the storage array (target subsystem). When setting up access control on a Pure Storage FlashArray, the storage administrator must capture the Host NQN from the operating system and configure a Host object on the array with that specific NQN. This ensures that only the authorized host can discover, connect to, and access its provisioned NVMe namespaces (volumes).

Here is why the other options are incorrect:

VLANs (A): Virtual LANs are used for network-level isolation and segmentation at Layer 2 of the OSI model. While you might use a VLAN to separate your storage traffic from your management traffic, it is a network security measure, not a device-level access control mechanism for the storage protocol itself.

LACP (C): Link Aggregation Control Protocol (LACP) is a network protocol used to bundle multiple physical network links into a single logical link for redundancy and increased bandwidth. It has nothing to do with storage access control or mapping volumes to hosts.

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.