Get Pure Storage FlashArray-Storage-Professional Exam Practice Questions - Real and Updated

Answer : B

ActiveCluster Connectivity Models: In an ActiveCluster environment, hosts can connect to the arrays using either a Uniform or Non-Uniform access model. In a Uniform model, the host has active paths to both FlashArrays in the cluster.

The Failover Scenario: When the replication network between the two arrays fails (a 'split-brain' scenario), the Mediator decides which array keeps the pod online (the winner) and which array takes it offline (the loser) to ensure data consistency.

Analyzing the Symptoms:

The pod failed over, meaning one array is now the exclusive servicer for that pod.

Most volumes in that pod stayed online for the host. This proves that the host is correctly registered in Purity (ruling out Option C) and that the general ActiveCluster/Pod logic is functioning.

Only one specific volume lost connectivity.

The Root Cause (Zoning/Access): If a single volume loses connectivity while others do not, it indicates a pathing issue specific to that volume's visibility. In an ActiveCluster failover, if the 'winning' array does not have a physical path to the host for that specific volume (due to missing FC Zoning or Ethernet VLAN tagging on the switches), the host will lose access once the 'losing' array drops its paths.

Why Option A is unlikely: If 'Uniform access' (the ability to see both arrays) was the issue, it would typically affect all volumes in the pod equally during a failover, not just a single outlier. The fact that the rest of the volumes remained available suggests the host is configured for uniform access, but the specific network plumbing (zoning) for that one volume's path to the surviving array is missing.

!

Answer : C

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.

Answer : B

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.

Answer : C

Understanding Space Reporting: To understand this behavior, you have to look at how Purity calculates capacity. Pure Storage uses a data reduction engine where data is deduplicated and compressed.

Volume Space vs. Shared Space:

Volume Space: This represents the unique data belonging to a specific volume that is not shared with any other volume via deduplication or snapshots.

Shared Space: This represents the data that is common across multiple volumes or snapshots. If you have two volumes that are clones of each other, most of that data is 'Shared.'

The 'Shift' Mechanism: When a volume is deleted (and potentially eradicated), the data it once shared with other volumes no longer needs to be 'shared.'

Imagine Volume A and Volume B share 100GB of data. That 100GB is accounted for in Shared Space.

If you delete Volume B, that 100GB of data is now only referenced by Volume A.

Consequently, that 100GB is moved from the Shared Space bucket into Volume A's Volume Space bucket.

Net Result: The total physical space used on the array remains the same initially, but the accounting shifts. You see a decrease in Shared Space and an identical increase in the Volume Space of the remaining volumes that held those deduplication references.

Answer : A

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.