FlashArray-Implementation-Specialist Pure Certified FlashArray Implementation Specialist (FAIS) Exam Question and Answers

To determine the specific model of a replacement controller while in the puresetup or manufacturing shell (before the controller has joined the cluster), the correct command ishwconfig --model.

During a controller replacement procedure, the engineer often connects to the new controller via serial or a temporary IP. At this stage, the full Purity CLI (and thus purearray list) may not be fully available or relevant because the controller is in a "setup" or "unconfigured" state.

hwconfig: This is a lower-level utility used to read the Field Replaceable Unit (FRU) data directly from the hardware VPD (Vital Product Data).

--model: This flag specifically filters the output to display the model string (e.g., FA-X50R3-CT0). Verifying this string is a critical safety step to ensure the replacement hardware matches the existing cluster node before attempting the software join process (puresetup replace).

TheFlashArray//XR2 and //XR3(representing the FlashArray//X generation) utilize a standardized3U(3 Rack Units) chassis form factor.

This 3U chassis is the foundation for the majority of the FlashArray//X line, including the //X10, //X20, //X50, //X70, and //X90 models. It is designed to be compact while providing sufficient airflow and space for the dual controllers, two data packs (up to 20 DirectFlash Modules), and power/cooling infrastructure.

Dimensions:Approximately 5.12 inches (13 cm) in height.

Rack Layout:Implementation Engineers must reserve 3U of contiguous space for the base controller chassis. If expansion shelves are included, they typically require an additional 2U each (for SAS or NVMe shelves).

Option B (4U) is not a standard height for current Pure Storage arrays. Option C (5U) refers to theFlashArray//XL, a larger, performance-optimized platform designed for maximum scale and density, which uses a significantly taller chassis to accommodate more expansion slots and power components. Therefore, for the specified R2/R3 X-series, 3U is the correct height.

The correct pre-implementation step is tomake 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 of6 metersbetween 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 thesame rackand 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.

Verifying external connectivity is a critical final step in any maintenance window to ensure the array remains supported. The commandpuresupport testis the specific tool designed to validate the entire support communication chain.

Running puresupport test:

Checks DNS resolution for Pure1 endpoints.

Tests outbound HTTPS connectivity through any configured proxies.

Verifies the "Phone Home" log upload capability.

Validates the "Remote Assist" tunnel functionality.

This comprehensive check confirms that the array can "call home" if an issue arises and that Support can connect remotely if needed. purearray test is generic or refers to internal tests, whereas puresupport test explicitly targets the support infrastructure.

The FlashArray//XL series (such as the XL130R5) utilizes a modern backend connectivity architecture for its expansion shelves, specifically the DirectFlash Shelf (DFS). Unlike older generations that might have used SAS (Serial Attached SCSI) for shelf connectivity, the //XL architecture relies on high-speed Ethernet with RoCE (RDMA over Converged Ethernet) to communicate with external media shelves. This ensures that the NVMe drives in the shelf perform with the same low latency as those in the head unit.

To attach a DirectFlash Shelf to a FlashArray//XL130R5, the chassis must be populated with specific PCIe interface cards designated for shelf back-end connectivity. The correct part for this is theFA-XL-100G Ethernet/RoCE 2-Portcard. This card provides the necessary 100 Gigabit Ethernet bandwidth and RoCE protocol support required for the NVMe-oF (NVMe over Fabrics) backend fabric that Pure Storage uses.

It is crucial to distinguish this from host-facing cards. While an "iSCSI/RoCE" card exists, the shelf connectivity specifically utilizes the "Ethernet/RoCE" designation in the BOM to differentiate backend fabric ports from frontend host ports. The 200G options are generally reserved for host connectivity or inter-array clustering in specific high-performance setups, but the standard validated card for connecting the DFS to the //XL130R5 is the 100G Ethernet/RoCE adapter. Verifying this line item on the BOM prevents onsite delays where the engineer might otherwise find themselves with incompatible ports for the expansion shelves.

Upgrading from a FlashArray//X to a FlashArray//XL involves a significant architectural change, often requiring a data migration or a specific "chassis replacement" workflow known as a Data-in-Place upgrade where the new chassis temporarily acts as an expansion shelf. In this specific procedure, the new FlashArray//XL chassis is not immediately populated with its final drives (DFMDs) before power-on because it first needs to be configured to accept data or join the cluster in a controlled state.

