FlashArray-Implementation-Specialist Exam Dumps : Pure Certified FlashArray Implementation Specialist (FAIS) Exam

The upgrade from a FlashArray//XR4 to a FlashArray//XL is a specific "Data-in-Place" hardware migration that utilizes the purewes (Pure Workflow Execution Service) utility to orchestrate complex steps. One of the most critical steps involves stopping the Purity software stack on the controller that is about to be removed (CT0) to ensure a clean failover and data flush to the surviving controller.

The correct command syntax is purewes controller disable --purity --verify-mode secondary --verify-array ARRAY_NAME ct0 .

purewes controller disable : Initiates the shutdown of the controller's services.

--purity : Specifies that the Purity software stack should be stopped (not just the hardware).

--verify-mode secondary : This is a crucial safety check. It ensures the command only executes if CT0 is currently the Secondary controller. If CT0 were Primary, running this command without a failover first would cause an outage.

--verify-array : Confirms the action is being taken on the correct target array.

This command sequence ensures the controller is safely quiesced before the Implementation Engineer physically removes it from the chassis.

=========

A FlashArray support case should be opened before starting the installation (Option C).

Proactive Support: Pure Storage advocates for a proactive support model. Opening a case (often categorized as an "Install" or "Planned Event" ticket) prior to the engineer arriving onsite or beginning the physical work serves multiple purposes:

Notification: It alerts Pure Support that a new array is about to come online.

Validation: It allows Support to verify the serial number, entitlement, and ensure the array is ready to receive the latest Purity updates or patches immediately upon connection.

Remote Assist: It establishes a placeholder for the "Health Check" phase. Once the physical install is done, the engineer can immediately reference this existing case number when enabling Remote Assist, allowing a Technical Support Engineer (TSE) to quickly jump in and perform the final validation without the delay of ticket creation and routing.

Waiting until an issue arises (Option A) is reactive, and waiting until completion (Option B) delays the mandatory sign-off process.

On the FlashArray//XL , PCIe Slot 5 is explicitly reserved for Non-Disruptive Upgrade (NDU) procedures and specific control plane functions.

The FlashArray//XL chassis (5U) features a redesigned controller layout with 9 PCIe slots per controller (numbered 0-8). While slots 0-3 and 6-8 are generally available for Host I/O (FC/iSCSI) or Backend Expansion (SAS/NVMe-oF), Slot 5 is kept open or populated with specific interconnect cards used during controller upgrades.

During a "Data-in-Place" upgrade (e.g., moving from an //X to an //XL or upgrading //XL generations), this slot facilitates the high-speed link required to cluster the old and new controllers or to transfer state information. Implementation Engineers must ensure this slot is not populated with standard customer I/O cards (like FC HBAs) during the initial configuration, as doing so would block the ability to perform future non-disruptive hardware upgrades.