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

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.

iSCSI cards can be reused when upgrading from XR2 to XR3 controllers, supporting hardware continuity within this upgrade path.

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.

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.

The command pureadm stop --controller CT0 specifically stops Purity on the designated controller (CT0), which is the correct step to safely begin a controller upgrade.

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

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.

Mirrored Write statistics appear in the Purity GUI’s Analysis section when ActiveCluster is enabled, as it tracks synchronous replication activity between clusters.

Cage nuts should be placed in the lowest square hole of the lowest rack unit (RU) where the array rails will be installed to ensure proper alignment and support.

The FlashArray//XL supports up to two DirectFlash Shelves (DFS) for capacity expansion. This configuration allows for scalable storage solutions while maintaining optimal performance and efficiency. Each shelf can be connected to the array using appropriate interfaces, ensuring seamless integration and data flow. This setup is particularly beneficial for environments requiring high throughput and low latency, such as large-scale databases and enterprise applications.

The command hwconfig --model returns the model information of the controller, which is essential before running the puresetup replace procedure.

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.

The command purehost monitor --balance checks the distribution and health of I/O across hosts and initiators, helping verify balanced I/O after a controller upgrade.

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.

For an NDU from FlashArray//X70R2 to //X90R3, the minimum required hardware from the shipped array is the controllers, which are swapped into the existing chassis and power infrastructure.

The purearray remoteassist --connect command explicitly enables Support to establish a remote connection to the array for troubleshooting or assistance.

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.

To connect a DirectFlash Shelf located 6 meters away from the chassis, longer (7-meter) cables should be ordered to ensure proper physical connectivity without relocating equipment.