The procedure requires the Implementation Engineer to boot the FlashArray//XL chassis first and configure it intoShelf Mode (SPM). Onlyafterthe chassis is successfully running in this mode—effectively acting as a passive SAS/Ethernet attached shelf to the existing controllers—are the DirectFlash Modules (DFMd) inserted.

Inserting them earlier could cause the array to attempt a full boot sequence or initialize a new array instance, complicating the upgrade logic. By waiting until Shelf Mode is confirmed, the engineer ensures that the modules are recognized correctly as part of the migration target resources, allowing Purity to manage the layout and data redistribution correctly from the source array.

=========

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.

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).

When performing a standard installation on a FlashArray, the first logical configuration step is theCT0 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 ofController 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 performedafterthe 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 definesConfiguration/Initializationas the primary step to bring the system online. Configuration of CT1 (Option B) happens automatically as part of the cluster creation initiated from CT0.

Monitoring the health and status of physical hardware components is a key task during upgrades and daily administration. While the FlashArray GUI provides a visual representation, the CLI offers granular detail.

To view the specific installation status, firmware version, and health of the NVRAM modules, the correct command ispurehw list --all.

purehw: This command suite is dedicated to reporting on the physical hardware components (fans, power supplies, temperature sensors, and NVRAM).

--all(or listing specific types) ensures that internal components like the NVRAM modules are displayed in the output.

The output will show the "Status" (e.g., ok, installing, updating), which is critical during a Purity upgrade or hardware replacement to confirm that the NVRAM firmware is being applied or that a new module has been successfully integrated.

puredrive list is strictly for the storage media (SSDs/DFMs), and purearray list shows high-level system info (name, ID, capacity) rather than component-level health.

=========

In the architectural evolution from FlashArray//XR2 and //XR3 to the FlashArray//XR4, Pure Storage made significant changes to the controller's rear panel and I/O design to accommodate higher performance and PCIe Gen 4 capabilities. One of the most critical changes for an Implementation Engineer to plan for during a hardware Non-Disruptive Upgrade (NDU) is the removal of the onboard, default iSCSI ports that were present on previous generations.

On //XR2 and //XR3 controllers, there were onboard Ethernet ports often used for iSCSI host connectivity without requiring a discrete PCIe adapter. However, the //XR4 controller design removes these dedicated onboard iSCSI ports to streamline the motherboard design and shift host I/O strictly to PCIe add-in cards. The //XR4 retains onboard ports specifically for Management (Mgmt) and Replication connectivity,ensuring that administrative access and array-to-array replication can still be maintained without additional hardware.

Consequently, if a customer was relying solely on the onboard ports for iSCSI traffic on their legacy //XR2 or //XR3, the Bill of Materials (BOM) for the upgrade to //XR4 must include discrete Ethernet/iSCSI PCIe cards to migrate those connections. Failure to identify this architectural difference during the pre-upgrade inventory can result in a loss of host connectivity or an inability to cable the new controllers correctly, as the expected physical ports simply will not exist on the new chassis.

=========

The FlashArray//XR2 and //XR3 architectures utilize dedicated NVRAM modules to provide the non-volatile write cache necessary for acknowledging writes safely before they are destaged to flash. These chassis are equipped with multiple NVRAM bays (labeled NVB0 through NVB3).

For standard configurations, specifically the //X10, //X20, and //X50 models, the system requires a redundant pair of NVRAM modules to function. These arealways installed in NVRAM bays 0 and 1.

Bays 0 and 1form the primary high-availability pair. If one fails, the other retains the data, and the system can continue to operate (though often in write-through mode or with alerts).

Higher-end models like the //X70 and //X90 populate all four bays (0-3) to provide the larger write buffer required for their higher throughput capabilities.

However, since the question asks which bays arealwayspopulated (i.e., the minimum requirement for the platform to function across the board), the answer is the foundational pair in slots 0 and 1. An Implementation Engineer must ensure these specific slots are populated first during any chassis maintenance or upgrade.

=========

The Purity upgrade process involves two main phases: installing the software image (placing the bits on the boot drive) and then activating it (booting into the new kernel).

