Which command should the Implementation Engineer run to set the maintenance tag?

During the lifecycle of a Pure Storage FlashArray, Implementation Engineers and storage administrators frequently perform hardware non-disruptive upgrades (HWNDU), capacity expansions, controller replacements, or network reconfigurations. Because the FlashArray is inherently designed to aggressively monitor its own hardware sensors and software states, these administrative actions will naturally trigger a cascade of critical alerts. If left unchecked, the array's Call Home feature will immediately dispatch these alerts to Pure Storage Support (automatically opening support tickets) and blast emails to the customer's IT Operations teams, causing unnecessary panic.

To cleanly suppress these automated alerts during a planned event, the Implementation Engineer must utilize the puremaintenance command-line suite within the Purity operating system. By executing the specific command puremaintenance schedule array --timeout < timeout > , the engineer successfully flags the entire storage array as being in an active maintenance window. The --timeout parameter is crucial, as it dictates exactly how long the maintenance window will remain open (e.g., 2h for two hours) before the array automatically reverts to its normal, fully alerting state. This acts as a built-in safety mechanism, ensuring that if an engineer forgets to manually remove the maintenance tag after the upgrade, the array will not remain indefinitely silenced and exposed to unreported future failures. The other options presented either use incorrect command syntax or reference non-existent Purity CLI tools.