A "4X Module" kit is specifically designed to widen an existing write group (RAID set).

Write Group Geometry: In standard FlashArray//X configurations, DirectFlash Modules (DFMs) operate in "Write Groups" (typically 10 modules wide for a standard data pack). However, to offer more flexible entry points or capacity expansion options, Pure Storage allows configurations that start with smaller write groups (e.g., 6 modules).

Widening: When a customer wants to expand capacity or performance on these smaller configurations without adding a full new 10-pack, they can purchase a widening kit (in this case, 4 modules).

Process: The Implementation Engineer installs these 4 modules into the empty slots. The Purity operating system then logically integrates these new drives into the existing narrow write group, "widening" it to the standard width (e.g., 6 + 4 = 10). This operation redistributes parity and data across the full set of 10 drives, improving performance and efficiency.

Standard enterprise data center power distribution units (PDUs) typically use C13 or C19 outlets. The FlashArray//X series power supplies utilize C14 inlets (the male connector on the chassis side). Therefore, the standard accessory kit included with a FlashArray//X ships with C13 to C14 power cables.

The C13 connector plugs into the array's power supply (matching the C14 inlet), and the C14 connector on the other end is designed to plug into a standard rack PDU (which typically has C13 outlets). This is the industry-standard "jumper cord" for rack-mounted server and storage hardware.

It is important for the Implementation Engineer to verify this during the pre-install phase. If the customer's facility uses non-standard PDUs (like those with C19 outlets or wall-style plugs), the standard kit cables will not fit, and the engineer must ensure the correct cables were ordered separately or provided by the customer. However, for the exam and standard BOM validation, the correct answer is the ubiquitous C13 to C14 cable type.

=========

The FlashArray//XL series has a specific, validated slot population rule for its PCIe cards to ensure optimal performance and thermal management. For a standard Fibre Channel (FC) configuration on a FlashArray//XLR5 , the factory default shipment includes a specific arrangement of host I/O cards and offload engines.

The correct default configuration is:

PCIe Slot 3: 4-Port 32Gb FC card.

PCIe Slot 5: 2-Port 32Gb FC card.

PCIe Slot 6: DirectCompress Accelerator (DCA).

This layout (Option B) adheres to the //XL's architecture where specific slots are prioritized for frontend host I/O (like slots 3 and 5) and others for offload functions or backend connectivity. Implementation Engineers must verify cards are in these exact slots during the visual inspection. If cards are moved to incorrect slots (like slot 1 or 4 for primary FC in this specific config), the array may not boot or may fail to initialize the FC services correctly due to BIOS enumeration orders.

=========

Data evacuation from a shelf is a sensitive background process where data is migrated off specific physical media to free it for removal. While the purearray evacuate command initiates the data movement, the finalization of the process—specifically the logical removal of the shelf object from the system configuration to allow for safe physical disconnection—often requires engineering-level commands or verification.

Therefore, before Pure Storage Support can log in to run these specific completion scripts or verification checks, the Implementation Engineer must Enable Remote Assist (RA) .

Remote Assist creates a secure, outbound SSH tunnel that allows Support to access the array remotely.

Without RA enabled, Support cannot connect to the array to execute the necessary puredrive or internal maintenance commands to mark the shelf as "vacated" and safe to unplug.

Powering off the shelf (Option B) before this step could result in data loss or an array outage if the system still believes data resides there.

=========

The FlashArray//XL platform features a split-chassis design with a unique PCIe bus layout compared to the standard //X series. To maintain optimal performance and redundancy, the backend connectivity for DirectFlash Shelves (DFS) must be balanced across the specific PCIe root complexes managed by the dual CPUs.

For a configuration involving multiple shelves (specifically targeting the logical shelf identifiers SH8 and SH9, which often correspond to the first pair of backend loops in an //XL deployment), the validated configuration is to use PCIe Slot 0 and PCIe Slot 6 . These slots are architecturally designated for the backend NVMe-oF (RoCE) fabric cards.

Using Slot 0 (typically located on the far left) and Slot 6 (located on the right side of the chassis) ensures that the I/O load is distributed across the internal midplane and CPUs correctly. Placing cards in incorrect slots (like Slot 1 or 7, which might be reserved for host I/O or inter-controller links) can result in shelf detection failures or performance bottlenecks where one CPU is overloaded with backend traffic while the other is idle.

=========

When new capacity (a data pack) is physically installed into a FlashArray, the drives are detected by the system but are not automatically added to the storage pool to prevent accidental data overwrites or configuration errors. They appear in an "unadmitted" state.

To logically add these drives to the array's capacity, the Implementation Engineer must explicitly admit them. The command to perform this action is purearray drive admit (or puredrive admit in some contexts, but purearray drive admit is the specific option provided and valid). This command triggers the Purity software to format the new drives, add them to the system's write groups, and begin rebalancing data across the expanded capacity. Without running this admission command, the drives will remain visible but unusable for storage.

=========

Understanding the hardware architecture and proper drive population rules is critical during a Pure Storage FlashArray installation. FlashArray models generally utilize either standard DirectFlash Modules (DFMs) or DirectFlash Modules with distributed NVRAM (DFMDs).

DFMDs, primarily introduced with models like the FlashArray//XL, integrate non-volatile write caching directly into the capacity drives themselves, eliminating the need for dedicated NVRAM hardware modules. However, standard FlashArray models—such as the //X10, //X20, //X50, //X70, and //X90—use standard DFMs strictly for capacity. Because standard DFMs do not contain built-in NVRAM, these arrays rely heavily on specialized, dedicated NVRAM modules to safely acknowledge incoming writes and protect data in flight against unexpected power loss or controller failures.

To maintain absolute high availability and guarantee there is no single point of failure within the write cache, NVRAM is always mirrored across two separate physical modules. During the physical hardware installation of a non-DFMD array, the Implementation Engineer must populate the dedicated NVRAM bays located centrally on the chassis. According to official Pure Storage implementation guidelines, the primary pair of NVRAM modules must always be installed in the first two designated bays, which are explicitly labeled NVB0 and NVB1. Placing the modules in alternate or staggered bays (such as NVB0 and NVB2) violates the strict hardware population rules and will prevent the array from initializing.