Pure Storage FlashArray-Storage-Professional Practice Exam Questions & Answers

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.

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.

What is SafeMode Ratcheting?: SafeMode is Purity's 'immutability' feature that prevents snapshots from being deleted, eradicated, or modified, even by an administrator with compromised credentials. Ratcheting is the process of increasing the protection levels (like extending the retention period) for a protection group (pgroup) to ensure even stricter data safety.

The Dependency on Local Snapshots: SafeMode's primary function is to protect point-in-time copies of data residing on the array. For a protection group to be 'ratcheted' into a SafeMode-protected state, it must have an active Local Snapshot Schedule.

Why Option C is the Constraint: If a protection group does not have a local snapshot schedule, there are no local snapshots being generated for SafeMode to 'lock.' SafeMode cannot protect what doesn't exist locally. While a pgroup might be used for replication only, SafeMode requires the local scheduling component to be active and configured to apply its immutable retention policies.

Why Option B is incorrect: Protection groups are designed to contain hosts, host groups, or volumes. This is the standard way to group related data for snapshot consistency and has no negative impact on SafeMode eligibility.

Operational Note: When you enable SafeMode on a protection group with a local schedule, the 'Erradicate' button for those snapshots is disabled. To 'ratchet' the protection, you typically work with Pure Storage Support to ensure the retention settings meet your compliance needs.

Understanding Space Reporting: To understand this behavior, you have to look at how Purity calculates capacity. Pure Storage uses a data reduction engine where data is deduplicated and compressed.

Volume Space vs. Shared Space:

Volume Space: This represents the unique data belonging to a specific volume that is not shared with any other volume via deduplication or snapshots.

Shared Space: This represents the data that is common across multiple volumes or snapshots. If you have two volumes that are clones of each other, most of that data is 'Shared.'

The 'Shift' Mechanism: When a volume is deleted (and potentially eradicated), the data it once shared with other volumes no longer needs to be 'shared.'

Imagine Volume A and Volume B share 100GB of data. That 100GB is accounted for in Shared Space.

If you delete Volume B, that 100GB of data is now only referenced by Volume A.

Consequently, that 100GB is moved from the Shared Space bucket into Volume A's Volume Space bucket.

Net Result: The total physical space used on the array remains the same initially, but the accounting shifts. You see a decrease in Shared Space and an identical increase in the Volume Space of the remaining volumes that held those deduplication references.

Requirement for Lossless Ethernet: NVMe over RoCE (RDMA over Converged Ethernet) requires a lossless fabric to function correctly. Unlike standard iSCSI which uses TCP for error recovery, RoCE assumes the network will not drop packets. If the network is 'lossy,' performance degrades significantly.

The Role of PFC: Priority Flow Control (PFC) (IEEE 802.1Qbb) is the specific mechanism used in Data Center Bridging (DCB) to provide flow control on a per-priority basis. It allows the switch to send a 'pause' frame to the sender when buffers are full, preventing packet drops.

Symptom Analysis: In the scenario provided, the array itself is not overloaded ('within the performance envelope'). However, the addition of a new workload increased traffic to the point where buffer congestion occurred. Because PFC was likely misconfigured (either on the FlashArray ports, the network switches, or the host NICs), the network dropped packets instead of pausing traffic. This leads to 'go-back-N' retransmissions and massive latency spikes that affect all workloads sharing that fabric.

Pure Storage Best Practices: Pure Storage documentation for NVMe-RoCE emphasizes that PFC must be enabled and consistent across the entire path. If there is a mismatch in PFC configuration, the resulting packet loss will cause the symptoms described: extreme latency and potential service outages.