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

ActiveDR is Pure Storage’s continuous, near-sync replication solution. It differs fundamentally from standard asynchronous replication because it uses a continuous stream of data rather than snapshot-based " periodic refreshes " (which eliminates Option A).

When you perform a test failover in ActiveDR, you do so by promoting the target pod . The target pod becomes writable, allowing your hosts and applications to run against the replicated data without disrupting the ongoing continuous replication from the source array in the background.

When the test is completed, you demote the target pod. To ensure that the data generated during your test failover isn ' t accidentally lost forever, ActiveDR automatically creates an undo pod at the exact moment of demotion.

If you need to resume that exact test failover scenario or recover the test data, you can re-promote the target pod and instruct ActiveDR to present the content from the undo pod . This unique mechanism allows storage administrators to seamlessly non-disruptively test, pause, and resume DR environments without affecting production protection.

Local Array Limitations: The FlashArray GUI and CLI maintain a local buffer for audit logs (which track commands, logins, and configuration changes). However, this local storage is limited in size and record count (typically around 1000 records or a short timeframe) to ensure that logging does not consume excessive system resources on the controllers. Once the limit is reached, older records are overwritten (FIFO - First In, First Out).

Pure1 as the Historical Repository: Pure1 is Pure Storage’s cloud-based management and monitoring platform. One of its primary functions is to act as a long-term repository for array data. FlashArrays " phone home " their audit logs to Pure1, where they are indexed and stored for much longer periods (typically up to one year or more, depending on the subscription level).

Auditing in Pure1: By logging into the Pure1 portal, an administrator can navigate to the Audits section. Unlike the local GUI, Pure1 allows users to filter by specific date ranges, specific arrays, and specific users across the entire fleet. This makes it the standard tool for security audits and compliance reporting.

Why Option A and C are incorrect: * Option A: While the CLI is powerful, it still pulls from the same limited local buffer as the GUI. If the record has been overwritten locally, the CLI cannot retrieve it.

Option C: Purity does not typically allow customers to modify " tunables " to increase log storage, as this could impact the stability or performance of the Purity Operating Environment.

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.

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.

In any NVMe-based storage fabric (including NVMe/TCP, NVMe/FC, and NVMe/RoCE), the standard method for identifying endpoints and enforcing device-level access control is the NQN (NVMe Qualified Name) .

The NQN serves the exact same purpose in the NVMe protocol as an IQN (iSCSI Qualified Name) does in an iSCSI environment, or a WWPN (World Wide Port Name) does in a Fibre Channel environment. It is a unique identifier assigned to both the host (initiator) and the storage array (target subsystem). When setting up access control on a Pure Storage FlashArray, the storage administrator must capture the Host NQN from the operating system and configure a Host object on the array with that specific NQN. This ensures that only the authorized host can discover, connect to, and access its provisioned NVMe namespaces (volumes).

Here is why the other options are incorrect:

VLANs (A): Virtual LANs are used for network-level isolation and segmentation at Layer 2 of the OSI model. While you might use a VLAN to separate your storage traffic from your management traffic, it is a network security measure, not a device-level access control mechanism for the storage protocol itself.

LACP (C): Link Aggregation Control Protocol (LACP) is a network protocol used to bundle multiple physical network links into a single logical link for redundancy and increased bandwidth. It has nothing to do with storage access control or mapping volumes to hosts.

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. "

User Mapping in FA File: On a Pure Storage FlashArray, User Mapping is the mechanism that translates identities between different protocols (like mapping a Windows SID to a Unix UID/GID) or between an external directory service (like Active Directory or LDAP) and the local file system permissions.

The Impact of Disabling Mapping: When User Mapping is disabled on an active NFS export, the FlashArray can no longer resolve the identity of the user attempting to access existing files. Because NFS (specifically NFSv3 and NFSv4.1 supported by Pure) relies on these identifiers to verify file ownership and ACLs, existing files—which are tagged with specific owner IDs—become effectively " orphaned " from the perspective of the incoming request.

Access vs. Creation: * Existing Files: Accessibility is lost because the system cannot verify that the user has the rights to read or modify the file without the mapping logic.

New Files: Interestingly, in many " No Mapping " configurations, a user may still be able to create new files (often defaulting to a ' nobody ' or ' anonymous ' UID depending on the export rules), but they will immediately lose the ability to manage or access them once created because the mapping link is broken.

Real-time Application: Unlike some legacy storage systems that require a service restart, Purity applies export policy changes dynamically . As soon as the " User Mapping " toggle is disabled, the logic is removed from the data path, impacting active sessions immediately.

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.

Pure Storage FlashArrays utilize Thin Provisioning as a core, always-on architectural principle. When a volume is created, the " size " assigned to it is merely a logical limit (a quota) presented to the host; no physical back-end flash capacity is allocated or " pinned " at the time of creation.

