Pass the Pure Storage FAIS FlashArray-Implementation-Specialist Questions and answers with ExamsMirror

When adding a second DirectFlash Shelf to aFlashArray//XL, the connectivity utilizesPCIe Slot 6(in conjunction with Slot 0).

FlashArray//XL Architecture:The //XL chassis distributes its backend NVMe-oF (100GbE RoCE) connectivity across two dedicated PCIe slots to ensure redundancy and maximum bandwidth. As established in hardware diagrams,Slot 0(lower riser) andSlot 6(upper riser) are the designated slots for the 2-port 100GbE backend cards.

Expansion Logic:

First Shelf:Typically connects to Port 0 of the card in Slot 0 and Port 0 of the card in Slot 6 (providing HA).

Second Shelf:Connects to the remaining ports (Port 1) on thesame cardsin Slot 0 and Slot 6.

Exam Context:In the context of "which slot must be used" for the expansion or specifically highlighting the secondary backend slot distinct from the primary host slots,Slot 6is the correct identifier for the backend expansion capability on the //XL. Options A (Slot 0) is the primary, but C (Slot 6) is often the specific answer required to demonstrate knowledge of the //XL's unique split-riser backend layout compared to legacy arrays.

The upgrade from a FlashArray//XR4 to a FlashArray//XL is a specific "Data-in-Place" hardware migration that utilizes thepurewes(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 ispurewes 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 commandonlyexecutes 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.

=========

TheFlashArray//XLrequires4 x C19/C20power cables to connect to the rack Power Distribution Units (PDUs).

The FlashArray//XL chassis (5U) is significantly larger and draws more power than the standard FlashArray//X series (3U). It is equipped with four high-capacity Power Supply Units (PSUs) to support the increased thermal and electrical load of the dense DirectFlash Modules and high-performance controllers.

Connector Type:To handle the higher amperage safely, the //XL utilizesIEC C20inlets on the chassis side (rectangular with horizontal pins) rather than the standard C14 inlets found on most servers. Consequently, the required cables must have aC19connector (female) to plug into the array and aC20connector (male) to plug into the PDU (assuming a high-power PDU).

Quantity:Since the chassis has four PSUs for N+2 redundancy, four distinct cables are required. The standard C13/C14 cables (Option A/B) used for lower-wattage IT equipment are physically incompatible and electrically insufficient for the //XL platform.

The upgrade from aFlashArray//X10 (or X20) to a FlashArray//X50requires a mandatorypower supply unit (PSU) upgrade.

While the FlashArray//X series utilizes a shared chassis design (3U) for models X10 through X90, the power requirements differ significantly between the entry-level and performance-tier controllers.

X10/X20:These models typically ship with1000W or 1200Wpower supplies, which are sufficient for their lower-power CPUs and component loads.

X50/X70/X90:These "Performance" class arrays utilize higher-wattage Intel Xeon processors and often support denser NVMe configurations, necessitating1600Wpower supplies to ensure stability and N+1 redundancy.

When a customer performs a Data-in-Place upgrade (swapping controllers) from an X10 to an X50, the existing chassis is retained, but the lower-capacity PSUs must be physically swapped for the high-capacity 1600W units to support the new X50 controllers. Conversely, upgrades like X50 > X70 (Option B) or R2 > R3 (Option C) typically occur within the same power tier, utilizing the existing 1600W PSUs.

FlashArray controllers operate in an Active/Active high-availability cluster. Each controller (CT0 and CT1) has its own physical IP address for hardware-level management. However, Purity configures aVirtual IP (VIP)that floats between the two controllers.

TheVirtual management IPis the recommended address for all administrative access, including the GUI, CLI, and API integrations. Using the VIP ensuresHigh Availability (HA)for management sessions. If an Implementation Engineer were to log in directly to CT0's IP and CT0 subsequently rebooted (e.g., during an NDU or failure), the management session would be disconnected.

By contrast, the VIP automatically fails over to the surviving controller (CT1) in the event of a disruption, allowing the management session (and the GUI) to remain accessible. This abstraction layer simplifies administration, as the user does not need to know which controller is currently "primary" for management tasks. Direct controller IPs are typically reserved for specific hardware troubleshooting steps where accessing a specific node is required.

=========

The FlashArray//XR4 utilizes onboard 100GbE RoCE (RDMA over Converged Ethernet) ports for connecting to the first loop of DirectFlash Shelves, removing the need for dedicated PCIe add-in cards for the base configuration. The port mapping for these onboard backend ports differs from previous generations.

On the //XR4 controller chassis, the specific Ethernet interfaces designated for thefirst DirectFlash Shelf loopare typically the high-numbered onboard ports. In this specific exam context and hardware revision,ETH 18 and ETH 19are identified as the correct primary backend connectivity ports .

Implementation Engineers must connect the QSFP28 cables from the "uplink" ports on the first shelf (IOM0 and IOM1) toETH18 and ETH19on the controllers (CT0 and CT1) respectively. Using incorrect ports (like ETH0/1, which are management) would result in the shelf not being detected by the storage fabric.

=========

Pure Storage DirectFlash Shelves (DFS) are designed with high-efficiency, enterprise-grade power supply units (PSUs). These PSUs are "auto-ranging," meaning they can accept a wide range of input voltages, typically from roughly 90V to 264V AC.

While data centers often prefer 208V-240V power sources for better efficiency (less heat loss and lower amperage draw for the same wattage), the hardware isfully validated and supported to operate on standard 110V/120V circuits. There is no "temporary only" restriction or hardware lockout that prevents operation on 120V.

Therefore, if the customer's high-voltage PDUs are full, the Implementation Engineer can safely connect the DirectFlash Shelf to the available 120V outlets. The shelf will function normally, provided the circuit has sufficient amperage capacity (amps) to handle the slightly higher current draw that results from using a lower voltage. This configuration is supported for the entire service life of the shelf.

=========

A FlashArray support case should be openedbefore 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 theFlashArray//XL,PCIe Slot 5is explicitly reserved forNon-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 5is 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.

The FlashArray//XL features a robust2+2power supply unit (PSU) redundancy configuration. Unlike the smaller FlashArray//X chassis (3U), which typically utilizes two power supplies in a 1+1 redundancy setup, the FlashArray//XL utilizes a larger 5U chassis designed for higher performance and density, requiring a more substantial power infrastructure.

The //XL chassis is equipped with four physical Power Supply Units. These are configured to operate in an N+2 mode (effectively 2+2), meaning the system requires two PSUs to support the full electrical load of the chassis, while the other two provide redundancy. This architecture allows the array to survive the simultaneous failure or loss of input power to up to two power supplies without any interruption to service.

This design ensures maximum availability even in scenarios where an entire power grid feed (A-side or B-side) fails, or if multiple hardware components malfunction simultaneously. Options A (1+1) applies to the standard //X series, and Option C (3+1) is not a supported configuration for the FlashArray//XL. The 2+2 design is critical for maintaining the "Always-On" reliability standards required for the mission-critical workloads that the //XL platform supports.