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

Answer : B

Within the Purity//FA operating system, specialized system variables, behavioral overrides, and feature flags are managed using 'tunables.' Tunables are typically set by Pure Storage Support or Implementation Engineers to address specific environmental edge cases, enable beta features, or manage hardware non-disruptive upgrade (HWNDU) states.

Once a maintenance window is complete or a tunable is no longer required, it must be carefully removed to return the array to its default operational state. The correct and officially supported Purity CLI command to remove a tunable is puretune --unset <tunable_name>.

Because FlashArray controllers operate in a highly available, clustered configuration, standard tunables applied to the array are generally mirrored. Executing puretune --unset from the active primary controller will cleanly strip the tunable from the configuration database, applying the change system-wide. Commands like pureadm do not exist in the standard Purity CLI, and puretune remove is incorrect syntax.

Answer : C

When deploying a high-end Pure Storage FlashArray//XL (which utilizes a massive 5U chassis), the PCIe slot architecture differs significantly from the standard 3U //X series. The //XL is designed for extreme backend NVMe-oF (RoCE) bandwidth to support multiple DirectFlash Shelves (DFS) without creating bottlenecks.

According to the official FlashArray//XL cabling matrix and hardware implementation guides, specific PCIe slots are strictly reserved and optimized for backend expansion. To connect external DirectFlash Shelves, the Implementation Engineer must populate the 100GbE RoCE backend expansion cards into PCIe Slot 0 and PCIe Slot 6.

When cabling the first two external shelves (typically designated logically as SH8 and SH9 depending on the loop configuration), the preferred mapping routes the NVMe-oF connections from the shelf modules to Slot 0 for one shelf and Slot 6 for the other. Utilizing other slots, such as Slot 1, 7, or 8, is incorrect because those are primarily reserved for frontend host connectivity (like 32G/64G Fibre Channel or frontend NVMe/TCP host bus adapters). Incorrectly slotting the backend cards will result in hardware_check.py validation failures, sub-optimal NUMA node alignment, and potential backend network instability.

Answer : A

In the Purity//FA Graphical User Interface (GUI), the management of FA File resources is integrated into the core 'Storage' navigation pane. To manage specific file system directories---such as creating new exports, setting quotas, or managing directory-level policies---the Implementation Engineer must navigate to Storage > File Systems.

Within this view, the engineer can see the list of provisioned file systems. By clicking into a specific file system, they can access the 'Directories' sub-tab or detailed view where folders (directories) within that file system can be explicitly managed.

It is important not to confuse this with 'Directory Services,' which is located under the Settings menu. 'Directory Services' (Option B) refers to the configuration of Active Directory (AD) or LDAP connections for user authentication and identity mapping, not the management of the actual file storage structure. Similarly, the Analytics tab (Option C) provides performance metrics but does not offer configuration capabilities for creating or modifying directories.

=========

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 : C

Pure Storage enforces strict naming conventions for FlashArrays to ensure compatibility with network protocols (like DNS), replication pairing, and fleet management tools. The allowable character set for an array name is alphanumeric characters (A-Z, a-z, 0-9) and hyphens (-).

The proposed name 'corporate Lab-0L' contains a space character between 'corporate' and 'Lab-0L'. FlashArray names cannot contain spaces.

Hyphens (Option A) are allowed and commonly used (e.g., FlashArray-01).

Numbers (Option B) are allowed (e.g., Lab-01).

To resolve the error, the Implementation Engineer should replace the space with a hyphen or remove it entirely (e.g., corporate-Lab-0L or corporateLab-0L). This restriction prevents issues with CLI parsing and host hostname resolution where spaces are often interpreted as delimiters.

Answer : A

The FlashArray//X20 R4 operates with a minimum AC voltage input of approximately 90 VAC.

The FlashArray//X series (specifically the entry-to-mid-range models like the X10, X20, and X50) utilizes high-efficiency Power Supply Units (PSUs) designed with auto-ranging capabilities. These PSUs conform to standard global power infrastructure requirements, supporting a nominal input range of 100V to 240V AC (50/60 Hz).

Low-Line Support: Because the X20 is an entry-level enterprise array often deployed in diverse environments (including edge locations or standard office server rooms), it fully supports 'low-line' power (100-120V nominal). The technical minimum tolerance for these power supplies typically extends down to 90 VAC to account for voltage sags or fluctuations.

Contrast with High-End: Larger, higher-density systems like the FlashArray//XL or fully loaded high-performance chassis configurations often require 'high-line' power (200V-240V) to deliver sufficient wattage efficiently. However, the X20 R4 does not have this restriction. Therefore, Option A (90V) represents the correct minimum floor, whereas Options B and C represent high-line voltages that are supported but not required for minimum operation.

Answer : C

Standard enterprise data center power distribution units (PDUs) typically use C13 or C19 outlets. The FlashArray//X series power supplies utilize C14 inlets (the male connector on the chassis side). Therefore, the standard accessory kit included with a FlashArray//X ships with C13 to C14 power cables.

The C13 connector plugs into the array's power supply (matching the C14 inlet), and the C14 connector on the other end is designed to plug into a standard rack PDU (which typically has C13 outlets). This is the industry-standard 'jumper cord' for rack-mounted server and storage hardware.

It is important for the Implementation Engineer to verify this during the pre-install phase. If the customer's facility uses non-standard PDUs (like those with C19 outlets or wall-style plugs), the standard kit cables will not fit, and the engineer must ensure the correct cables were ordered separately or provided by the customer. However, for the exam and standard BOM validation, the correct answer is the ubiquitous C13 to C14 cable type.

=========