Important Pure Storage FlashArray-Implementation-Specialist FAIS Exam Questions

Answer: A

Explanation:

Data evacuation from a shelf is a sensitive background process where data is migrated off specific physical media to free it for removal. While the purearray evacuate command initiates the data movement, the finalization of the process---specifically the logical removal of the shelf object from the system configuration to allow for safe physical disconnection---often requires engineering-level commands or verification.

Therefore, before Pure Storage Support can log in to run these specific completion scripts or verification checks, the Implementation Engineer must Enable Remote Assist (RA).

Remote Assist creates a secure, outbound SSH tunnel that allows Support to access the array remotely.

Without RA enabled, Support cannot connect to the array to execute the necessary puredrive or internal maintenance commands to mark the shelf as 'vacated' and safe to unplug.

Powering off the shelf (Option B) before this step could result in data loss or an array outage if the system still believes data resides there.

=========

Answer: B

Explanation:

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

Explanation:

During and after a Hardware Non-Disruptive Upgrade (HWNDU), the FlashArray may generate various alerts related to component removals, path failovers, or temporary redundancy reductions. Once the upgrade is physically complete and the software has stabilized, the Implementation Engineer must verify that the array has returned to a fully healthy state.

The command purealert list is the primary tool for this verification. It displays the current table of active alerts on the system.

If the array is healthy, this list should be empty or contain only 'Info' level messages.

If the system is still recovering, you might see alerts with a status indicating they are 'closing' or 'downgrading' as the conditions resolve (e.g., 'Controller redundancy restored').

pureaudit list shows the history of user commands, not system health alerts. puremaintenance is not a standard command for checking alert status. Therefore, purealert list is the correct command to validate that no critical hardware or software issues remain active after the maintenance window.

Answer: A

Explanation:

The FlashArray//XR4 architecture utilizes massive 100GbE RDMA over Converged Ethernet (RoCE) for its backend loops to maintain NVMe-level performance across external expansion shelves. Because of the sheer bandwidth requirements, specific port and slot assignments are strictly regulated by the Purity operating system.

On a standard //XR4 model, the controllers feature dedicated, integrated 100GbE ports on the motherboard (typically enumerated as eth18 and eth19) which are strictly reserved for connecting the first DirectFlash Shelf loop. When an Implementation Engineer needs to install a second DirectFlash Shelf, those onboard ports are already fully saturated.

To establish a new dedicated backend fabric loop for the second shelf, the engineer must install an additional dual-port 100GbE RoCE PCIe expansion card into a designated slot (typically Slot 4). Once this card is properly seated, cabled, and recognized by the Purity operating system, it enumerates the new high-speed network interfaces natively as ETH6 and ETH7. The Implementation Engineer must use these exact interfaces to connect the shelf to ensure the backend topology passes the mandatory pre-flight validation scripts and functions at optimal NVMe-oF speeds.

Answer: A

Explanation:

When executing a Hardware Non-Disruptive Upgrade (HWNDU) to a new chassis generation, such as moving to a FlashArray//XR5, the new controllers must be properly prepped to join the existing, older-generation cluster. The correct sequence of operations is critical to prevent the cluster from rejecting the mismatched hardware.

Once the new //XR5 controller is physically inserted into the slot of the removed older controller, the Implementation Engineer must first install the correct target version of the Purity//FA operating system locally using the pureinstall command via the KVM console. After Purity is successfully installed, but strictly before the controller is logically initialized to join the cluster (via the puresetup secondary command), the engineer must execute the start_ndu controller-ndu script.

This script applies specific internal HWNDU tunables---such as relaxing hardware mismatch checks, bypassing specific alert monitors, and adjusting heartbeat timeouts. Setting these tunables ensures that when the controller is finally initialized, the surviving primary controller safely accepts it as a valid secondary partner without triggering a system fault, hardware rejection, or disrupting active host I/O.