FlashArray-Storage-Professional Pure Certified FlashArray Storage Professional Questions and Answers

ActiveCluster Scalability Limits: Pure Storage FlashArrays have specific scalability limits regarding the number of " Active " or " Stretched " pods allowed per array or ActiveCluster pair. While these limits can vary slightly based on the Purity//FA version and the specific hardware model (e.g., //X, //XL, or //m), a common architectural limit in many Purity versions is up to 12 stretched pods .

The Scenario Analysis: In this case, the environment already has 12 stretched pods successfully replicating. When the administrator attempts to stretch a 13th pod, the operation fails because the array has hit the maximum concurrent stretched pod count supported by the Purity operating environment for that configuration.

Stretched vs. Unstretched: A pod exists locally (unstretched) without consuming an ActiveCluster pod " slot " in the same way. The failure specifically occurs during the " stretch " operation, which is the point where the synchronous replication relationship and mediator monitoring are established.

Resolution: To resolve this, the administrator would either need to:

Unstretch or Eradicate an existing pod that is no longer needed to free up a slot.

Check the specific Purity Release Notes for the hardware model to see if a firmware upgrade increases the maximum pod limit (some newer versions support more, but 12 is the classic threshold often tested in professional certifications).

Remote Assist (RA) Overview: Remote Assist is a secure, customer-initiated tunnel that allows Pure Storage Technical Support Engineers (TSEs) to log into a FlashArray to perform diagnostics and maintenance. It is disabled by default and must be explicitly opened by the customer.

Access Modes in Purity: In modern Purity versions (like 6.8.4), Pure Storage has introduced granular access controls for these support sessions to satisfy enterprise security and compliance requirements (such as SOC2 or HIPAA).

Restricted Access: This mode is specifically designed for high-security environments. When RA is enabled with the Restricted flag, the Support Engineer is limited to a pre-defined subset of non-destructive, read-only, or diagnostic commands. They cannot perform major configuration changes, delete data, or access sensitive metadata without further authorization.

Elevated vs. Secured: * Elevated access (often used during emergency recovery) provides the TSE with broader permissions, including the ability to run system-level scripts and configuration commands that go beyond standard diagnostics.

Secured is often a baseline state but does not imply the specific command-level filtering that " Restricted " does.

Security Best Practice: If a security team mandates that " only certain commands can be executed, " Restricted is the correct administrative choice. This ensures that the principle of least privilege is applied even to the vendor’s support staff.

According to the official Pure Storage FlashArray Asynchronous Replication Configuration and Best Practices Guide , the proper and immediate method to halt an active, in-progress asynchronous replication transfer is by disallowing the protection group at the target .

When you navigate to the target FlashArray and disallow the specific Protection Group, Purity immediately breaks the replication authorization for that group. If there is an in-progress snapshot transfer occurring at that exact moment, the transfer is immediately stopped, and the partially transferred snapshot data is discarded on the target side.

Here is why the other options are incorrect:

Disabling the replication schedule (B): Toggling the replication schedule to " Disabled " only prevents future scheduled snapshots from being created and sent. It does not kill or interrupt a replication transfer that is already currently in progress.

Removing the volume member from a protection group (A): Modifying the members of a protection group updates the configuration for the next snapshot cycle. It does not actively abort the transmission of the current point-in-time snapshot that the array is already busy sending over the WAN.

Protocol Compatibility: While NVMe-over-Fabrics (NVMe-oF) is the future of high-performance storage, support for it within specific hypervisor ecosystems varies. In the context of Microsoft Hyper-V , especially in older or standard Ethernet-switched environments, iSCSI remains the most mature, widely supported, and native protocol for block storage.

Ethernet Constraints: The question specifies an Ethernet-switched environment . This immediately rules out NVMe/FC (NVMe over Fibre Channel), as that requires dedicated Fibre Channel switching infrastructure and HBAs, not standard Ethernet.

NVMe/RoCE vs. iSCSI: While NVMe/RoCE (RDMA over Converged Ethernet) runs on Ethernet, it requires specialized NICs (RDMA-capable) and a specific switch configuration (PFC/LFC) to ensure a lossless fabric. Hyper-V has specific requirements for RoCE (often tied to SMB Direct for File services), but for general block storage volumes in a standard Ethernet environment, iSCSI is the " best suited " due to its ease of deployment, native Windows initiator support, and lack of requirement for specialized lossless hardware.

