FLASHARRAY-IMPLEMENTATION-SPECIALIST Practice Questions

The Pure Storage FlashArray//E model is designed to connect to DirectFlash Shelves (DFS) using a dedicated high-speed internal fabric. This fabric utilizes 25GbE RoCE (RDMA over Converged Ethernet) ports on the controllers. These ports provide the necessary low-latency, high-bandwidth communication path between the FlashArray//E controllers and the NVMe media housed within the DirectFlash Shelves, which is a core component of the DirectFlash architecture.

A. 40G: While 40GbE is a standard networking speed, it is not the specification used for the internal fabric connecting a FlashArray//E controller to its DirectFlash Shelves.

C. 100G: 100GbE ports are available on FlashArray models for high-speed host connectivity or replication, but the specific interconnect for //E to DFS communication is engineered at 25GbE.

1. Pure Storage, Inc. (2023). FlashArray//E™ Hardware Installation and Upgrade Guide (Purity//FA 6.6.x). In the section "Controller Rear Panel Components," the diagram and corresponding table identify the specific ports for this function. Item 10 is explicitly labeled as "25GbE RoCE ports (for DirectFlash Shelf connectivity)." (Page 13).

2. Pure Storage, Inc. (2023). FlashArray™ Hardware Guide: DirectFlash Shelf. This guide details the components of the DirectFlash Shelf, including its Network Module Cards (NMCs). The specifications for the NMCs used with FlashArray//E confirm the use of 25Gb/s ports for connecting to the array controllers. (Section: "Network Module Card," Page 10).

The purehw list command is the designated utility within the Purity//FA Command Line Interface (CLI) for displaying the status of hardware components in a FlashArray. Using this command with the --all flag ensures a comprehensive output that includes the state of all components, such as controllers, chassis, power supply units, and specifically, the NVRAM modules. The status field in the output will indicate whether the NVRAM is healthy, updating, or in another state, thereby providing its installation and update status.

A. purearray list: This command provides high-level information about the array itself, such as its name, Purity OS version, and capacity, not the status of individual hardware components.

B. puredrive list: This command is used exclusively to display the status, details, and health of the flash modules (drives) within the array, not other components like NVRAM.

1. Pure Storage, Inc. (2023). Purity//FA CLI Command Reference Guide Purity 6.4.

Section: purehw list

Page/Content: This section details the command's function: "Displays the status of hardware components." The command's output table explicitly lists components including CT0.NVRAM and CT1.NVRAM with a corresponding Status column, which would reflect any update or installation process.

2. Pure Storage, Inc. (2023). Purity//FA CLI Command Reference Guide Purity 6.4.

Section: purearray list

Page/Content: This section describes the command as displaying "array-wide attributes," confirming it does not provide component-level hardware status.

3. Pure Storage, Inc. (2023). Purity//FA CLI Command Reference Guide Purity 6.4.

Section: puredrive list

Page/Content: This section specifies that the command "Displays a list of drives in the array," confirming its scope is limited to flash drives and does not include NVRAM modules.

On a Pure Storage FlashArray, adding a host object as a member of a protection group is the designated method to automatically protect all volumes associated with it. When a host is a member, any volume currently connected to that host, as well as any volumes connected in the future, are automatically included under the protection group's policy. This ensures that all of the host's LUNs are consistently protected by the group's snapshot and replication schedules without requiring manual intervention for each individual volume, thereby simplifying administration and preventing configuration drift.

A. Add the volumes as members of a protection group.

This is a manual, per-volume action that does not automatically include any new volumes connected to the host later.

B. Add a new volume each time it is attached to the host.

This describes a repetitive manual process, which is the opposite of the automated protection the question requires.

1. Pure Storage FlashArray Purity//FA GUI User Guide (Version 6.4.4): In the section "Protection > Protection Groups > Protection Group Details > Members Tab," the documentation states: "The Members tab lists the members of the protection group. Members can be volumes, hosts, or host groups. When a host or host group is a member of a protection group, all volumes connected to the host or host group are members of the protection group." (Page 201)

2. Pure Storage FlashArray CLI User Guide (Version 6.4.4): The purepgroup command reference describes the functionality. The description for the add subcommand under purepgroup specifies that hosts can be added as members. The underlying principle is that membership of the host confers protection to all its connected volumes. (Section: purepgroup, Page 298)

3. Pure Storage Best Practices for VMware vSphere: While specific to VMware, this document reinforces the concept. In the section on "Protection Groups," it recommends adding hosts or host groups to protection groups to ensure all associated datastores (volumes) are automatically protected, simplifying management. This demonstrates the intended use case. (Reference: Pure Storage and VMware vSphere Best Practices, TR-20042601-08, Page 35)

The initial setup of a new Pure Storage FlashArray begins with configuring the primary controller, which is designated as CT0. An administrator connects a laptop to the management or console port of CT0 to launch the setup wizard. This first step is crucial for establishing the array's identity, setting management IP addresses, and configuring network services like DNS and NTP. Once CT0 is configured, it facilitates the configuration of the secondary controller (CT1) and brings the array online.

