After upgrading Purity during a new installation, which command should an Implementation Engineer run to determine what version of Purity will be…

The pureboot list command is the correct tool for this task. After a Purity software upgrade, this command displays the Purity//FA environments that are installed on the controllers' boot drives. The output clearly indicates which environment is the current (running) version and, crucially, which is marked as the next version to be loaded upon the subsequent reboot. This allows the engineer to verify that the upgrade has been staged correctly and the intended version will be active after the next boot cycle.

A. purearray list --controller displays the status of the controllers, including the Purity version that is currently running, not the version staged for the next boot.

B. pureversion -a is not a valid command. The pureversion command, without arguments, shows the currently running Purity version on the array, not the next boot version.

1. Pure Storage FlashArray CLI Command Reference Guide: The guide details the pureboot command set. Specifically, pureboot list is documented as the command to "Display the Purity Run environments that are installed on the boot drive," showing which is designated as 'current' and 'next'. (Refer to the pureboot command section in any recent Purity//FA CLI Reference Guide).

2. Pure Storage Knowledge Base Article KB-1001, "How to Upgrade Purity": This type of procedural document outlines the upgrade steps, which include using pureboot list to verify the staged version before rebooting the controllers. It confirms this command is a standard part of the verification process post-upgrade and pre-reboot. (Specific article numbers may vary, but the procedure is standard).