Pure Storage Best Practices: Pure Storage FlashArrays provide industry-leading iSCSI performance. When using iSCSI with Hyper-V, Pure recommends using the native Windows MPIO (Multi-Path I/O) with the " Least Queue Depth " policy to ensure optimal load balancing across the Ethernet fabric.

Understanding Data Reduction Rate (DRR): DRR is a measure of the effectiveness of Purity ' s deduplication and compression algorithms. It compares the amount of data written by the host to the amount of physical space actually occupied on the flash media after these processes have occurred.

Calculation: $\text{DRR} = (\text{Deduplication} \times \text{Compression})$.

Understanding Total Reduction: The Total Reduction metric is a broader " efficiency " value. It represents the ratio of the Total Provisioned (logical) space to the Physical space used.

The " Thin Provisioning " Factor: The primary difference between these two numbers is Thin Provisioning .

FlashArrays are 100% thin-provisioned by default. If a customer creates a 100TB volume but the host only writes 1TB of data, the " Total Reduction " will be massive because it counts all that unwritten, " virtual " space as " saved. "

The DRR, however, only looks at the 1TB that was actually written and calculates how well it was compressed and deduped.

Why Option C is incorrect: Both metrics generally account for the efficiency of snapshots. However, snapshots contribute to DRR through deduplication (since they share blocks with the source volume). The massive gap between DRR and Total Reduction is almost always mathematically attributed to the " unwritten " space provided by thin provisioning.

Key Takeaway: If your DRR is 5-to-1 but your Total Reduction is 50-to-1, it means your data is compressing/deduping well, but you have also provisioned a significant amount of volume space that hasn ' t been written to yet.

API Evolution: Pure Storage introduced REST API 2.x to provide a more scalable, standardized, and performant way to automate FlashArray management. It uses a different authentication method (OAuth2 with API Clients) compared to the API Token-based method in 1.x.

Feature Freeze on 1.x: As of Purity 6.x and beyond, Pure Storage has designated REST API 1.x as " Legacy. " While 1.x is still supported for backward compatibility to ensure older scripts don ' t break, all new Purity features (such as specialized ActiveDR commands, advanced File Services, or new hardware capabilities) are only developed and exposed via REST API 2.x .

Side-by-Side Support: Contrary to option C, both versions are supported side-by-side on the same array. An administrator can run a script using 1.x for volume creation and another script using 2.x for performance monitoring simultaneously without contacting support.

Feature Parity: REST API 2.x has long since reached and exceeded the capabilities of 1.x. It offers improved filtering, pagination, and a more consistent object model (e.g., /volumes instead of multiple nested endpoints).

Best Practice: Pure Storage strongly recommends that all new automation projects use REST API 2.x to ensure access to the full suite of Purity features and to future-proof infrastructure-as-code (IaC) workflows.

Edge Services and Gateways: Pure Storage FlashArray uses Edge Services (often associated with FA File or cloud integrations) to manage communication between the array and external services. The Gateway is the component that facilitates this secure connection.

Update Policy Control: To prevent unplanned outages or changes to the environment, Purity includes a safety toggle for Gateway updates. When the status shows " Eligible (updates disallowed) " , it means a newer version of the agent is available on the Pure Storage back-end, but the array ' s local policy is currently set to prevent automatic or manual " one-click " updates.

GUI Authorization: This is a security and administrative control. An administrator with Array Admin privileges must navigate to the Edge Services/Gateway configuration section in the Purity GUI and explicitly change the setting to " Allow Updates " . Once this toggle is enabled, the status will change to " Eligible, " and the update can be initiated.

Why Option A is incorrect: While the CLI is used for many advanced support functions, the puresupport namespace is generally reserved for Pure Storage Support technicians and requires a challenge-response session key. Standard agent updates are handled via the administrative GUI.

Why Option B is incorrect: Removing and re-installing the agent is an unnecessary and disruptive process. The " disallowed " status is simply a policy setting, not a corruption of the agent itself.

For FlashArray File Services (FA File), user authentication and mapping depend on the storage protocol being used. In an NFS-only environment, remote user authentication (resolving UNIX UIDs and GIDs to actual usernames and managing access) is typically handled via LDAP or NIS.

