Pure Storage Certified FlashArray Implementation Specialist FlashArray-Implementation-Specialist FAIS Exam Questions

Answer : C

During a hardware upgrade, physical components are often moved or handled, leading to potential connection issues. If a specific port (like CT0.ETH14) that is expected to carry traffic shows 0.00 b/s and 'Link Down' or similar status immediately after the controller is initialized, the most likely physical issue is an improperly seated transceiver (SFP) or cable.

The standard troubleshooting hierarchy dictates checking Layer 1 (Physical) first. Therefore, the engineer should ensure the SFP in CT0.ETH14 is fully seated and re-seat it if necessary. SFPs can easily become slightly dislodged during the cable swap from the old controller to the new one. Checking the seating is a quick, non-disruptive step that resolves a high percentage of 'dead port' issues during upgrades. Swapping to a management port (Option A) is invalid because management ports often have different speeds or configurations, and asking the customer to reboot hosts (Option B) is premature and potentially disruptive before ruling out the physical array connection.

=========

Answer : A

The FlashArray//XL170R5 is a high-performance, high-capacity enterprise storage system. To maintain its performance characteristics and data layout efficiency, Pure Storage enforces a minimum raw capacity requirement for new orders and installations.

For the //XL170R5 model, the minimum supported configuration is 115TB of raw flash. This is typically achieved through a specific population of DirectFlash Modules (e.g., twenty 5.5TB modules or a similar combination that meets the threshold).

Implementation Engineers must verify during the pre-installation site readiness review that the hardware delivered matches this minimum. Attempting to initialize an //XL170 with significantly less capacity (e.g., 90TB) would be an unsupported configuration, potentially leading to performance degradation or an inability to initialize the wide write groups required by the //XL architecture.

=========

Answer : A

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 the FlashArray//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.

=========

Answer : C

When transitioning to a significantly different hardware platform---like moving from a 3U FlashArray//X50 R3 to a 5U FlashArray//XL130 R5---customers typically leverage Pure Storage's Evergreen storage programs (such as Ever Agile or Capacity Consolidation).

The FlashArray//XL introduces a fundamentally different chassis architecture. It requires a minimum of 20 DirectFlash Modules with distributed NVRAM (DFMDs) populated in slots 0-19 to provide the necessary write caching, completely replacing the standalone NVRAM modules found in the older //X series.

Options A and B are procedurally incorrect. While it is technically possible to retain compatible older DFMs in an //XL chassis (specifically in slots 20-39), moving drives 'one at a time, allowing parity to reach 100%' is never the standard Pure Storage procedure for a hardware upgrade. Evacuating and rebuilding parity for 20 individual drives sequentially would take an exorbitant amount of time, severely degrade array performance during the continuous rebuilds, and expose the system to unnecessary data loss risks. Pure Storage does not use a drive-by-drive rebuild methodology for controller or chassis swaps.

Instead, when older capacity is being replaced, a non-disruptive upgrade (NDU) or data migration is orchestrated via Purity's upgrade scripts and array-to-array migration tools. All data is transparently migrated from the legacy //X50 R3 drives to the fully populated DFMDs/DFMs in the new //XL130 R5. Once the software verifies that the data migration phase is successfully complete, the 20 legacy DirectFlash Modules from the //X50 R3 are decommissioned and returned to Pure Storage to fulfill the trade-in agreement.

Answer : B

When deploying File Services (often referred to as FA File) on a unified Pure Storage FlashArray, the system must integrate with the customer's existing identity management infrastructure, most commonly Active Directory (AD). Joining the AD domain allows the array to authenticate users seamlessly for SMB and NFS file shares.

During the configuration of FA File, the Implementation Engineer creates a dedicated Virtual Network Interface (VIF), which handles all the high-throughput, frontend client data traffic (the file reads and writes). However, control plane traffic behaves differently.

According to the official Pure Storage File Server Creation Wizard documentation, by default, FlashArray uses the management Ethernet port (management) for DNS communication and reaching domain controllers. The Purity operating system inherently routes LDAP queries, Kerberos authentication handshakes, and DNS hostname resolutions out of eth0 or eth1.

If the customer's network architecture is heavily segmented---meaning the management subnet is completely isolated and cannot route traffic to the Active Directory subnet---the Implementation Engineer must explicitly override this default behavior in the File Services configuration wizard by selecting the newly created File VIF as the 'Source Network Interface' for DNS/AD traffic. Otherwise, the default remains the management interface.

Answer : A

A '4X Module' kit is specifically designed to widen an existing write group (RAID set).

Write Group Geometry: In standard FlashArray//X configurations, DirectFlash Modules (DFMs) operate in 'Write Groups' (typically 10 modules wide for a standard data pack). However, to offer more flexible entry points or capacity expansion options, Pure Storage allows configurations that start with smaller write groups (e.g., 6 modules).

Widening: When a customer wants to expand capacity or performance on these smaller configurations without adding a full new 10-pack, they can purchase a widening kit (in this case, 4 modules).

Process: The Implementation Engineer installs these 4 modules into the empty slots. The Purity operating system then logically integrates these new drives into the existing narrow write group, 'widening' it to the standard width (e.g., 6 + 4 = 10). This operation redistributes parity and data across the full set of 10 drives, improving performance and efficiency.

Answer : B

When deploying File Services (often referred to as FA File) on a Pure Storage FlashArray, adhering to strict networking best practices is critical for ensuring enterprise-grade high availability and performance. Unlike basic management interfaces, which can technically operate on a single connection without disrupting data flow, data-serving interfaces demand robust redundancy. Therefore, the minimum requirement for deploying the file-services interface is dedicating at least 2 physical Ethernet ports per controller (for example, eth2 and eth3).

These dedicated physical ports are logically aggregated into a bonded interface using the Link Aggregation Control Protocol (LACP). LACP provides two distinct benefits: link redundancy and bandwidth aggregation. From a redundancy standpoint, if a single physical port, twinax cable, optical transceiver, or even the upstream Top-of-Rack (ToR) switch fails, the file traffic seamlessly fails over to the surviving port within the bond without disrupting active SMB or NFS client sessions. From a performance standpoint, multiple ports allow the array to distribute the file protocol workload more effectively. Attempting to configure File Services with zero dedicated ports or only a single physical port per controller violates Pure Storage implementation guidelines, creates a severe single point of failure, and will trigger persistent health alerts within the Purity operating system until the required redundancy is established.