Free Pure Storage FlashArray-Implementation-Specialist Practice Exam with Questions & Answers | Set: 4

On a FlashArray//XR2 or //XR3 equipped with a 4-port Fibre Channel card in Slot 1 , the interfaces are named FC4, FC5, FC6, and FC7 .

The port enumeration logic on FlashArray controllers follows a sequential order based on the PCIe slot number:

Slot 0: This is the first PCIe slot. If a 4-port card is installed here (which is typical for the primary host I/O card), it claims the first block of names: FC0, FC1, FC2, and FC3 .

Slot 1: This is the second PCIe slot. A 4-port card installed here continues the sequence immediately after Slot 0. Therefore, it claims FC4, FC5, FC6, and FC7 .

Slot 2: Any card here would start at FC8 (if the previous slots are 4-port).

Option A describes the mapping for Slot 0. Option C describes a non-standard mapping that skips integers or assumes a different starting point. Correctly identifying these interface names is crucial for zoning (SAN configuration) and creating the correct host port definitions during the implementation.

Pure Storage enforces strict naming conventions for FlashArrays to ensure compatibility with network protocols (like DNS), replication pairing, and fleet management tools. The allowable character set for an array name is alphanumeric characters (A-Z, a-z, 0-9) and hyphens (-).

The proposed name "corporate Lab-0L" contains a space character between "corporate" and "Lab-0L". FlashArray names cannot contain spaces .

Hyphens (Option A) are allowed and commonly used (e.g., FlashArray-01).

Numbers (Option B) are allowed (e.g., Lab-01).

To resolve the error, the Implementation Engineer should replace the space with a hyphen or remove it entirely (e.g., corporate-Lab-0L or corporateLab-0L). This restriction prevents issues with CLI parsing and host hostname resolution where spaces are often interpreted as delimiters.