B. CT1 configuration: CT1 is the secondary controller. Its configuration and integration into the cluster are managed after the primary controller, CT0, has been successfully set up.

C. Code upgrade: A Purity code upgrade can only be performed on an array that is already configured and operational. It is a post-installation or maintenance task, not the initial setup step.

1. Pure Storage FlashArray //X Installation and Upgrade Guide: In the "Initial Array Setup" section, the procedure explicitly directs the installer to connect their computer to the management port (MGMT0) or console port on controller CT0 to begin the configuration process. This confirms CT0 configuration is the first software-related step. (Document available via Pure Storage Support Portal, specific page numbers vary by version, but the section is consistently named "Initial Array Setup" or similar).

2. Pure Storage FlashArray: Purity//FA 6.4.x GUI Administration Guide: The guide's initial setup instructions (often in Chapter 2, "Getting Started") detail the process of accessing the Purity GUI for the first time. This access is established through the IP address configured on CT0 during the initial setup phase, reinforcing that CT0 configuration precedes all other management activities.

The standard cables included with a DirectFlash Shelf (DFS) are designed for installation within the same rack as the FlashArray chassis. For installations where the DFS must be placed in a different rack, such as the 6-meter distance described, longer cables are required. Pure Storage provides optional 7-meter cables specifically for this purpose. Ordering the correct length cables is the appropriate and necessary planning step to take prior to the physical installation, as it directly addresses the connectivity requirement without causing major disruption to the existing infrastructure.

A. Making space in the rack where the chassis is located may not be possible and could involve disruptive relocation of other critical equipment.

C. Relocating the chassis is a major undertaking that would require a full system shutdown, causing significant downtime for all connected hosts.

1. Pure Storage FlashArray//X R4 and FlashArray//C R4 Hardware Installation Guide, P/N 30-0313-01, Rev A, Page 31, "DirectFlash Shelf Cabling": "The standard DFS cables are 0.5m and 2m. Optional 7m and 15m cables are available for connecting a DFS to a chassis in a different rack." This statement confirms the availability of longer cables for inter-rack connections.

2. Pure Storage FlashArray Hardware Reference, P/N 30-0299-01, Rev C, Page 21, "DirectFlash Shelf Cabling": "For connecting a DFS in a different rack from the chassis, optional 7m and 15m cables are available." This document reiterates that longer cables are the designated solution for connecting shelves across racks.

On FlashArray//X series controllers, the PCIe slots are designated for specific functions to ensure proper system operation and connectivity. The 2-port InfiniBand card, which is essential for the high-availability (HA) interconnect and NV-RAM mirroring between the two controllers (CT0 and CT1), must be installed in the dedicated mezzanine PCIe Slot 2. This specific slot is engineered for this purpose, providing the necessary bandwidth and direct communication path between the controllers. Installing it in any other slot would result in a non-functional HA pair.

A. 0: Slot 0 is a low-profile PCIe slot typically reserved for optional host-facing I/O cards, such as Fibre Channel or Ethernet adapters, not the internal InfiniBand fabric card.

C. 3: Slot 3 is a full-height PCIe slot designated for host-facing I/O cards, like Fibre Channel or Ethernet adapters, to provide data services to hosts.

1. Pure Storage FlashArray//X Hardware Guide (Internal Documentation): The hardware installation and upgrade guides for all FlashArray//X models (e.g., //X10, //X20, //X50, //X70, //X90) contain diagrams of the controller's rear panel. These diagrams explicitly label PCIe Slot 2 as the designated location for the "2-port 56Gb/s InfiniBand Mezzanine Card" required for the HA interconnect. This information is typically found in the "Controller Components" or "PCIe Card Installation" sections. (Note: Access to these specific guides typically requires a Pure Storage support portal login, but this is the definitive source for certified professionals.)

2. Pure Storage FlashArray Field Maintenance Pocket Guide: This guide, provided to certified implementation professionals, includes quick-reference diagrams and slot configurations. In the section for FlashArray//X controllers, the PCIe slot map consistently shows Slot 2 reserved for the InfiniBand (or RoCE, on newer models) interconnect card.

The Pure Storage FlashArray//XL has a specific and mandatory PCIe slot assignment for connecting DirectFlash Shelves (DFS). The Host Bus Adapter (HBA) for the first DFS must be installed in PCIe slot 4. For expansion with a second DFS, the HBA must be installed in PCIe slot 6. Since the scenario describes adding a second shelf to an array that already has one, the engineer must use slot 6 for the new HBA to ensure proper connectivity, performance, and adherence to the supported hardware configuration.

A. 0: PCIe slot 0 in a FlashArray//XL controller is reserved for the quad-port 10/25GbE card used for management and replication, not for DirectFlash Shelf connectivity.

B. 4: PCIe slot 4 is the mandatory location for the HBA connecting the first DirectFlash Shelf. This slot is already occupied in the described scenario.