Because of this architecture, Purity allows administrators to create volumes that are significantly larger than the actual physical capacity of the array (this is known as over-provisioning). If an administrator accidentally selects PB (Petabytes) instead of GB, the Purity GUI will allow the volume to be created because it is a logical operation that doesn ' t immediately consume 1PB of physical flash. However, Purity includes a built-in safety check: if the requested logical size is exceptionally large or exceeds the current physical capacity of the array, the GUI will present a warning or confirmation prompt to ensure the administrator is aware of the massive logical size being provisioned before finalizing the change.

Here is why the other options are incorrect:

The volume will be created and space will immediately be used (A): This describes " Thick Provisioning, " which Pure Storage does not use. Space is only consumed on a FlashArray when unique data is actually written by the host and processed by the deduplication and compression engines.

The volume will not be created and a warning will be displayed (C): Purity does not strictly forbid over-provisioning. While it warns the user to prevent human error, it does not block the creation of the volume, as over-provisioning is a standard practice in thin-provisioned environments.

Pure1 Manage Capabilities: Pure1 is a SaaS-based platform that provides a " single pane of glass " view across an entire fleet of FlashArrays. It excels at aggregating metrics that are otherwise siloed on individual arrays.

Specialized File Metrics: Because FlashArray File (FA File) operates as a specific service layer within Purity, its performance metrics (NFS/SMB latency, throughput, and IOPS) are tracked separately from traditional block storage.

The File Systems Performance Report: This specific report/view in Pure1 allows administrators to:

Select multiple file systems residing on different arrays.

Overlay their performance graphs to identify trends or outliers.

Filter by specific protocol (NFS vs. SMB) to see how different workloads are behaving across the infrastructure.

Why Options B and C are less ideal:

Overview Dashboard: While great for a " health at a glance " check (showing total capacity and high-level alerts), it does not provide the granular, side-by-side performance comparison required for a deep-dive analysis.

Array Performance: This report typically shows the total load on the controllers. While this includes file traffic, it often aggregates it with block traffic, making it difficult to isolate how the file services specifically are performing across the fleet.

Analytical Advantage: Using the File Systems Performance report allows the administrator to correlate performance spikes with specific file-level events, such as a large backup job or a high-intensity data migration occurring on one array versus another.

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.

Replication Fundamentals: On a Pure Storage FlashArray, replication is a snapshot-based process . To replicate a Protection Group (pgroup) to a target array, the system must first create a point-in-time snapshot of the volumes within that group on the source array.

The " Immutable " Rule: Even if the Local Snapshot Schedule is disabled, the act of replicating requires the existence of a local snapshot to serve as the " base " or " source " for the data transfer. Purity does not stream data directly from the active volume to the wire; it creates a snapshot and then replicates the unique blocks contained in that snapshot.

Accounting for Local Copies: When a Protection Group is configured for replication, every snapshot generated by the Replication Schedule is stored locally on the source array. These snapshots will remain on the source array until they are aged out according to the Local Retention policy (even if the local schedule itself is off, the retention policy still applies to those replicated snapshots).

Visibility: If you navigate to the Protection Group in the Purity GUI, you will see these snapshots listed under the " Snapshots " tab. They are functionally identical to local snapshots, meaning they can be used for local clones or restores without needing to pull data back from the target array.

Why Option A and C are incorrect: * Option A: If 0 snapshots were stored, there would be nothing to replicate.

Option C: While Purity uses the most recent snapshot as a reference for delta-tracking, it keeps the entire history of snapshots defined by your retention policy, not just a single one.

On a Pure Storage FlashArray, " System Space " is a specific GUI-reported metric. Purity has a predefined, hidden internal space budget—typically around 20% of the raw mapped capacity (which would be 2TB on a 10TB array)—reserved for internal array operations. This budget covers RAID/parity overhead, metadata, and reclaimable space (data from deleted volumes, snapshots, or overwritten blocks that are waiting for the backend garbage collection process to fully erase them from the flash chips).

Normally, this internal overhead stays below the 20% budget, and " System Space " displays as 0.00 in the GUI. However, if an administrator deletes a massive amount of data at once, causing the reclaimable space to exceed that 2TB budget, the overflow is prominently displayed in the GUI as " System Space. "

Here is why the other options are incorrect:

Virtual machines have not yet issued an unmap command (A): If a VMware VM deletes a file but the OS hasn ' t issued an UNMAP/TRIM command, the FlashArray is completely unaware that the data was deleted. Therefore, the array continues to report that capacity as standard Volume Space , not System Space.

More than 2TB of volume snapshots were destroyed (C): While destroying snapshots leads to reclaimable space, " reclaimable space " (Option B) is the specific, correct Purity architectural term and metric that the system uses to calculate the internal budget threshold.

