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

Interface Separation: Pure Storage FlashArrays distinguish between Management traffic (used for the GUI, CLI, and Pure1 connectivity) and Data traffic (used for host connectivity). Within the data path, File Service Interfaces are the logical interfaces assigned to handle NFS and SMB traffic.

Directory Service Communication: For FA File to function, it must communicate with external identity providers (like Microsoft Active Directory or OpenLDAP) to authenticate users and resolve permissions.

The Default Path: By design, Purity prioritizes the File Service Interfaces for these lookups. This is because the directory servers (Domain Controllers) are typically located on the same production/data network as the clients accessing the files. Using the File Service Interface ensures that authentication traffic follows the same network path and security rules as the data traffic itself.

Why Option B is incorrect: While the array management plane can use the management interfaces for its own administrative LDAP/SAML logins, the File Services component defaults to the data-path (File) interfaces to avoid " crossing the streams " between management and production data networks.

Why Option C is incorrect: Purity is very specific about its routing tables. It does not blindly use " all " interfaces for DNS/Directory services. If a File Service interface is configured and active, it becomes the primary egress point for file-related metadata and authentication requests.

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.

In the Pure Storage ecosystem, " Meta fingerprinting " refers to the core technology behind Pure1 Meta , which is Pure ' s cloud-based artificial intelligence and machine learning engine. Pure1 collects thousands of data points of telemetry (metadata) from all connected FlashArrays globally every day.

By analyzing this vast amount of telemetry data, Pure1 Meta creates workload signatures or " fingerprints. " It then continuously compares your array ' s telemetry footprint against the global pool of arrays. The major benefit of this is that it enables predictive support . If Pure1 Meta detects that your array ' s fingerprint matches a known issue experienced by another array elsewhere in the world, Pure Storage can proactively alert you, open a support ticket, or recommend a Purity upgrade before you ever experience an outage or performance impact. It also uses these fingerprints for highly accurate capacity and performance forecasting.

Here is why the other options are incorrect:

Provides security for Remote Assist (RA) (A): Remote Assist allows Pure Support to log into your array for troubleshooting, but its security is based on a customer-initiated, secure outbound TLS connection (tunneling), not meta fingerprinting.

Ensures biometric security (B): This is a distractor. " Fingerprinting " in the context of Pure Storage refers to data and workload profiling, not human biometric authentication like physical fingerprint scanners.

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.

When configuring NVMe/TCP (or iSCSI) for optimal performance on a Pure Storage FlashArray, configuring Jumbo Frames (an MTU of 9000) end-to-end is a standard best practice.

The command ping -M do -s 8972 < ip_addr > is specifically used to verify Jumbo Frame configuration across the network.

The -M do flag sets the " Do Not Fragment " (DF) bit, meaning the network is not allowed to break the packet into smaller pieces.

The -s 8972 flag sets the ICMP data payload to 8972 bytes. When you add the standard 8-byte ICMP header and the 20-byte IP header, the total packet size equals exactly 9000 bytes.

If this ping command fails, it indicates that somewhere along the network path between the host (initiator) and the FlashArray (target), a switch port, router, or network interface is not configured to support an MTU of 9000. The packet is being dropped because it is too large and cannot be fragmented. The administrator must verify the MTU settings on every network hop (switches, routers, and host NICs) to resolve the issue.

Here is why the other options are incorrect:

Engage support to enable NVME/ TCP services (A): The failure of a Jumbo Frame ping test is a Layer 2/Layer 3 network configuration issue, not an indicator that the NVMe/TCP storage protocol service is disabled on the array.

Run the command from the target (C): While pinging from the FlashArray back to the host is a valid secondary troubleshooting step, it will likely also fail if the network path doesn ' t support Jumbo Frames. The actual resolution is to fix the MTU on the network hops.

Definition of Unified Storage: In the storage industry, " Unified Storage " refers to a platform that can natively serve both Block-level storage (accessed via protocols like Fibre Channel, iSCSI, or NVMe-oF) and File-level storage (accessed via protocols like NFS or SMB) from a single pool of capacity and under a single management interface.

