Pure Storage FlashArray-Implementation-Specialist Exam Questions

The pureinstall command is a low-level Purity operating system utility used strictly by Implementation Engineers and Pure Storage Support to install or upgrade the Purity//FA image on a controller's boot drive before the array is logically initialized.

When an Implementation Engineer unpacks a new FlashArray, the controllers may ship with a factory default version of Purity. If the customer's deployment requires a specific target version of Purity//FA (e.g., to match a fleet standard or enable a new feature), the engineer must boot into the controller via the local KVM/Serial connection and log in as the puresetup user. From here, they mount a USB drive containing the .ppkg firmware file and execute pureinstall purity-<version>.ppkg.

This process writes the new Purity operating system to the alternate boot partition. After executing pureinstall and rebooting the controller to boot from the new partition, the engineer then runs the puresetup newarray command (or puresetup secondary on the peer controller) to logically initialize the array, assign management IP addresses, and set the array name. Therefore, pureinstall must always be run prior to initialization.

DirectFlash Shelves (DFS) are populated with DirectFlash Modules (DFMs) or DFMDs (DirectFlash Module with Distributed NVRAM, though usually just DFMs in shelves). For the Gen 2 DirectFlash Shelf, Pure Storage offers specific 'starter packs' or partially populated configurations to allow for capacity flexibility while maintaining necessary performance and electrical balance.

The validated starter configurations for a Gen 2 DFS are 12-slot and 14-slot populations. This means the shelf must be populated with at least this number of drives to be a supported configuration. Populating fewer than this (e.g., 8 or 10) might result in insufficient bandwidth utilization across the shelf's internal fabric or fail strict configuration checks in the Purity operating system. Engineers must verify the drive count matches these supported increments during inventory to avoid configuration errors during initialization.

=========

The command to check I/O health and validate connectivity after a controller upgrade is purehost monitor --balance.

Following an upgrade (especially after a controller reboot or failover/giveback), it is essential to verify that the host Multipath I/O (MPIO) drivers have re-established connectivity to all paths.

purehost monitor: Displays real-time performance statistics (IOPS, Bandwidth, Latency) for connected hosts.

--balance: This specific flag breaks down the metrics per initiator (HBA port) for each host.

Why it's used: An Implementation Engineer uses this to look for 'imbalanced' flow. If one initiator shows high IOPS and another shows zero, it indicates a dead path, a zoning issue, or an MPIO driver that failed to recover the path to the upgraded controller. Options A and B provide static configuration lists (mappings and WWNs) but do not show live I/O flow, making them insufficient for health monitoring.

.

Capacity expansion on a Pure Storage FlashArray is a highly controlled, safe process. When an Implementation Engineer physically unboxes and inserts a new data pack (a group of DirectFlash Modules) into the available drive bays of a chassis or a DirectFlash Shelf, the Purity operating system detects the hardware instantly. However, it does not automatically wipe the drives and assimilate them into the global storage pool.

Instead, the newly inserted modules are placed into a safe, quarantined state known as 'unadmitted.' This intentional design choice prevents catastrophic data loss in the event that an engineer accidentally inserts a drive containing live data from another system, or inserts drives before the customer is financially or operationally ready to activate the new capacity.

To officially claim the drives, integrate them into the system's Wide Write Groups (WWGs), and initiate the background parity redistribution process, the Implementation Engineer must explicitly authorize their use. This is accomplished by running the puredrive admit command. The engineer can either specify the exact drives (e.g., puredrive admit CH0.BAY10 CH0.BAY11...) or use a global flag like puredrive admit --all if all unadmitted drives are ready for ingestion. Once admitted, the drives transition to a 'healthy' state, and the array's total usable capacity increases seamlessly without any host disruption.

To reduce SafeMode protections (such as shortening the retention period or disabling the eradication timer), two authorized SafeMode approvers must authenticate and approve the request via Pure1 step-up authentication.

SafeMode is a ransomware protection feature designed to prevent the accidental or malicious deletion of snapshots. Because reducing these protections weakens the array's security posture, Pure Storage enforces a strict 'Ratchet' authorization process.

The Process: Unlike standard support requests, a single admin or local user cannot authorize this change (making Option C incorrect). The customer must have previously designated specific individuals as 'SafeMode Approvers' in their Pure1 portal.

Authorization: When a request to weaken the policy is made, Pure Support triggers a verification workflow. Two of these designated approvers must log into Pure1 and perform a secondary authentication (often involving a PIN or TOTP) to explicitly 'sign off' on the reduction. This 'two-person rule' ensures that a compromised credential or a rogue insider cannot unilaterally expose the organization's backup data to destruction.