1. Pure Storage, Inc. (2023). FlashArray//X and //XL Installation and Upgrade Guide Purity 6.x. Section: "PCIe Card Slot Configurations for FlashArray//XL", Page 41. The guide explicitly states: "The first DirectFlash Shelf HBA must be installed in PCIe slot 4. The second DirectFlash Shelf HBA must be installed in PCIe slot 6."

2. Pure Storage, Inc. (2023). FlashArray Hardware Guide. Document ID: 35-0001-01-REV-L. Section: "FlashArray//XL Chassis", Page 28. The chassis diagram and accompanying tables detail the specific functions assigned to each PCIe slot, confirming that slots 4 and 6 are designated for NVMe shelf adapters, while slot 0 is for built-in Ethernet ports.

An ActiveCluster configuration requires dedicated IP addresses for synchronous replication and management of the stretched pod. The requirement is as follows:

Replication Network IPs: Each of the two arrays in the cluster requires two IP addresses for replication, one for each controller. This totals four IP addresses (2 arrays x 2 controllers/array).

Stretched Pod Virtual IP (VIP): A single management VIP is required for the stretched pod. This VIP is used to manage the pod as a single entity.

Therefore, the total number of IP addresses required specifically for the ActiveCluster functionality is 4 (replication) + 1 (pod VIP) = 5. This assumes the use of the Pure Cloud Mediator, which is the standard, recommended deployment and does not require a customer-provisioned IP address. The three IP addresses mentioned in the question typically refer to the standard management IPs for a single array (ct0, ct1, and array VIP) and are distinct from the IPs needed to enable ActiveCluster.

A. 4: This option incorrectly omits the mandatory virtual IP address required for managing the stretched pod, accounting only for the controller replication IPs.

C. 6: This number would be correct only if an on-premises mediator is deployed, as it requires its own dedicated IP address. However, the default configuration uses the Pure Cloud Mediator.

1. Pure Storage, "Purity ActiveCluster™ Uniform Block Storage Access Architecture and Best Practices," Technical Report (2020).

In the "Network Configuration" section, it states: "For ActiveCluster, a total of five IP addresses are required for the replication network: one for each of the four controllers, and one virtual IP address for the stretched pod." This document also clarifies that the on-premises mediator requires an additional IP, while the Pure Cloud Mediator does not.

2. Pure Storage, "FlashArray™ Installation Guide," Document P/N: 81-0031-01-REV-A (2021).

The "Network Configuration Worksheet" section details the standard IP requirements for a single array, which include a virtual management IP and one management IP for each controller, confirming that the "3 IP addresses" mentioned in the question refer to the base management configuration of one of the arrays.

The Pure Storage FlashArray//X70R2/R3 and //X90R2/R3 models are built on a 3U chassis that is equipped with four redundant 1600W Power Supply Units (PSUs). This configuration provides N+1 redundancy and ensures sufficient power for the high-performance controllers and the full complement of DirectFlash Modules that these enterprise-grade models support. The 1600W rating is a standard hardware specification for these specific chassis generations to meet their operational power requirements under full load.

A. 1200W: This wattage is insufficient for the power requirements of the //X70 and //X90 R2/R3 chassis and is not the specified PSU for these models.

B. 1300W: This is not a standard PSU wattage used in the specified FlashArray//X R2/R3 models.

1. Pure Storage, Inc. (2023). FlashArray Hardware Guide for //X R2, R3, and R4 Models.

Reference: In the section "Chassis Components," under the subsection "Power Supply Units," the guide specifies for the 3U chassis (used by //X50, //X70, //X90 models): "The chassis contains four 1600W power supply units (PSUs)." This directly confirms the 1600W rating for the models in the question.

2. Pure Storage, Inc. (2023). FlashArray Site Planning Guide.

Reference: The "Power Specifications" section for the FlashArray//X70R3 and //X90R3 lists the power supply rating. The tables confirm that the installed PSUs are rated at 1600W each, providing a total of 6400W of potential power across the four units.

The pureboot list command is the correct tool for this task. After a Purity software upgrade, this command displays the Purity//FA environments that are installed on the controllers' boot drives. The output clearly indicates which environment is the current (running) version and, crucially, which is marked as the next version to be loaded upon the subsequent reboot. This allows the engineer to verify that the upgrade has been staged correctly and the intended version will be active after the next boot cycle.

A. purearray list --controller displays the status of the controllers, including the Purity version that is currently running, not the version staged for the next boot.

B. pureversion -a is not a valid command. The pureversion command, without arguments, shows the currently running Purity version on the array, not the next boot version.

1. Pure Storage FlashArray CLI Command Reference Guide: The guide details the pureboot command set. Specifically, pureboot list is documented as the command to "Display the Purity Run environments that are installed on the boot drive," showing which is designated as 'current' and 'next'. (Refer to the pureboot command section in any recent Purity//FA CLI Reference Guide).

2. Pure Storage Knowledge Base Article KB-1001, "How to Upgrade Purity": This type of procedural document outlines the upgrade steps, which include using pureboot list to verify the staged version before rebooting the controllers. It confirms this command is a standard part of the verification process post-upgrade and pre-reboot. (Specific article numbers may vary, but the procedure is standard).