In Pure Storage FlashArray File Services (Purity//FA), administrators can apply Quota Policies to managed directories to control and monitor capacity consumption. When configuring the rules for these quotas, the limits are categorized into two specific types: Enforced and Unenforced .

Enforced Quotas (Hard Limits): When a quota rule is set with the --enforced flag set to True , it acts as a hard boundary. If the users or applications writing to that managed directory hit the specified capacity limit, the FlashArray will actively block any further write operations, ensuring the directory cannot exceed its allocated space.

Unenforced Quotas (Soft Limits): When a quota rule is unenforced (the flag is set to False ), it acts purely as a monitoring and alerting threshold. Users can continue to write data and organically grow the directory past the specified limit without application disruption, but the system will track the overage and trigger administrative notifications.

Here is why the other options are incorrect:

File and Block (A): This describes the two underlying storage protocols/architectures the unified FlashArray serves, not the types of capacity quota limits for directories.

Limited and Unlimited (B): While you can theoretically leave a file system to grow " unlimited " up to the size of the array, the specific technical parameters in the Purity quota policy engine are defined as enforced vs. unenforced.

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.

The Concept of Root Squash: In the world of NFS, " Root Squashing " is a fundamental security feature. By default, most modern storage systems (including FlashArray File Services) do not trust the " root " user of a remote client. This prevents a user with administrative access on a random laptop or server from gaining full administrative control over the files on the central storage.

Mounting vs. Accessing:

Mounting: This is the process of attaching the remote export to the local file system. If the Export Policy allows the client IP to connect, the mount will succeed.

Accessing: Once mounted, the array evaluates the identity of the user. If Root Squash is enabled, the array " squashes " the root user (UID 0) and maps it to a non-privileged user (usually nobody or anonymous ). Consequently, the client ' s root user loses their administrative permissions when trying to read/write files.

The Export Policy Setting: The behavior described (able to mount but permission denied for files as root) is almost always caused by the User ID Mapping or Access rules within the Export Policy .

To resolve this, an administrator must edit the specific rule in the Export Policy and enable " No Root Squash " (or change the mapping to allow root access). This tells the FlashArray to honor the client ' s root identity.

Why Options A and B are incorrect:

Managed Directory: This is where you set the directory structure and quotas, but it doesn ' t control the protocol-level identity mapping.

File System: While a file system has underlying permissions, if the mount is successful but specifically blocks the root user, the " gatekeeper " is the Export Policy rule.

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.

What is SafeMode Ratcheting?: SafeMode is Purity ' s " immutability " feature that prevents snapshots from being deleted, eradicated, or modified, even by an administrator with compromised credentials. Ratcheting is the process of increasing the protection levels (like extending the retention period) for a protection group (pgroup) to ensure even stricter data safety.

The Dependency on Local Snapshots: SafeMode ' s primary function is to protect point-in-time copies of data residing on the array. For a protection group to be " ratcheted " into a SafeMode-protected state, it must have an active Local Snapshot Schedule .

Why Option C is the Constraint: If a protection group does not have a local snapshot schedule, there are no local snapshots being generated for SafeMode to " lock. " SafeMode cannot protect what doesn ' t exist locally. While a pgroup might be used for replication only, SafeMode requires the local scheduling component to be active and configured to apply its immutable retention policies.

Why Option B is incorrect: Protection groups are designed to contain hosts, host groups, or volumes. This is the standard way to group related data for snapshot consistency and has no negative impact on SafeMode eligibility.

Operational Note: When you enable SafeMode on a protection group with a local schedule, the " Erradicate " button for those snapshots is disabled. To " ratchet " the protection, you typically work with Pure Storage Support to ensure the retention settings meet your compliance needs.

Within the Pure Storage ecosystem, the absolute best method to troubleshoot and pinpoint the exact source of VMware latency is to use VM Analytics (VM Topology) in Pure1 .

VM Analytics is a feature built directly into Pure1 that maps the entire data path from the virtual machine all the way down to the physical FlashArray. It provides a visual topology map detailing the VM, Virtual Disk, ESXi Host, Datastore, and FlashArray Volume. By analyzing performance across this topology, an administrator can instantly identify exactly where the latency is being introduced. For example, you can clearly see if the latency spikes at the ESXi host layer (indicating compute contention) or the network layer, even if the FlashArray volume itself is reporting sub-millisecond latency at the storage level.

Here is why the other options are incorrect:

Analyze load metrics in Pure1 for each volume in the user ' s data path (C): Looking exclusively at volume-level metrics on the FlashArray will only tell you the latency from the array ' s perspective. If the latency is being caused by an overloaded ESXi host CPU or a saturated SAN fabric, the FlashArray metrics will look perfectly healthy, and you will fail to identify the source of the problem.

Analyze performance charts in vSphere for CPU, Memory, Network, and Storage Path for the user ' s data path (B): While vCenter performance charts are useful, they often lack deep storage-array-level context. Pure1 ' s VM Topology is the " best " method because it correlates the vSphere stack data with the native FlashArray telemetry data in a single, unified view, making full-stack root cause analysis much faster.