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

The purehost iobalance --check command validates whether I/O is balanced evenly across initiators, helping ensure optimal performance and distribution.

To upgrade from Purity 5.3.8 to 6.1.21 on a new array, the Implementation Engineer should create a bootable USB installer from the target ISO and reimage both controllers to ensure a clean and supported upgrade.

In the FlashArray//XR2 and //XR3 models, the 2-port InfiniBand card should be installed in PCIe slot 2 on controller CT1. This slot is designated for InfiniBand connectivity, ensuring optimal performance and compatibility during the upgrade process. Installing the card in the correct slot is crucial for maintaining proper system functionality and achieving the desired performance metrics.

On FlashArray//XL, the PCIe slot 8 supports installation of 4-port Fibre Channel cards, allowing higher port density for SAN connectivity.

On an X50R2/3 FC array, Pure ships each controller with a factory-installed dual-port 32 Gb Fibre Channel card in the PCIe slot numbered 2, providing out-of-the-box SAN connectivity.

FlashArray//XL arrays require four power cables with C19 (receptacle) to C20 (plug) connectors to connect properly to rack PDUs, supporting redundant power supplies and higher power demands.

Waiting 10 minutes after running puredb run giveback --safe ensures the system completes safe resource rebalancing and stabilizes before proceeding with the next controller upgrade step.

A swing shelf is installed during the SAS to NVMe Evergreen XFORM upgrade only if the array lacks enough free capacity to evacuate data packs, enabling safe data migration during transformation.

The command purearray phonehome --send-logs is used to send all Phonehome logs to support upon completion of an upgrade.

The correct consolidation process involves evacuating data from the existing chassis drives first, then installing the new larger 91TB data pack, and finally evacuating shelf 0 to complete the consolidation efficiently.

The installation process begins with configuring controller 0 (CT0) first, as it is the primary controller responsible for initial system setup.

The FlashArray//X20R4 requires a minimum AC input voltage of 180V to operate. This ensures stable power delivery for the array's components.

The provided netmask "255.255.255.223" is invalid. Changing it to the standard subnet mask "255.255.255.0" aligns correctly with the gateway "10.24.18.1" for proper network configuration.

The command purenetwork list --ntpserver displays the configured NTP servers on the FlashArray network settings.

Upgrading from FlashArray X10 to X50 requires upgrading power supplies to meet the higher power demands of the larger chassis and expanded hardware.

FlashArray//E models utilize 25Gb Ethernet (25G) ports for connecting to DirectFlash Shelves (DFS). These 25G ports are designed to handle the high throughput demands of DFS, providing efficient data transfer between the storage array and expansion shelves. This configuration ensures optimal performance and scalability for FlashArray//E systems.

When replacing SAS chassis data packs with DirectFlash Modules (DFMs) after an upgrade to //X20R3-EMEZZ, a DFM Swing Shelf is required to facilitate data evacuation and migration during the transition.

FlashArray//XL power supply units (PSUs) are designed with 2+2 redundancy, meaning there are four PSUs where any two can fail without impacting array operation.

To ensure compatibility and optimal performance, the Implementation Engineer should consult the recommended DFS versions for the installed Purity release and upgrade both the FlashArray and DirectFlash Shelf accordingly.

Drive relocation should be performed only after the XFORM upgrade completes to avoid disrupting the upgrade process and ensure data integrity.

Port 443 (HTTPS) must be open on all management ports to enable secure outbound connections for Phonehome and Remote Assist functionality.

For ActiveCluster with Ethernet replication, a total of 8 IP addresses are typically required; if 3 are already provided, 5 additional IPs are needed to complete the configuration.