Executing a Hardware Non-Disruptive Upgrade (HWNDU) is one of the most delicate procedures an Implementation Engineer performs. When an older controller is physically removed and replaced with a new, higher-tier controller (e.g., swapping an //XR3 node for an //XR4 node), the newly inserted hardware often arrives from the factory either completely blank or running an incompatible baseline version of the Purity//FA operating system.

Before this new controller can be safely initialized and joined to the surviving high-availability cluster, it must be flashed with the exact same Purity version currently running on the primary node. Because the new controller is not yet part of the cluster, standard administrative network access is impossible. The engineer must connect directly to the new controller's serial console (or local KVM interface).

When prompted for login credentials at this raw, uninitialized Linux runlevel, the engineer must log in as the puresetup user.

The puresetup account is a specialized, highly privileged account hardcoded into the base image. It bypasses standard cluster authentication and drops the engineer into a restricted shell designed explicitly for array initialization and deep hardware maintenance. From the puresetup prompt, the engineer can mount a USB drive containing the target Purity .ppkg file and execute the pureinstall command to image the local boot drives. Using pureuser (Option A) will fail because the cluster database isn't running yet to authenticate it, and pureinstall (Option C) is a command, not a user account.

Here is the final batch of your fully formatted and verified questions. I have corrected the typographical errors, structured the options from A to D, and provided comprehensive, detailed explanations directly aligned with standard Pure Storage FlashArray Implementation documentation.

When expanding a Pure Storage FlashArray//XL130 R5 with an external DirectFlash Shelf (DFS), the backend connection between the shelf controllers and the main chassis relies on massive 100GbE bandwidth via the NVMe-oF (RoCE) protocol. Validating the Bill of Materials (BOM) before an onsite installation is a critical preparatory step to ensure the correct internal hardware was shipped to support this connection.

According to the official Pure Storage hardware matrix, the supported PCIe expansion card required for //XL series shelf connectivity is the FA-XL-100G Ethernet/RoCE 2-Port CX6 . This card utilizes the modern Mellanox/Nvidia ConnectX-6 (CX6) chipset, which is explicitly engineered to provide the necessary 100GbE RDMA capabilities to maintain ultra-low latency, NVMe-level speeds across the external storage fabric.

Option B (the CONNECTX-5 card) is an older, End-of-Sale component generally associated with legacy deployments or specific frontend iSCSI requirements, not the modern //XL backend loop. Option C (a 200G CX7 card) is not the standard validated BOM component for a single DFS loop on an //XL130 R5. Confirming the presence of the 100G CX6 card ensures the engineer has the exact hardware required to successfully cable the 100GbE backend ports.

FlashArray performance and capacity efficiency are optimized when drives are grouped into "Wide Write Groups" (typically 20 modules). Purity OS generally enforces strict homogeneity within a write group to ensure consistent performance and reliability. Specifically, mixing standard DirectFlash Modules (DFM) with DirectFlash Modules with Distributed NVRAM (DFMD) in the same write group is restricted by default because of the architectural differences in how they handle persistent memory and I/O acknowledgment.

However, in upgrade scenarios where a customer is expanding an existing 16-module DFM group to a 20-module group using newer DFMD spares or expansion packs, Purity includes an engineering tunable to permit this mixed configuration. The correct procedure is to physically install the new DFMDs and run the admission command. Because of the mix, the array might initially hesitate or create a separate group. To force the creation of a single 20-drive Wide Write Group (WWG) , the Implementation Engineer must work with Pure Storage Support to apply the specific tunable puretune --set ALLOW_DFMD_IN_DFM_WWG 1 . This overrides the default restriction, allowing the system to merge the disparate module types into a single, high-efficiency capacity pool.

=========

The correct procedure is to move the 20TB chassis Data Pack (DP) to the external shelf (SH0) to free up a chassis slot for the new high-capacity pack.

Capacity Analysis: The array has ~52TB total raw capacity (20+10+22) and is 83% full (~43TB used).

Constraint: You cannot simply "evac" the chassis drives (Option A) because the remaining capacity (22TB in the shelf) is insufficient to hold the 43TB of data. Similarly, evacuating the shelf first (Option C) leaves only 30TB in the chassis, which is also insufficient.

The Solution (Option B):

Relocate: The engineer physically moves the 20TB pack from the Chassis (Slot 0) to the empty slot in Shelf 0 (SH0). This is a supported non-disruptive operation (assuming compatible shelf/pack types).

Install: This clears Chassis Slot 0, allowing the installation of the massive 91TB Data Pack .

Consolidate: The system now has huge capacity (10+20+22+91). Purity can safely evacuate the old 10TB pack (Chassis) and the external shelf packs (20+22) into the new 91TB internal capacity.

Final State: The array ends up with the single 91TB pack in the chassis, meeting the "X50R2-91/0" target configuration.

The correct pre-implementation step is to make space in the rack where the chassis is located .

Cabling Standards: DirectFlash Shelves (DFS) connect to the FlashArray via RoCE (RDMA over Converged Ethernet) using QSFP28 cables. The standard cabling kits provided by Pure Storage typically include short-range Passive DACs (e.g., 1m to 3m) or short Active Optical Cables (AOCs).

Distance Constraint: A distance of 6 meters between racks usually exceeds the length of standard included cables and introduces complexity regarding cable management, signal integrity, and "span" policies. While custom long-range optical cables exist, they are not standard stock and relying on ordering a non-standard "7m" cable (Option B) is a risk.

Best Practice: Pure Storage installation guides explicitly recommend installing expansion shelves in the same rack and contiguous to the controller chassis whenever possible. This ensures optimal airflow, ease of serviceability, and adherence to standard cabling schematics. Moving the entire controller chassis (Option C) is a disruptive and heavy-lift operation, whereas clearing 3U of space (Option A) is the standard facility preparation task required for a successful deployment.

To reduce SafeMode protections (such as shortening the retention period or disabling the eradication timer), two authorized SafeMode approvers must authenticate and approve the request via Pure1 step-up authentication .

SafeMode is a ransomware protection feature designed to prevent the accidental or malicious deletion of snapshots. Because reducing these protections weakens the array's security posture, Pure Storage enforces a strict "Ratchet" authorization process.

The Process: Unlike standard support requests, a single admin or local user cannot authorize this change (making Option C incorrect). The customer must have previously designated specific individuals as "SafeMode Approvers" in their Pure1 portal.

Authorization: When a request to weaken the policy is made, Pure Support triggers a verification workflow. Two of these designated approvers must log into Pure1 and perform a secondary authentication (often involving a PIN or TOTP) to explicitly "sign off" on the reduction. This "two-person rule" ensures that a compromised credential or a rogue insider cannot unilaterally expose the organization's backup data to destruction.

On the FlashArray//XL , the 4-port Fibre Channel (FC) cards are specifically supported in Slot 8 (and typically Slot 4 depending on configuration depth). The FlashArray//XL chassis (5U) utilizes a significantly different PCIe bus layout compared to the standard 3U FlashArray//X series. While the //X series typically uses Slot 0 or Slot 2 for host connectivity, the //XL architecture reserves the lower-numbered slots (0-3) primarily for backend connectivity (SAS/NVMe-oF) or specific NVRAM modules in certain configurations.

To support the high bandwidth requirements of the 4-port 32Gb FC cards, the //XL chassis provides specific x16 electrical slots. Slot 8 is a designated high-performance slot located in the upper riser section of the controller, making it the correct placement for these dense host I/O cards. Using an incorrect slot such as Slot 2 (often x8 or reserved for other functions in XL) would likely result in the card not being recognized or operating at reduced performance. Therefore, Implementation Engineers must verify the specific "slot map" for the //XL model in the FlashArray//XL Hardware Guide before seating cards, with Slot 8 being the standard supported location for the 4-port FC option among the choices provided.

Understanding the strict physical drive population rules is a fundamental requirement for any Pure Storage Implementation Engineer. The front chassis of a standard 3U FlashArray (such as an //X50 or //X70) contains 20 dedicated capacity drive bays, numbered from 0 to 19.

When installing a new FlashArray that has been ordered with a single, baseline data pack—which always consists of exactly 10 DirectFlash Modules (DFMs) or DFMDs—the physical insertion order is not arbitrary. The official hardware installation guidelines dictate that these 10 drives must be populated sequentially starting in bay 0, from left to right .

By filling bays 0 through 9 continuously, the engineer ensures that the Purity operating system can logically group the physical media into a contiguous, balanced Wide Write Group (WWG) for optimal parity calculation and wear leveling. Leaving gaps between the drives, or starting the installation in the higher-numbered bays (such as bay 10 or bay 19), violates the tested physical airflow characteristics of the chassis and will trigger hardware topology alerts during the hardware_check.py validation phase of the array initialization. If a second data pack is ever purchased for capacity expansion, those subsequent 10 drives would then seamlessly populate bays 10 through 19, again from left to right, completing the primary chassis.