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

FlashArray ActiveCluster is designed for synchronous replication between two FlashArray systems, enabling active-active configurations across two sites. This setup allows both arrays to serve I/O simultaneously, providing high availability and zero RPO (Recovery Point Objective). Each array in the ActiveCluster configuration maintains identical volume identities, ensuring seamless access for hosts regardless of the array they connect to. The configuration supports metro-area clustering, with a maximum round-trip latency of 11 milliseconds between arrays. Additionally, the Pure1 Cloud Mediator or an on-premises mediator is utilized to manage failover and prevent split-brain scenarios, eliminating the need for a third site or external gateway.

While ActiveCluster supports a two-site configuration, it does not support additional arrays within the same synchronous setup. For scenarios requiring protection across more than two sites, asynchronous replication solutions like ActiveDR™ can be employed. ActiveDR allows for asynchronous replication to a third site, providing broader disaster recovery capabilities.

Therefore, the maximum number of arrays supported in a single ActiveCluster configuration is two.

Opening a support case before starting the installation ensures timely assistance and coordination with support throughout the deployment process.

TheFlashArray//XLfeatures a5 Rack Unit (5U)chassis height.

This form factor represents a significant change from the standard FlashArray//X and //C series, which utilize a 3U chassis. The increase to 5U is engineered to support the massive performance and density requirements of the //XL platform.

Key Design Features:The 5U height accommodates:

Dual Controllers:Larger, high-performance controllers with increased airflow requirements.

40 DirectFlash Module Slots:Double the drive density of the 3U chassis (which holds 20), allowing for petabytes of effective capacity in the base unit.

4 Power Supplies:A 2+2 redundant power architecture.

9 PCIe Slots:Extensive I/O expansion for host and backend connectivity.

Airflow:Dedicated fan modules and thermal ducting to cool the high-wattage components (up to 3.5kW max power draw).

On a newFlashArray//XR4installation, the Implementation Engineer must run thecobalt_check.pyscript before executing puresetup newarray.

The FlashArray//XR4 represents a significant hardware architectural shift (internally codenamed or associated with the "Cobalt" platform generation). This platform introduces new PCIe layouts, NVMe backplanes, and controller components that require specific validation beyond the standard legacy checks. The cobalt_check.py script is a specialized hardware diagnostic tool pre-loaded on the manufacturing image of //XR4 controllers.

Its purpose is to verify that the specific hardware components of the R4 platform—such as the status of the internal NVMe interconnects, the correct population of the chassis, and the health of the new controller mainboard—are functioning within strict tolerances. Running this check ensures that the physical layer is 100% healthy before the Purity operating system attempts to initialize the database and claim the storage media. Option A (pureboot list) checks boot versions but not hardware health, and Option C (purehw list) is a general command that might not catch the specific low-level architectural issues the cobalt_check.py script is designed to identify on this specific generation.

Service clearance is a critical physical installation requirement to ensure that components (like controllers, fans, and drives) can be safely removed and replaced without obstruction.

For theFlashArray//XR4, the specific service depth requirements are:

Front Panel:216 mm (8.5 in.). This allows sufficient room to open the bezel, unlatch drives, and pull them out of the chassis.

Rear Panel:530 mm (20.9 in.). This larger clearance is necessary because the controllers themselves (which are long, heavy components) slide out from the rear of the chassis. The engineer needs enough space to fully extract the controller without hitting a wall or another rack door.

Adhering to these clearances prevents situations where a failed controller cannot be replaced because the rack is too close to a wall.

=========

The FlashArray//X20R4-LL (Low-Line) model is a specific configuration designed for lower capacity and power entry points. Unlike the standard //X or //XL models which can support fully populated chassis and shelves, the "Low-Line" configurations often come with strict hardware limitations regarding power draw and drive count. A known constraint for specific Low-Line chassis upgrades, particularly when moving to the X20R4-LL, is a limitation on the number of DirectFlash Modules (drives) supported due to the power supply unit (PSU) capacity or thermal design targeted for that specific SKU.

In this scenario, if the source array (X20R3) was populated with more drives than the target X20R4-LL supports—specifically more than 10 drives—the upgrade validation checks (such as those performed by the upgrade script or Purity health checks) will flag a failure. Even though the voltage readings are technically correct (indicating the PDUs are providing power), the check fails because the hardware configuration exceeds the supported power budget for that specific chassis model.

Implementation Engineers must verify the drive count of the source array against the specifications of the target "Low-Line" array during the planning phase. If the source array has 11 or more drives, the target hardware cannot be an LL model; it would require a standard model to support the additional power load of the extra drives. This check prevents the array from booting into a state where it might experience power contention or thermal shutdown under load.

=========

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.

FlashArrays require outbound HTTPS connectivity to reach Pure1 for log uploads, phone home, and remote assist. In many enterprise environments, direct internet access is blocked, and traffic must be routed through an HTTP/HTTPS proxy.

To configure this setting in Purity via the CLI, the correct command ispurearray setattr --proxyfollowed by the full proxy URL (including protocol and port). The setattr (set attribute) subcommand is the standard method for modifying array-wide configuration parameters like the array name, idle timeout, and proxy settings. The other command variations (puresetup proxy or purearray configure) are incorrect syntax for this specific operation. This configuration is often a critical step during the "Pre-Flight" or initial setup phase to ensure the array can "phone home" immediately upon deployment.

=========

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.

=========

On aFlashArray//XR2 or //XR3controller equipped with an optional Ethernet Mezzanine (EMEZZ) card, the additional ports are enumerated asETH6, ETH7, ETH8, and ETH9.

The port numbering logic on these controllers follows a strict sequence:

ETH0 and ETH1:Fixed onboard 1GbE Management ports.

ETH2 and ETH3:Fixed onboard 10/25GbE ports (often used for replication or iSCSI).

ETH4 and ETH5:Reserved or used by the first PCIe slot expansion (if populated with Ethernet).

ETH6 through ETH9:Assigned to theEthernet Mezzanine (EMEZZ)slot.

The EMEZZ is a specific internal slot distinct from the standard PCIe risers. When populated, the Purity operating system reserves the eth6–eth9 block for these interfaces. Options B and C are incorrect because they describe port ranges that would typically be assigned to PCIe expansion cards in Slot 1 or Slot 2 (e.g., eth10+), or they simply do not align with the hardcoded enumeration logic of the R2/R3 controller architecture. Correct identification of these interfaces is critical for configuring link aggregation (LACP) or assigning iSCSI IPs during the initial setup.