To configure this integration in the Purity GUI, the storage administrator must navigate to Settings > Access > Directory Services . This specific section allows the FlashArray to connect to a centralized directory server (such as OpenLDAP or even Active Directory providing LDAP services) to pull the necessary UNIX user and group attributes required for NFS file permissions to function properly.

Here is why the other options are incorrect:

Settings > Access > Create Active Directory Account (A): This specific menu path is used strictly for configuring native Active Directory (AD) computer accounts and joining the domain to support the SMB (Server Message Block) protocol. Since the scenario explicitly states the company is an " NFS only shop, " configuring an SMB AD account is not the correct step.

Settings > Access > File System (C): While you manage file-level exports and policies within the Purity file interface, the global configuration for remote user authentication and directory server integration lives under the dedicated Directory Services pane.

Modern Monitoring Standards: Pure Storage has built its management ecosystem around the REST API . While traditional methods like SNMP and Syslog are supported for basic health alerts, the REST API provides the depth of data (granularity) and the performance required for modern observability platforms like Prometheus , SolarWinds , and Grafana .

The Pure Storage Exporter: For tools like Prometheus, Pure Storage provides an official " Pure Exporter. " This exporter acts as a bridge; it queries the FlashArray via the REST API to gather real-time metrics (latency, bandwidth, IOPS, capacity) and converts them into the format Prometheus understands.

SolarWinds Integration: SolarWinds utilizes the Pure Storage REST API to pull performance and health data into its storage monitoring modules. This allows for deep-dive historical analysis that exceeds the capabilities of simple SNMP traps.

Why SMI-S (Option B) is incorrect: SMI-S (Storage Management Initiative Specification) is a legacy industry standard that is largely deprecated in favor of RESTful interfaces. Pure Storage does not focus on SMI-S for modern third-party tool integration.

Why SYSLOG (Option C) is incorrect: Syslog is excellent for Event Logging (e.g., " User Logged In, " " Volume Deleted " ), but it is a poor choice for Performance Monitoring . You cannot effectively graph IOPS or bandwidth trends using Syslog streams alone.

When an NFS client successfully mounts an export using the target ' s IP address, it proves that the fundamental network connectivity (routing, firewalls) and the storage protocol layer (NFS export policies, host access permissions) are functioning correctly.

However, if the exact same mount attempt fails when using the Fully Qualified Domain Name (FQDN) of the FlashArray file service, the issue lies entirely with name resolution. The Domain Name System (DNS) is responsible for translating human-readable FQDNs into the IP addresses required for network communication. If the client cannot reach the DNS server, or if the DNS server lacks the correct A or AAAA records for the FlashArray ' s file Virtual IP (VIP) addresses, the client won ' t be able to resolve the name to the IP, causing the mount command to fail.

Here is why the other options are incorrect:

Issue with the Active Directory (AD) controller (A): Active Directory is primarily used for directory services, user authentication, and authorization (such as mapping permissions for SMB or NFSv4). While AD environments usually include DNS, an " AD controller issue " in the context of storage protocols usually points to permission denials, not host name resolution failures. Furthermore, since the mount works via IP, basic access is already validated.

Issue with the OpenLDAP (C): Similar to AD, OpenLDAP provides directory services for user mappings (UID/GID) and authentication. It does not perform FQDN-to-IP resolution.

What is UNMAP?: UNMAP (SCSI command 0x42) is the mechanism that allows a host (like ESXi) to inform the storage array that specific blocks of data are no longer in use (e.g., after a VM is deleted or moved). This is critical for Pure Storage because it allows the array to reclaim that space and maintain high data reduction ratios.

Evolution in ESXi: In versions prior to 6.5, UNMAP was a manual process executed via the CLI. Starting with ESXi 6.7, VMware introduced Automatic Space Reclamation , which runs in the background.

The Pure Storage Recommendation: Pure Storage recommends setting the reclamation priority to Auto with Low Priority .

Low Priority: This ensures that the UNMAP commands are sent to the FlashArray at a steady, manageable rate (roughly up to 25 MB/s to 100 MB/s depending on the Purity version). Because FlashArrays are built on a high-performance metadata engine, " Low Priority " is more than sufficient to keep up with even high-churn environments without causing any contention for active application I/O.

