Pure Storage FlashArray-Implementation-Specialist - Pure Certified FlashArray Implementation Specialist (FAIS) Exam

When adding a second DirectFlash Shelf to a FlashArray//XL , the connectivity utilizes PCIe 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) and Slot 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 the same cards in 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 6 is 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.

This scenario describes a physical layer mismatch between the FlashArray optics and the customer's switch infrastructure.

The PER (planning document) specified 10 Gb/s , so the Implementation Engineer likely installed 10 Gb SFP+ transceivers into the array.

The SAN Switch is operating at 40 Gb/s (likely using QSFP+ ports).

You cannot simply "force negotiate" a 10Gb SFP+ optic to run at 40Gb/s, nor can you plug a 10Gb SFP+ directly into a 40Gb QSFP+ port without specific breakout cables or QSA adapters that match the signaling. The physical transceivers themselves are incompatible with the link speed required by the switch.

To resolve this, the Implementation Engineer must replace the transceivers with the appropriate type .

If the switch is 40Gb native, the array needs 40Gb (QSFP+) optics (if supported on that slot).

Alternatively, if the customer intends to use 10Gb, they must provide 10Gb ports on their switch side.

Given the prompt implies the SAN is 40Gb, the 10Gb optics in the array are the incorrect hardware for that link.

=========

During the initial deployment phase of a FlashArray, the puresetup user is utilized to run the initial configuration scripts (setting IPs, array name, etc.). However, once the array initialization is complete and the Purity operating system is fully running, the puresetup account is effectively disabled or restricted from performing standard administrative tasks.

For all subsequent operations, including running final health checks, verifying services, and performing day-to-day management, the Implementation Engineer must switch to the pureuser account. This is the default administrative superuser for the FlashArray.

The pureuser account has full privileges to run commands like purearray list, pureadm list, and other validation tools required to sign off on the installation. The pureeng account is reserved strictly for internal Pure Storage Engineering use and is not available for standard implementation tasks. Therefore, attempting to log in as puresetup after the array is configured will often result in authentication failure or a restricted shell that does not allow for the necessary health validation commands.

=========

During the initialization phase of a new Pure Storage FlashArray, the Implementation Engineer executes the puresetup newarray (or puresetup array) command via a local serial console connection. This interactive script prompts the engineer for foundational network parameters, including the management IP addresses (vir0, eth0, eth1), subnet mask, default gateway, DNS servers, and NTP servers.

By default, the puresetup utility contains built-in safety mechanisms. As soon as the IP parameters are entered, the script actively attempts to ping the provided default gateway, resolve external hostnames via the provided DNS servers, and synchronize time with the NTP targets. If the customer's top-of-rack (ToR) switches are not yet configured, the cables are unpatched, or the array is being pre-staged in a lab completely isolated from the production network, these validation tests will inevitably fail, causing the setup script to hang or reject the configuration.

To intentionally bypass this validation and force the array to accept the network parameters without testing them, the Implementation Engineer must append the --skip-network-tests flag to the setup command. Executing puresetup newarray --skip-network-tests allows the system to save the configuration to the internal database and logically initialize the cluster. The array will bring the management interfaces online locally, allowing the engineer to connect via the GUI or SSH as soon as the physical network is eventually plugged in and routed.

When upgrading from a FlashArray//X to a FlashArray//XL, the hardware migration often involves handling DirectMemory Modules (DMMs) differently than standard data drives. DMMs are high-performance cache modules that reside in the controller chassis.

In this specific scenario—migrating a fully populated //X90R3 to an //XL that already has its own set of DirectFlash Modules (DFM-Ds)—the DMMs from the old chassis need to be moved to the new chassis to preserve their cache function or be properly decommissioned.

The correct procedure is to Evacuate DMMs as a datapack then install into any slot in //XL .

DMMs cannot be simply "hot-swapped" randomly while the system is live in a way that disrupts the cache map.

They must be logically grouped and evacuated (conceptually "vacated" of active data) so they can be safely removed from the old chassis.

