Newly Released Pure Storage FlashArray-Storage-Professional Exam PDF

Definition of Host Personality: In Purity//FA, a Host Personality is a setting applied to a host object that modifies how the FlashArray communicates with that specific initiator. It ensures the array sends the correct SCSI responses that the target Operating System (OS) expects. Common personalities include ESXi, AIX, HP-UX, and Hitachi-VSP.

The Importance of Timing: The best practice is to set the personality during the host creation phase , before any volumes are attached or I/O has commenced. This ensures that from the very first " Inquiry " command sent by the host, the FlashArray responds with the appropriate settings (such as specific VAAI primitives for ESXi or specific ALUA behaviors for other Unix variants).

Risks of Changing Later: While Purity allows you to change a host personality later, doing so while volumes are connected and I/O is active can be disruptive. For many operating systems, a change in personality requires the host to be rebooted or the storage paths to be " rescanned " to recognize the change in device capabilities.

Default Behavior: If no personality is selected, the FlashArray uses a " Generic " personality suitable for standard Windows and Linux distributions. However, for specialized hypervisors like ESXi , failing to set the personality correctly from the start can lead to performance issues or lack of support for hardware acceleration features.

Why Option C is incorrect: Changing the personality after volumes are connected is reactive rather than proactive. It increases the risk of the host misinterpreting the storage device ' s capabilities, potentially leading to mount failures or path instability.

Understanding MTU: The Maximum Transmission Unit (MTU) defines the largest size of a packet or frame that can be sent in a single network transaction. The standard Ethernet MTU is 1500 bytes . Anything larger than 1500 bytes is referred to as a Jumbo Frame .

Replication Efficiency: Replication involves moving large amounts of data between arrays. Using standard 1500-byte frames results in higher overhead because the CPU must process a larger number of headers for the same amount of data. By increasing the MTU, the FlashArray can pack more data into each frame, reducing CPU interrupts and improving overall throughput.

The Pure Recommendation: Pure Storage specifically recommends an MTU of 9000 for both iSCSI and Replication traffic. This is the industry standard for Jumbo Frames that balances efficiency with compatibility across most enterprise-grade switches.

Configuration Requirements: It is critical to remember that MTU must be configured end-to-end . For an MTU of 9000 to work on the replication ports:

The FlashArray replication ports must be set to 9000.

The network switches along the path (and any routers/ISLs) must support and be configured for at least 9000.

The target array ' s replication ports must also be set to 9000.

Why 9216 (Option A) is incorrect: While some switches support a " Baby Giant " or slightly larger MTU like 9216 to account for VLAN tagging overhead, Pure ' s internal and best practice documentation specifically points to 9000 as the standard setting for the array ' s interface.

On the Pure Storage FlashArray//C R4 (as well as the //XL and //E series architectures), the onboard 100Gb/s Ethernet LOM (LAN on Motherboard) ports—specifically eth0 and eth1—are purpose-built and strictly reserved for DirectFlash Shelf (DFS) connectivity .

Pure Storage uses these dedicated 100GbE ports to run NVMe over RoCE (RDMA over Converged Ethernet), effectively extending the array ' s internal PCIe backplane to additional backend storage shelves. Because these ports are hardcoded exclusively for back-end shelf expansion, the Purity operating environment fundamentally restricts them from being assigned IP addresses for front-end host I/O services. Therefore, an administrator will be completely unable to configure eth0 or eth1 for iSCSI, NVMe/TCP, or Replication. Front-end iSCSI services must instead be configured on the dedicated Host I/O PCIe cards (which typically appear as eth2, eth3, etc., depending on the slot configuration).

Here is why the other options are incorrect:

The ports are designated for Management connectivity (A): On modern FlashArrays, dedicated management ports are typically out-of-band 1GbE/10GbE RJ45 ports (often designated as vir0 or specific management eth ports on older hardware), not the ultra-high-speed 100Gb/s QSFP28 ports.

The DAC cables are not compatible with the array ' s ports (B): While incompatible cables can prevent a link from coming up physically, the specific reason the administrator cannot configure the ports for iSCSI in the Purity software is due to the port ' s hardcoded role (DFS), not the physical cable type.

Zoning Best Practices: In a Fibre Channel SAN environment, zoning is used to partition the fabric to ensure that initiators (hosts) can only see the targets (FlashArray ports) they are intended to communicate with.

The " Single Initiator " Rule: Pure Storage, following industry-standard SAN best practices (and Cisco/Brocade recommendations), strongly advises using Single Initiator Zoning . This means each zone should contain exactly one initiator (HBA port) and one or more targets (FlashArray ports) .

Why Single Initiator to Multiple Targets (Option B)?:

Isolation: This prevents " Initiator-to-Initiator " communication. If multiple initiators are in the same zone, they may attempt to communicate with or probe each other (Registered State Change Notifications - RSCNs), which can cause host instability, driver timeouts, or discovery issues.

Troubleshooting: It simplifies troubleshooting. If a port is experiencing CRC errors or flapping, the impact is isolated to that specific host ' s zone rather than affecting a broad " group " zone.

Efficiency: When a target port changes state (e.g., during a controller reboot), the switch sends an RSCN. In a single-initiator zone, only that specific host is notified. In a multi-initiator zone, every host in the zone is interrupted to process the notification, even if they aren ' t using the port that changed.

Target Selection: While the zone should have only one initiator, it can (and should) include multiple target ports from the FlashArray (usually one port from CT0 and one from CT1 for the same fabric) to provide path redundancy and allow the host ' s MPIO software to manage failover.