Why avoid High Priority (Option B)?: Setting it to high priority or using a fixed high-burst rate can lead to " bursty " SCSI traffic. While the FlashArray can handle the load, it is considered a best practice to keep background maintenance tasks like space reclamation at a lower priority to ensure the " Big Three " (latency, bandwidth, IOPS) for production workloads remain optimized.

Verification: You can verify that UNMAP is working by looking at the Data Reduction metrics in the Purity GUI or Pure1. If the " Thin Provisioning " or " Reclaimed " numbers are increasing after file deletions, the host is correctly communicating its freed space to the array.

ActiveCluster Mediator Logic: In an ActiveCluster setup, the Mediator is a lightweight component (an " arbiter " ) that resides at a third site (failure domain). Its job is to break the tie in a " split-brain " scenario (when arrays lose connectivity with each other) to determine which array stays online.

Default Behavior: By default, every FlashArray is configured to use the Pure1 Cloud Mediator . This is a managed service provided by Pure Storage that requires no local infrastructure other than internet access from the array controllers.

On-Premises Mediator Deployment: Organizations that cannot use the Cloud Mediator (due to " dark site " security requirements or lack of reliable internet) can deploy the Pure Storage On-Premises Mediator as a small OVF/VM template.

Configuration at the Pod Level: Simply deploying the On-Premises Mediator VM and connecting the arrays to it at the array level is not enough for existing or new pods to switch automatically. In Purity, the mediator preference is a per-pod attribute .

When a pod is created or stretched, it inherits the default (Cloud).

To use the local mediator, the administrator must explicitly configure the pod to point to the On-Premises Mediator’s IP or DNS name. This is done via the CLI using purepod setattr --mediator < address > < pod-name > or through the Pod settings in the GUI.

Why Option C is incorrect: While an A record is necessary for DNS resolution, the prompt implies the mediator is already " deployed " and available. The most common reason it isn ' t being used is simply that the pod hasn ' t been told to look there instead of the default Cloud option.

On a Pure Storage FlashArray, Ethernet ports operate at both a physical hardware layer and a logical network configuration layer. If you need to verify the actual physical negotiated port speed of an Ethernet port (for example, verifying if a 25GbE port negotiated down to 10GbE due to switch configurations or cable limitations), you must query the hardware layer directly.

The command purehw list --all --type eth interacts directly with the physical NIC hardware components to report their true link status, health, and dynamically negotiated hardware link speed.

Here is why the other options are incorrect:

purenetwork eth list -- all (B): The purenetwork command suite is primarily focused on the logical Layer 2/Layer 3 networking stack. It is used to configure and list IP addresses, subnet masks, MTU sizes (Jumbo Frames), and routing, rather than focusing on the physical hardware negotiation details of the NIC itself.

pureport list (A): The pureport command suite is specifically used for managing and viewing storage protocol target ports. An administrator would use this to list the array ' s Fibre Channel WWNs or iSCSI IQNs to configure host zoning or initiator connections, not to verify Ethernet link negotiation speeds.

Pure Storage strongly recommends an MTU size of 9000 (Jumbo Frames) for replication networks—such as those used for Asynchronous Replication, ActiveCluster, and ActiveDR—as well as for iSCSI and NVMe/TCP data networks.

A 9000-byte MTU significantly reduces protocol overhead and CPU processing load on the storage controllers by allowing a much larger payload of data to be transmitted inside a single network packet. During heavy replication, this drastically increases throughput and maximizes bandwidth efficiency.

Here is why the other options are incorrect:

1500 (B): While 1500 bytes is the standard default MTU for Ethernet and is exactly what Pure Storage recommends for the management ports (vir0), it is not the recommended optimization for high-throughput replication traffic. (Note: If your network cannot support 9000 end-to-end, 1500 must be used to prevent packet fragmentation, but 9000 remains the best-practice recommendation).

4200 (A): This is an arbitrary number and is not a standard network MTU size used in Pure Storage environments.

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.

ActiveCluster and Pod Roles: In a Pure Storage ActiveCluster or ActiveDR environment, a Pod is a management container for volumes. To move workloads or perform a planned failover between two arrays, you use the Promote and Demote commands.

The Reversal Process: When you have two pods in a replication relationship (Source and Target), data flows from the Promoted (Active/Source) pod to the Demoted (Passive/Target) pod.