Once removed, they can be installed into the new //XL chassis. The //XL architecture supports DMMs in specific slots, and Purity will detect and re-incorporate them into the cache pool.

This ensures that the expensive SCM (Storage Class Memory) hardware is reused in the new system without causing data integrity issues during the transition.

=========

FlashArray File Services (FA File) brings unified block and file storage capabilities directly into the Purity operating system, allowing customers to provision high-performance SMB and NFS shares alongside their traditional Fibre Channel and iSCSI volumes.

Once the initial FA File networking (Virtual Interfaces) and DNS/Active Directory integrations are configured, the Implementation Engineer must actually create the file structures for the customer. In the Pure Storage Purity GUI, the logical hierarchy for file storage requires the administrator to first create a "File System," which acts as the top-level container, and then create "Directories" within it that will be exported to clients.

To manage, create, or modify these directories, the Implementation Engineer must navigate through the left-hand navigation pane to Storage > File Systems . Clicking into a specific File System reveals the "Directories" tab. From this central pane, the engineer can create new managed directories, apply specific export policies (defining which IPs or users have read/write access), and configure directory-level snapshot schedules. Option B (Settings > Access > Directory Services) is a common distractor, but that menu path is used exclusively for configuring the array's connection to Active Directory or LDAP for administrative login authentication, not for managing storage directories.

When unpacking and installing a new Pure Storage FlashArray controller, the initial configuration—such as assigning management IP addresses, subnet masks, and gateways via the puresetup utility—must be done completely out-of-band. Because the array does not yet have an IP presence on the customer's network, the Implementation Engineer must connect directly to the controller's serial console port using a standard serial-to-USB adapter and terminal emulation software (such as PuTTY, SecureCRT, or Tera Term).

To successfully establish a readable CLI session with the custom Linux microkernel running on the FlashArray controllers, the terminal emulator must be configured with the exact serial communication parameters expected by the array. According to Pure Storage hardware documentation, the mandatory COM port settings are:

Baud Rate (Speed): 115,200

Data Bits: 8

Parity: None (N)

Stop Bits: 1

Flow Control: None

This configuration is universally abbreviated as 115200 8-N-1 . If an engineer attempts to use older standard speeds (like 9600 or 38400 baud) or leaves flow control (like Xon/Xoff or RTS/CTS) enabled, the terminal window will display unreadable, garbled characters (often referred to as "wingdings"), or the keyboard inputs will fail to register entirely, preventing the initialization of the array.

The puresupport command suite is used to manage and verify the connectivity between the FlashArray and Pure Storage Support (Pure1). Specifically, to test the Remote Assist functionality—which allows Pure Support to securely log in to the array for troubleshooting—the correct command is puresupport test.

While phonehome is a related concept (sending logs out), Remote Assist is a distinct inbound tunnel feature. purearray test pinghome is often confused with phonehome but is an older or specific test for the log sender. The puresupport test command runs a comprehensive check of the support channel connectivity, including the ability to establish the Remote Assist tunnel. If this test passes, the Implementation Engineer can be confident that Support can access the array if needed during or after the deployment.

=========

When performing a standard installation on a FlashArray, the first logical configuration step is the CT0 configuration (typically via the puresetup utility on the primary controller).

Workflow: After the physical rack-and-stack, cabling, and power-on, the Implementation Engineer must establish a management connection to the array. This is done by connecting to the serial console or the default IP of Controller 0 (CT0) .

Initialization: The puresetup process on CT0 initializes the system, sets the management IP addresses (VIP, CT0, CT1), and configures the gateway/DNS. This step effectively "builds" the array cluster.

Why not C? While ensuring the array is on the target code version is critical, a "Code Upgrade" is typically performed after the array is initialized and network-accessible (or via the Pure1 SSU workflow). The only exception is a manual USB re-image for a factory reset, but the standard installation procedure defines Configuration/Initialization as the primary step to bring the system online. Configuration of CT1 (Option B) happens automatically as part of the cluster creation initiated from CT0.