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

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.'

Purity Safety Mechanism: In Pure Storage Purity, volume resizing---specifically downsizing---is a destructive operation because it can lead to data truncation. To protect against human error (like the one described in the scenario), Purity automatically creates a 'pre-resize' snapshot of the volume before the change is committed.

The 'Destroyed' Snapshot: When a volume is shrunk, Purity generates a snapshot of the volume in its state immediately before the shrink operation. This snapshot is placed in the Destroyed (or 'Pending Eradication') bucket.

Recovery Process: To recover the data, the administrator does not simply 'resize back up' (Option C), as the data beyond the 1GB mark may have already been unmapped or treated as truncated by the host file system. Instead, the administrator should locate the auto-generated snapshot in the Destroyed volumes/snapshots section, 'recover' it to make it active again, and then either copy that snapshot to a new volume or overwrite the truncated volume from that snapshot.

SafeMode Integration: If SafeMode is enabled, these auto-generated snapshots are even more secure, as they cannot be manually eradicated before the timer expires, ensuring a guaranteed recovery point for accidental shrinks.

Why Option C is incorrect: Increasing the size of a volume back to 1TB (or 1PB) does not automatically restore the data that was logically removed or truncated when the volume was set to 1GB; the host file system would still see the data as corrupted or missing.

Understanding the Audit Log: In Purity, accountability and security are maintained through the Audit Log. This log captures every administrative action taken on the array, whether through the GUI, CLI, or REST API. It records who performed the action, what the action was (e.g., volume creation, host deletion), and when it occurred.

The CLI Command: The command pureaudit list is the specific CLI tool used to display these logs. By default, it lists events in chronological order, making it the perfect tool for an administrator to review 'shift change' activities.

Command Options: * pureaudit list can be filtered with flags like --user to see actions by a specific admin, or --start-time and --end-time to narrow down the 'previous shift' window.

Why Option C is incorrect: puremessage (accessed via puremessage list) is used to view Alerts and Notifications generated by the system (e.g., a failed drive or a high-temperature warning). While it tells you what the array did, it does not track what users did.

Why Option A is incorrect: This is not a valid Purity command syntax. Purity does not use double-dashes to 'pipe' or combine independent commands like pureaudit and puremessage in that manner.

Understanding Data Reduction Rate (DRR): DRR is a measure of the effectiveness of Purity's deduplication and compression algorithms. It compares the amount of data written by the host to the amount of physical space actually occupied on the flash media after these processes have occurred.

Calculation: $\text{DRR} = (\text{Deduplication} \times \text{Compression})$.

Understanding Total Reduction: The Total Reduction metric is a broader 'efficiency' value. It represents the ratio of the Total Provisioned (logical) space to the Physical space used.

The 'Thin Provisioning' Factor: The primary difference between these two numbers is Thin Provisioning.

FlashArrays are 100% thin-provisioned by default. If a customer creates a 100TB volume but the host only writes 1TB of data, the 'Total Reduction' will be massive because it counts all that unwritten, 'virtual' space as 'saved.'

The DRR, however, only looks at the 1TB that was actually written and calculates how well it was compressed and deduped.

Why Option C is incorrect: Both metrics generally account for the efficiency of snapshots. However, snapshots contribute to DRR through deduplication (since they share blocks with the source volume). The massive gap between DRR and Total Reduction is almost always mathematically attributed to the 'unwritten' space provided by thin provisioning.

Key Takeaway: If your DRR is 5-to-1 but your Total Reduction is 50-to-1, it means your data is compressing/deduping well, but you have also provisioned a significant amount of volume space that hasn't been written to yet.

On a Pure Storage FlashArray, 'System Space' is a specific GUI-reported metric. Purity has a predefined, hidden internal space budget---typically around 20% of the raw mapped capacity (which would be 2TB on a 10TB array)---reserved for internal array operations. This budget covers RAID/parity overhead, metadata, and reclaimable space (data from deleted volumes, snapshots, or overwritten blocks that are waiting for the backend garbage collection process to fully erase them from the flash chips).

Normally, this internal overhead stays below the 20% budget, and 'System Space' displays as 0.00 in the GUI. However, if an administrator deletes a massive amount of data at once, causing the reclaimable space to exceed that 2TB budget, the overflow is prominently displayed in the GUI as 'System Space.'

Here is why the other options are incorrect:

Virtual machines have not yet issued an unmap command (A): If a VMware VM deletes a file but the OS hasn't issued an UNMAP/TRIM command, the FlashArray is completely unaware that the data was deleted. Therefore, the array continues to report that capacity as standard Volume Space, not System Space.

More than 2TB of volume snapshots were destroyed (C): While destroying snapshots leads to reclaimable space, 'reclaimable space' (Option B) is the specific, correct Purity architectural term and metric that the system uses to calculate the internal budget threshold.

Understanding CRC Errors: CRC (Cyclic Redundancy Check) errors occur when the data received at a port does not match the checksum sent by the initiator or switch. In a Pure Storage environment, these are tracked per port and can be viewed via the CLI (purehw list) or the GUI.

Configuration vs. Hardware: While a failing SFP or a damaged fiber cable can cause CRC errors, they are a primary indicator of configuration mismatches in the SAN fabric. Common culprits include:

Port Speed Mismatches: Manually setting a port to 16Gbps when the switch is set to 'Auto' or 8Gbps.

Duplex Mismatches: Though rare in modern Fibre Channel, it is a classic Ethernet/iSCSI configuration error.

MTU Mismatches: In iSCSI or NVMe-oF environments, if the FlashArray is configured for Jumbo Frames (MTU 9000) but the switch or host is at MTU 1500, packet fragmentation or CRC-like errors/drops will occur.

Why Option A is incorrect: A blinking status LED on a controller is often part of normal operation (indicating heartbeat or activity). A solid amber LED would be an indicator of a hardware failure, not necessarily a misconfiguration.

Why Option C is incorrect: While latency spikes can be caused by misconfiguration (like incorrect MPIO settings), they are more commonly symptoms of workload changes, 'noisy neighbors,' or reaching the physical performance limits of the array. CRC errors are a much more specific diagnostic 'smoking gun' for port and fabric configuration issues.

Best Practice: When CRC errors are detected, Pure Storage recommends first checking the physical layer (reseating SFPs/cables) and then verifying that the port speed and protocol settings on the FlashArray match the upstream switch configuration exactly.

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.