After the pureinstall command has successfully unpacked and staged the new Purity version, the changes are not live until the system reboots. In a Non-Disruptive Upgrade (NDU), this is done one controller at a time.

The required step to commit and run the new version is toReboot the controller.

The pureinstall workflow typically prompts for or automatically initiates this reboot.

The secondary controller reboots first, loads the new Purity version, and rejoins the cluster.

Then, the primary controller fails over services to the updated secondary, reboots, and updates itself.

A full "Reboot the array" (simultaneous reboot) would be disruptive and is not the standard procedure for an NDU. "Logging out" has no effect on the system state.

To validate that I/O traffic is correctly distributed across a host's initiators (Fibre Channel WWNs or iSCSI IQNs), the correct command ispurehost monitor --balance.

Ensuring "multipathing balance" is a critical post-installation check. If a host is configured correctly with Multipath I/O (MPIO) software (like DM-Multipath on Linux or MPIO on Windows), read/write requests should be distributed relatively evenly across all active paths to the storage array.

Command Function:The purehost monitor command provides real-time performance statistics for hosts. Adding the --balance flag switches the view to a granular breakdown of IOPS and Bandwidthper initiatorfor the specified host.

Interpretation:An Implementation Engineer looks for initiators showing 0 IOPS or significantly lower traffic than others, which would indicate a path failure, zoning issue, or incorrect MPIO policy (e.g., Failover Only instead of Round Robin). Options A and B are incorrect syntax; purehost list shows configuration (not real-time stats), and iobalance is not a valid Purity command argument.

Upon verifying that a hardware upgrade is successfully completed and the system is stable, the command to remove the maintenance suppression ispurealert untag --maintenance.

During upgrade activities, engineers often apply a "maintenance" tag or flag to the alert system to prevent the generation of "noise" (false positive alerts) that would otherwise be triggered by expected events like controller failovers, link downs, or path fluctuations. This suppression ensures that the customer and Pure Support are not flooded with critical tickets for planned work.

Once the work is done, it is critical to remove this suppression so the array resumes normal monitoring. The purealert command with the untag verb and the specific --maintenance flag is the correct syntax to clear this state. Options A and C use invalid syntax (--cancel or --unset) that is not recognized by the Purity CLI for this specific alert management function. Failing to run this command leaves the array in a state where genuine failures might be masked, violating the "Always-On" monitoring standard.

The FlashArray//E (and the //XR4/R5 family) utilizes a modern architecture that moves away from the dedicated NVRAM modules found in legacy generations (like the //XR2 and //XR3). In those older systems, NVRAM was housed in specific PCIe cards plugged into the chassis.

In the FlashArray//E architecture, the Non-Volatile RAM (write buffer) functionality isDistributeddirectly onto the storage media itself. These specialized drives are calledDFMDs(DirectFlash Modules with Distributed NVRAM).

By integrating the NVRAM into the DFMs, the array scales its write buffer cache linearly with capacity and removes the bottleneck of fixed NVRAM slots in the chassis. This allows for higher density and simplified hardware designs. During installation or inventory, engineers must distinguish between standard DFMs (which store data only) and DFMDs (which store data and act as the write cache), ensuring the correct number of DFMDs are present to form the system quorum.

=========

When installing thefirst DirectFlash Shelf (DFS)on aFlashArray//XR2 or //XR3utilizing the onboard or default mezzanine connectivity, the correct ports to use areETH6 and ETH9.

Hardware Layout:The FlashArray//XR2 and //XR3 utilize a specificEthernet Mezzanine (EMEZZ)slot for backend connectivity to NVMe-oF shelves. This card typically enumerates its ports as ETH6 through ETH9 (a 4-port configuration).

Cabling Rule:To maximize physical separation and ensure redundancy across the internal ASIC lanes of the mezzanine card, standard cabling procedures for thefirstshelf dictate using the outer ports:ETH6(Port 0) andETH9(Port 3).

Redundancy:This configuration (Port 0 and Port 3) is preferred over using adjacent ports (like 6 and 7) to reduce the risk of a single lane cluster failure affecting both connections to the shelf. The second shelf, if added later, would typically utilize the remaining ports (ETH7 and ETH8).

The Pure Engagement Request (PER) or Implementation Workbook (IWB) is the planning document where customers specify their desired configuration parameters. Validating these parameters against Purity requirementsbeforearriving onsite is a critical step for the Implementation Engineer.