When you Demote the current source, it transitions from a " read-write " state to a " read-only " (passive) state.

If the other pod in the pair is then Promoted , Purity automatically intelligently reverses the direction of replication . The array that was previously receiving data now begins sending incremental updates back to the original source.

Continuous Protection: This design ensures that you don ' t have to manually tear down and recreate replication schedules every time you switch production sites. The system tracks the metadata changes and ensures that only the delta (changed blocks) are sent in the new direction.

Why Option C is incorrect: If replication were simply paused, the two sites would quickly drift out of sync, making it impossible to fail back without a full baseline resync.

Why Option A is incorrect: Demoting a pod does not delete any data; it simply changes the access characteristics and replication role. The data remains fully intact on the storage media.

In Pure Storage Purity OS, the absolute best practice and proper configuration method for sharing a single volume across multiple hosts—such as a VMware ESXi cluster or a Microsoft Windows Server Failover Cluster (WSFC)—is to connect the volume to a Host Group .

When you create a Host Group, you add the individual Host objects (which contain the WWPNs, IQNs, or NQNs) into that group. When a volume is then connected to the Host Group, Purity automatically ensures that the volume is presented to every host in that group using the exact same LUN ID . Consistent LUN IDs across all nodes in a cluster are a strict requirement for clustered file systems like VMFS and Cluster Shared Volumes (CSV) to function correctly and prevent data corruption.

Here is why the other options are incorrect:

Connect the volume to each individual host (C): This is known as creating " private connections. " If you manually connect a shared volume to multiple hosts individually, Purity might assign a different LUN ID to the volume for each host. Inconsistent LUN IDs will cause clustered operating systems to fail to recognize the disk as a shared resource. Private connections should only be used for boot LUNs or standalone standalone servers.

Connect a volume group to the host (B): In Purity, a " Volume Group " is a logical container used for applying consistent snapshot policies, replication schedules, or ActiveCluster configurations to a set of related volumes (like a database and its log files). Volume groups are not used for host presentation or access control.

On a Pure Storage FlashArray, volume snapshots are immutable, read-only, point-in-time representations of your data. Because they cannot be attached directly to a host to be read or modified, you must use the Copy function to make the data usable.

The Purity operating environment allows you to copy a snapshot to two specific destinations:

A new volume: This effectively creates a clone. It provisions a brand-new, writable volume using the exact data footprint of the snapshot. This is incredibly useful for test/dev environments, offline reporting, or granular file recovery where you don ' t want to disrupt the original production volume.

An existing volume: This takes the data from the snapshot and completely overwrites the target volume. This is the standard procedure when you need to perform a full rollback of a corrupted volume, or when you want to quickly refresh a lower-level environment (like refreshing a QA database with yesterday ' s Production snapshot).

Here is why the other options are incorrect:

A new Snapshot (B & C): You cannot directly " copy " a snapshot to create another standalone snapshot. Snapshots are uniquely generated from active volumes. If you wanted to duplicate a snapshot ' s exact state, you would first copy it to a volume, and then take a new snapshot of that resulting volume.

When physical links fail to establish—especially when using Direct Attach Copper (DAC) cables or Twinax—the most common culprit is a hardware compatibility mismatch. Pure Storage arrays have specific requirements for optics and cabling to ensure optimal signal integrity and performance.

The FlashArray Transceiver and Cable Support article (available on the Pure Storage Support portal) is the authoritative, verified resource for this scenario. It provides a comprehensive, constantly updated compatibility matrix detailing exactly which vendor DAC cables (e.g., Cisco, Brocade, Arista) and transceivers are officially validated and supported for use with specific FlashArray models and port types. If an unsupported DAC cable is used, the switch or host bus adapter (HBA) on the array might simply refuse to bring the link up.

Here is why the other options are incorrect for this specific issue:

The FlashArray User Guide (A): This guide is excellent for day-to-day administration (volume creation, host grouping, etc.) but is too broad to contain granular, constantly updating hardware compatibility matrices for specific cables.

The Port Usage and Definitions article (C): This document explains the logical and physical purpose of the ports on the back of the controllers (e.g., defining which ports are used for management, replication, or host connectivity), but it does not dictate hardware transceiver or cable interoperability.