Pure Storage Implementation (FA File): Pure Storage achieved unified storage on the FlashArray through the introduction of Purity//FA File Services . Unlike traditional unified storage that often required a " gateway " or separate hardware " heads, " Pure’s implementation runs natively on the FlashArray controllers.

Shared Resources: On a unified FlashArray, the global storage pool is shared between volumes (Block) and file systems (File). All of Pure’s core data services—such as deduplication, compression, and SafeMode snapshots —apply globally across both block and file data.

Protocol Diversity: While Option A mentions NFS and SMB, those are strictly File protocols. Option C mentions iSCSI and FC, which are strictly Block protocols. Only Option B correctly identifies the combination of Block and File , which defines the " Unified " architecture of the FlashArray.

As Pure Storage has iterated through FlashArray generations (moving from //X R2 to R3, R4, and beyond), the power density and performance capabilities of the controllers have increased significantly. Modern high-performance controllers, such as those found in the //X R4 or //XL series, have strict power requirements that often exceed what a standard 110V/120V (Low-Line) circuit can provide.

To support the higher wattage and current draw of modern CPUs and NVRAM modules, Pure Storage requires 200-240V (High-Line) power for its latest generation controllers. If an existing array is currently running on 110V power, it must be migrated to 220V power outlets before the upgrade can proceed. Attempting to run newer, high-spec controllers on 110V power could lead to power supply instability, insufficient cooling performance, or the controllers failing to boot entirely.

Here is why the other options are incorrect:

Call support to schedule a power supply replacement (A): The issue is not a faulty power supply; it is the external electrical infrastructure ' s inability to provide the necessary voltage/wattage for the new hardware. Replacing the power supply with the same model would not solve the voltage limitation.

Transition the array to DC power (B): While Pure Storage does offer DC power options for specific telco environments, this is not a standard requirement for a typical controller upgrade. Moving to standard high-line AC power (220V) is the standard prerequisite for data center environments.

Analyzing the Graph: The provided capacity graph shows a sharp, vertical drop in Unique and Shared space (the teal/green sections) at approximately 10:45. Simultaneously, there is a massive spike in System space (the grey shaded area).

The " System " Space Spike: In Purity, when a volume is deleted and eradicated, the data isn ' t physically wiped from the flash modules instantly. Instead, the logical references are removed, and the blocks are moved into a " Pending Reclamation " state. In older versions of Purity reporting (or specific views), this pending work is often categorized under System space until the background Garbage Collection (GC) process can physically reclaim it.

The Decay Curve: Notice the grey " System " area gradually tapers down over the following hours (from 11:00 to 14:00). This is the visual representation of the array ' s Garbage Collection engine working in the background to physically free up those blocks.

Why Option C is incorrect: If SafeMode were enabled, the space would not move into " System " space in this manner; it would remain locked in the Snapshots or Destroyed bucket for the duration of the retention period, preventing the graph from dropping at all.

Why Option A is incorrect: If space reclamation stopped working, the grey " System " area would stay flat and would not decay over time. The fact that it is trending downward proves that reclamation is actively processing the deleted volume.

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.

The ActiveCluster Mediator (whether it is the Pure1 Cloud Mediator or the On-Premises VM) is a lightweight tie-breaker that communicates continuously with the management interfaces of both FlashArrays. If it was previously online and suddenly reports as " unreachable " from both arrays simultaneously, the issue is almost always caused by a network interruption or firewall rule change blocking the required communication ports between the arrays ' management IP addresses and the Mediator VM.

If a network firewall is suddenly configured to drop or deny outbound TCP traffic (such as port 80/443 depending on the specific HTTP/HTTPS discovery and heartbeat configuration) from the FlashArrays to the ESXi-hosted Mediator, the arrays will fail to send their heartbeats, causing the mediator status to drop to " unreachable. "

Here is why the other options are incorrect:

Fibre Channel (FC) zoning or network access has not been created properly for the host (A): The Mediator is completely independent of the front-end host storage fabric (Fibre Channel or iSCSI). Host zoning issues would prevent the ESXi server from seeing its volumes, but it would not cause the FlashArrays to lose management network connectivity to the Mediator.

The mediator does not reside within a Pure datastore (B): This is actually a strict best practice and requirement . Pure Storage explicitly states that the On-Premises Mediator VM must be deployed in a separate (third) failure domain. It should not reside on the ActiveCluster mirrored datastore, because a site-wide SAN failure would take the mediator offline exactly when it is needed most. Therefore, not residing on a Pure datastore is the correct setup, not a cause for an outage.

Understanding the Audit Log: In Purity, accountability and security are maintained through the Audit Log . This log captures every administrative action taken on the array, whether through the GUI, CLI, or REST API. It records who performed the action, what the action was (e.g., volume creation, host deletion), and when it occurred.

The CLI Command: The command pureaudit list is the specific CLI tool used to display these logs. By default, it lists events in chronological order, making it the perfect tool for an administrator to review " shift change " activities.

Command Options: * pureaudit list can be filtered with flags like --user to see actions by a specific admin, or --start-time and --end-time to narrow down the " previous shift " window.

Why Option C is incorrect: puremessage (accessed via puremessage list) is used to view Alerts and Notifications generated by the system (e.g., a failed drive or a high-temperature warning). While it tells you what the array did, it does not track what users did.

Why Option A is incorrect: This is not a valid Purity command syntax. Purity does not use double-dashes to " pipe " or combine independent commands like pureaudit and puremessage in that manner.

Understanding CRC Errors: CRC (Cyclic Redundancy Check) errors occur when the data received at a port does not match the checksum sent by the initiator or switch. In a Pure Storage environment, these are tracked per port and can be viewed via the CLI (purehw list) or the GUI.

Configuration vs. Hardware: While a failing SFP or a damaged fiber cable can cause CRC errors, they are a primary indicator of configuration mismatches in the SAN fabric. Common culprits include:

Port Speed Mismatches: Manually setting a port to 16Gbps when the switch is set to " Auto " or 8Gbps.

Duplex Mismatches: Though rare in modern Fibre Channel, it is a classic Ethernet/iSCSI configuration error.

MTU Mismatches: In iSCSI or NVMe-oF environments, if the FlashArray is configured for Jumbo Frames (MTU 9000) but the switch or host is at MTU 1500, packet fragmentation or CRC-like errors/drops will occur.

Why Option A is incorrect: A blinking status LED on a controller is often part of normal operation (indicating heartbeat or activity). A solid amber LED would be an indicator of a hardware failure, not necessarily a misconfiguration.

Why Option C is incorrect: While latency spikes can be caused by misconfiguration (like incorrect MPIO settings), they are more commonly symptoms of workload changes , " noisy neighbors, " or reaching the physical performance limits of the array. CRC errors are a much more specific diagnostic " smoking gun " for port and fabric configuration issues.

Best Practice: When CRC errors are detected, Pure Storage recommends first checking the physical layer (reseating SFPs/cables) and then verifying that the port speed and protocol settings on the FlashArray match the upstream switch configuration exactly.

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.

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.

To provide true real-time data and alerts directly to a Network Operations Center (NOC) dashboard, the information must be sourced directly from the FlashArray . The FlashArray ' s Purity operating environment natively supports real-time data streaming and alerting integrations via protocols like Syslog, SNMP traps, and the local REST API. Polling the array directly or configuring it to push alerts guarantees that the NOC receives instantaneous, up-to-the-second notifications regarding array health, hardware faults, and performance metrics.

Here is why the other options are incorrect:

Pure1 (B): While Pure1 is Pure Storage ' s powerful, cloud-based monitoring and predictive analytics platform, it relies on phone-home telemetry data. This telemetry is batched and transmitted from the array to the Pure1 cloud on a short polling interval (typically a few minutes). Because of this transmission and processing interval, Pure1 provides near-real-time (lagging by a few minutes) and historical data. It is excellent for global fleet management and predictive support, but not for instantaneous, zero-latency NOC alerting.

Pure Performance Monitoring (A): This is a distractor. There is no standalone product or specific protocol in the Pure Storage ecosystem officially named " Pure Performance Monitoring. " Performance monitoring is simply a feature accessed via the FlashArray GUI/CLI or the Pure1 platform.

Command Purpose: The purehost monitor command is the primary tool in the Pure Storage CLI for observing real-time performance and connectivity health from the perspective of the hosts connected to the FlashArray.

The --balance Flag: When the --balance flag is added, the output shifts from general performance (IOPS, bandwidth, latency) to showing how I/O is distributed across the available paths (controllers and ports). This is critical for identifying " unbalanced " loads, which usually point to misconfigured MPIO (Multi-Path I/O) on the host side (e.g., a host only using one controller ' s ports).

Interval vs. Repeat:

The --interval flag specifies the time in seconds between each sample. In option C, --interval 15 tells the array to refresh the data every 15 seconds.

The --repeat flag (seen in option A) is used to limit the total number of samples taken before the command exits. However, in standard troubleshooting, the administrator typically wants a consistent stream of data until manually stopped (Ctrl+C).

--resample (seen in option B) is not a valid flag for the purehost monitor command in Purity.

Best Practice: When troubleshooting multipathing, Pure Storage recommends monitoring the balance to ensure that the " Relative I/O " percentage is roughly equal across all active paths. Large discrepancies often indicate that the host ' s MPIO policy is set to " Failover Only " instead of the recommended " Round Robin " or " Least Queue Depth. "

Understanding the Load Meter: The Load Meter in Pure1 and Purity represents the percentage of the array ' s performance capacity currently being utilized. It takes into account CPU cycles, back-end metadata processing, and front-end I/O. A 90% load means the controllers are nearly saturated.

The Impact of Capacity on Load: As a FlashArray fills up (specifically beyond 80% ), the Purity Operating Environment must work harder to find and organize free space. This " Garbage Collection " (GC) process becomes more intensive, which consumes more controller resources and contributes to a higher Load Meter reading.

Internal System QoS: To ensure the stability and integrity of the storage, Pure Storage uses Internal Quality of Service (QoS) . This is an " always-on " feature that prioritizes critical system processes (like metadata updates, internal health checks, and data protection) over incoming host I/O during periods of extreme resource contention.

Graceful Performance Pacing: When the load is consistently high (like the 90% described), Purity may introduce small amounts of latency to the host I/O (often seen as " Wait " or " Queue " time) to " pace " the workload. This prevents the controllers from reaching a 100% " locked " state, ensuring the array remains responsive and healthy even under heavy pressure.

Why Option C is incorrect: While the array needs to reclaim space, prioritizing Space Reclamation (a background task) during a 90% performance load would likely push the controllers to 100% load, causing significant latency spikes or instability for the host. The system must balance reclamation with active production I/O.

When new DirectFlash Modules (DFMs) or data packs are physically inserted into a Pure Storage FlashArray, the Purity operating environment detects the new hardware but places the drives in an " unadmitted " state. This safety mechanism prevents the accidental incorporation of drives and allows the system to verify the firmware and health of the modules before they are actively used to store data.

To formally accept these drives into the system ' s storage pool so their capacity can be utilized, the administrator must execute the CLI command puredrive admit. Once this command is run, the drive status transitions from " unadmitted " to " healthy, " and the array ' s usable capacity expands accordingly.

Here is why the other options are incorrect:

pureadmin -- admit-drive (A): This is syntactically incorrect. The pureadmin command suite is used for managing administrator accounts, API tokens, and directory services, not for hardware or drive management.

purearray admit drive (B): This is also incorrect syntax. While purearray is used for array-wide settings and status (like renaming the array or checking space), specific drive-level operations are exclusively handled by the puredrive command structure.

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.