Regarding the array name "123":Array names cannot start with a digit.

Purity naming conventions follow standard DNS hostname RFC guidelines to ensure compatibility with network services and scripts.

While numbers are allowedwithinthe name (e.g., array123), the first character must be a letter.

A name composed entirely of numbers (like "123") or starting with a number (like "1array") can cause ambiguity for parsers that might mistake the name for an IP address, a specific ID, or an integer value in scripts.

The engineer must flag this in the PER and request the customer provide a compliant name (e.g., flasharray-123) to avoid errors during the puresetup initialization process.

TheFibre Channel (FC)I/O card type is the only option listed that is universally compatible and supported acrossallFlashArray models, from the entry-level //X10 and //X20 up to the high-end //X90 and //XL.

Fibre Channel:Pure Storage architectures rely heavily on Fibre Channel as the primary enterprise storage protocol. All chassis generations and controller sizes feature PCIe risers compatible with Pure's standard 16Gb or 32Gb Fibre Channel HBAs.

Ethernet/iSCSI:While all arrays support iSCSI, the physicalcard typevaries.

10GBase-T:This refers to "copper" Ethernet (RJ45). This card type isnotsupported on all models. High-end FlashArrays (like the //X70, //X90, and //XL) typically utilize SFP+ or QSFP28 cages for optical connectivity (10/25GbE or 40/100GbE) and do not standardly support 10GBase-T copper cards due to power and latency characteristics.

Therefore, while theprotocol(iSCSI) is supported everywhere, the specific physicalcard(10GBase-T) is not. Fibre Channel cards remain the consistent hardware constant across the entire product line.

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 FlashArray//XL is a high-performance, 5U storage system designed for massive scale and throughput. To support its powerful processors and high-density DirectFlash modules, the chassis is equipped withfourPower Supply Units (PSUs).

Consequently, the installation requires4 power connections. Each PSU must be connected to a power source to ensure full redundancy and load sharing. Best practice dictates distributing these four connections across two independent Power Distribution Units (PDUs) (e.g., PSUs 1 & 3 to PDU A, PSUs 2 & 4 to PDU B) to survive the loss of a single power feed or PDU failure without interrupting array operations.

This is a key differentiator from the smaller 3U FlashArray//X models, which typically require only two power connections (one per PSU). Implementation Engineers must ensure that the rack has sufficient outlets (4 for the //XL chassis alone, plus additional outlets for any shelves) before beginning the physical installation.

=========

When performing a Hardware Non-Disruptive Upgrade (HWNDU) or preparing for a Purity software upgrade, the Implementation Engineer must log in with a user account that has full administrative privileges to execute upgrade commands, run health checks, and manage the array state.

Thepureuseraccount is the standard administrative superuser for the FlashArray. It is used for all day-to-day administration and maintenance tasks, including initiating upgrades via the CLI (pureinstall or pureupdate commands) and verifying system health (purearray health, pureadm list). The puresetup account is strictly for initial array initialization (setting IPs and array name) and is disabled or restricted once the array is up and running. pureinstall is a command, not a user account. Therefore, pureuser is the correct authenticated session required to manage the upgrade process.

=========

The status "unrecognized" on a drive module typically indicates that the physical hardware is detected by the chassis midplane, but the operating system (Purity) does not have the necessary driver definition or firmware logic to interact with it.

This most commonly occurs when newer generation DirectFlash Modules (e.g., larger capacity drives or newer NAND revisions) are inserted into an array running an older version of Purity. The hardware identifier of the new drive is unknown to the older software .

To resolve this, the Implementation Engineer must verify thePurity Compatibility Matrixfor the specific drive part number. The array will likely need a Purity software upgrade to a version that supports the new media before the drives can be successfully admitted and used. It is rarely a hardware fault (which would show as "failed" or "missing") or a capacity limit (which would prevent admission but usually identify the drive correctly).

=========

TheFlashArray//Econnects to its DirectFlash Shelves (DFS) using25Gb Ethernet (RoCE).

The FlashArray//E is the "Capacity Optimized" member of the FlashArray family, designed to replace spinning disk repositories with all-flash efficiency. While the high-performance FlashArray//XL utilizes 100GbE for its backend NVMe-oF connectivity to maximize throughput for mission-critical databases, the //E prioritizes cost-efficiency, density, and power consumption.

Architecture:To maintain this efficiency balance, the backend connectivity for expansion shelves on the //E platform is standardized on25GbE. This provides ample bandwidth for the QLC-based workloads (typically unstructured data, repository, or Tier 2 block) without the higher cost and power draw of 100GbE optics and controllers.

Comparison:Option A (40G) is a legacy QSFP standard not used in modern Pure backend designs. Option C (100G) is reserved for the performance-tier //XL and high-end //X models.

To initiate a Purity Operating Environment (OE) software upgrade from the Command Line Interface (CLI), the correct command ispureinstall.

pureinstall: This command manages the upgrade workflow. It typically takes an image file (ISO) as an argument or downloads it from the repository, unpacks it, performs pre-flight checks, and then applies the update to the controllers in a non-disruptive rolling fashion.

purereboot is used to restart a controller or the array but does not install software.

puresetup is used for the initial configuration of network settings and array names, not for software updates.

=========

At the completion of an upgrade, the correct command to manually trigger the upload of the relevant logs ispurearray phonehome --send-today.

Purpose:This specific argument (--send-today) instructs the array to bundle and upload all log files generated within the current 24-hour window. This is the standard procedure post-upgrade because it ensures that all logs capturing the pre-upgrade state, the upgrade process itself, and the immediate post-upgrade health checks are transmitted to Pure Support.

Verification:This allows the Support team to validate that the upgrade completed successfully and that no dormant issues were triggered during the controller failovers.

Syntax:Option A (purelogs) is not a valid command. Option B (--send-logs) is a generic approximation, but the specific "today" flag is the best practice command cited in upgrade checklists to avoid uploading gigabytes of historical data irrelevant to the immediate event.

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

ThePER(planning document) specified10 Gb/s, so the Implementation Engineer likely installed10 Gb SFP+ transceiversinto the array.

TheSAN Switchis operating at40 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 mustreplace 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 SANis40Gb, the 10Gb optics in the array are the incorrect hardware for that link.

=========

The puresupport command suite is used to manage and verify the connectivity between the FlashArray and Pure Storage Support (Pure1). Specifically, to test theRemote Assistfunctionality—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.

=========

The correct procedure is tomove 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 massive91TB 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.

ForPhoneHome(telemetry) andRemote Assist(support tunnels) to function correctly,TCP Port 443 (HTTPS)must be open for outbound traffic from all management ports (CT0.ETH0, CT1.ETH0, and the Virtual Management IP).

Pure Storage utilizes a secure, encrypted connection to communicate with the Pure1 Cloud and Support infrastructure.

PhoneHome:The array sends logs and heartbeat data to purestorage.com (and associated subdomains) via HTTPS over Port 443. If this port is blocked, the array cannot report its health status, preventing proactive support.

Remote Assist:This feature creates a reverse SSH tunnel encapsulated over HTTPS (websocket or similar secure transport) to allow Pure Support to remotely log in. It initiates the connectionoutboundto the support relay servers on Port 443.

Option A (Port 80) is generally not used for secure management traffic in modern configurations, often only serving as a redirect. Option C (Port 123) is required for NTP (Network Time Protocol) synchronization, which is critical for logs but is not the transport port for the PhoneHome/Remote Assist data stream itself. Therefore, verifying firewall rules for Port 443 is the primary troubleshooting step.

On aFlashArray//X20 (R2 or R3), the default Fibre Channel configuration is a2-port FC card installed in Slot 2.

The FlashArray//X hardware architecture differentiates slot usage based on the controller model:

Entry Level (X10/X20):These controllers have a limited number of PCIe lanes and slots available for user expansion. Slots 0 and 1 are often utilized by internal system components or reserved. Therefore, the primary Host I/O card (FC or iSCSI) is standardly installed inSlot 2. Additionally, due to the entry-level positioning, the 2-port card is the standard default (though 4-port is supported).

Performance Level (X50/X70/X90):As seen in previous questions, these models prioritizeSlot 0for Host I/O and typically default to4-portcards.

The distinction is critical for Implementation Engineers to ensure they are cabling the correct ports. For an X20, cabling Slot 0 (if a port is even visible) would be incorrect; the active host ports are in Slot 2.

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.

=========

On aFlashArray//XR2 or //XR3, if a dedicatedPCIe SAS HBA(Host Bus Adapter) is required for external shelf connectivity (expanding beyond the onboard SAS ports), it must be installed inSlot 1.

The PCIe slot prioritization on the FlashArray//X R2/R3 controllers is strictly defined to ensure optimal performance and lane distribution:

Slot 0:Reserved primarily for frontend Host I/O cards (Fibre Channel or iSCSI/Ethernet). This slot usually connects to CPU 0 and offers high bandwidth for host traffic.

Slot 1:Designated as the primary expansion slot forbackend connectivity(SAS cards for expansion shelves) or secondary Host I/O if no SAS expansion is needed.

Slot 2:On smaller models (X10/X20), this is often theonlyhost I/O slot, but on the larger X50/X70/X90 chassis, it is used for additional Host I/O.

If an Implementation Engineer installs a SAS card in Slot 0, the system may fail to recognize the shelves correctly or may flag a configuration error, as the Purity software expects backend expansion traffic to route through the bus associated with Slot 1. Therefore, for SAS expansion cards, Slot 1 is the mandatory location.

The FlashArray//XR4 introduces a new hardware platform architecture (internally codenamed or associated with "Cobalt" components for its BMC and chassis management). During the manufacturing and initial deployment phase, specific validation scripts are used to ensure the platform hardware is correctly initialized before the Purity Operating Environment takes over.

For a new install of a FlashArray//XR4, the Implementation Engineer is often required to runcobalt check . py(or cobalt_check.py).

This engineering-level Python script queries the Baseboard Management Controller (BMC) and internal sensors to verify that the chassis components, fans, and power delivery systems are reporting "Healthy" status specifically for the R4 architecture.

Running thisbeforepuresetup prevents the setup process from failing midway due to a hardware initialization error. It acts as a "pre-flight" hardware validation specific to the R4 generation's new chipset and management subsystem.

=========

FlashArray performance and capacity management rely on "Write Groups"—logical groupings of drives that Purity uses to stripe data. A "Wide Write Group" typically consists of roughly 20 drives and offers better performance and capacity efficiency than smaller groups. However, Purity generally requires write groups to be contained within a single physical enclosure (chassis or shelf) to maintain failure domain boundaries and performance predictability.

In this scenario, the customer wants the new 91TB pack to form a wide write group. The chassis already has a 91TB group and a 45TB group. The shelf has one 45TB group. To create a wide write group with the new 91TB pack, it is best to pair it with an existing matching or compatible group in the same enclosure. Since the chassis is full (20 drives), you cannot simply add the new pack there without moving something.

The correct procedure is tomove the 45TB write group from the chassis to the shelf. This frees up 10 slots in the chassis. The shelf now holds two 45TB groups (which is valid). The chassis now has the original 91TB group and 10 empty slots. The engineer can then install the new 91TB data pack into those empty chassis slots. Purity will then be able to merge or manage these two 91TB packs (the existing one and the new one) as a highly efficient configuration, potentially forming the requested wide write group or at least balancing the high-capacity drives within the controller chassis where bandwidth is highest. This physical rearrangement is necessary because write groups cannot span across the chassis-shelf interconnect.

=========

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.

To perform a "powercycle" or restart of the FlashArray system as typically requested by Support for diagnostic or initialization purposes, the correct and safe method is to run the purearray reboot command.

While the term "power cycle" often implies a physical interruption of power in general IT terminology, Pure Storage FlashArrays are designed as "Always-On" systems and do not have standard physical power buttons on the controllers for this purpose (Option A is incorrect as no such button exists for system-wide power cycling). Physically unplugging the power cables (Option B) constitutes a "hard" power cycle or "cold boot," which is generally reserved for specific hardware replacements or emergency procedures, not standard support requests on a healthy or newly installed system.

The purearray reboot command gracefully shuts down the Purity operating system services, flushes data from the volatile memory to the non-volatile storage, and restarts both controllers sequentially or simultaneously depending on the arguments. This ensures that the system returns to a clean state without the risk of data inconsistency or "dirty" shutdowns that physical cable removal might cause. In the context of a new installation or support troubleshooting, this software-driven restart is the standard procedure.

Validating multipath I/O balance is a critical post-configuration step. The FlashArray CLI provides a specific monitoring tool for this purpose under the purehost command suite.

purehost monitor --balanceis the correct command.

monitor: This keyword initiates a real-time display of performance metrics (IOPS, bandwidth, latency).

--balance: This flag breaks down the metricsper initiator(per HBA/path) for the specified host(s).

The output allows the engineer to see if I/O is flowing evenly across all paths. If one path shows 0 IOPS while others are active, it indicates a zoning, cabling, or multipathing configuration issue that must be resolved to ensure high availability.

During the initial deployment phase of a FlashArray, thepuresetupuser 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 thepureuseraccount. 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.

=========

TheFlashArray//XLsupports0 (zero)SAS expansion shelves for permanent capacity.

Architecture:The FlashArray//XL is architected exclusively forNVMestorage media. Its backend connectivity utilizes 100GbE RoCE (RDMA over Converged Ethernet) to connect toDirectFlash Shelves (DFS). It does not possess the legacy SAS controllers or ports required to drive SAS expansion shelves.

Migration Exception:While a "SAS Swing Shelf" (containing legacy SSDs from an older array) might be temporarily attached during a specific Data-in-Place upgrade migration scenario, this is a transient state. In terms ofsupportedoperational configuration for storage capacity, the limit is zero. The platform relies entirely on DirectFlash Modules in the chassis and external DirectFlash Shelves.

Contrast:Older generations (FlashArray//M, FlashArray//X R1/R2) supported SAS shelves, but the //XL platform eliminates this protocol entirely in favor of end-to-end NVMe.

To verify the history and transmission status of Phonehome log bundles, the correct command ispurearray phonehome --list.

Before starting a controller upgrade (NDU), it is mandatory to ensure that the array can successfully transmit diagnostic data to Pure Storage. This allows Support to review the "pre-flight" checks and ensures that if an issue occurs during the upgrade, logs will be available for triage.

Usage:Running purearray phonehome --list displays a table of recent log bundles generated by the system.

Verification:The Engineer must look at the Status column for the most recent entries. A status of"uploaded"confirms that the array has successfully connected to the Pure Storage cloud and transferred the data. If the status is "queued" or "failed," the upgrade should not proceed until network connectivity (firewall/proxy) is resolved. Options A and C are incorrect CLI syntax for this specific verification task.

When performing a controller upgrade (Non-Disruptive Upgrade) from an //X50R3 to an //X50R4, the specific hardware configuration of the source array dictates the target bill of materials. The presence ofSAS drivesin the chassis indicates that the source is a legacy or transitional configuration, as the standard //X R4 platform is optimized for end-to-end NVMe (DirectFlash).

However, the question asks for the specific controller SKU required. In Pure Storage nomenclature for upgrades, the standard controller replacement part is typically the base model code, hereFLASHARRAY//XC50 R4.

The "XC" designation often refers to the controller component itself in upgrade kits. While special considerations apply to SAS media (which are usually phased out or require specific handling during R4 upgrades since R4 natively drops legacy SAS support on the motherboard), thecontrollerpart number itself remains the standard R4 SKU (Option C). Options like "SE" or "NS" (often denoting specific encryption or networking variants) are not the standard identifiers for the base controller upgrade in this context.

=========

FlashArray//X R4 (and the associated //C R4) models, introduced with the PCIe Gen 4 architecture, feature support for64Gb Fibre Channel (FC)connectivity. The default Fibre Channel Host Bus Adapters (HBAs) and the accompanying SFPs shipped with this generation are64Gbcapable, marking a significant performance leap from the 32Gb standard of the R3 generation.

While the HBAs are backward compatible with 32Gb and 16Gb SAN infrastructures, the R4 platform is explicitly marketed and technically defined by its ability to drive 64Gb line speeds to match the increased throughput of the backend PCIe Gen 4 bus and DirectFlash Modules. For an Implementation Engineer verifying the bill of materials or configuring the switch ports, it is critical to know that the R4 optics are native 64Gb. If the customer's switch infrastructure is only 16Gb or 32Gb, the ports will auto-negotiate down, but theshipped default hardwareis the 64Gb standard (Option C). Option A (16Gb) and Option B (32Gb) refer to the default standards for the older //M and //X R2/R3 generations respectively.