Pass the Pure Storage FlashArray Storage FlashArray-Storage-Professional Questions and answers with Dumpstech

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.

Requirement for Lossless Ethernet: NVMe over RoCE (RDMA over Converged Ethernet) requires a lossless fabric to function correctly. Unlike standard iSCSI which uses TCP for error recovery, RoCE assumes the network will not drop packets. If the network is " lossy, " performance degrades significantly.

The Role of PFC: Priority Flow Control (PFC) (IEEE 802.1Qbb) is the specific mechanism used in Data Center Bridging (DCB) to provide flow control on a per-priority basis. It allows the switch to send a " pause " frame to the sender when buffers are full, preventing packet drops.

Symptom Analysis: In the scenario provided, the array itself is not overloaded ( " within the performance envelope " ). However, the addition of a new workload increased traffic to the point where buffer congestion occurred. Because PFC was likely misconfigured (either on the FlashArray ports, the network switches, or the host NICs), the network dropped packets instead of pausing traffic. This leads to " go-back-N " retransmissions and massive latency spikes that affect all workloads sharing that fabric.

Pure Storage Best Practices: Pure Storage documentation for NVMe-RoCE emphasizes that PFC must be enabled and consistent across the entire path. If there is a mismatch in PFC configuration, the resulting packet loss will cause the symptoms described: extreme latency and potential service outages.

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.

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.

SNMP Capabilities on FlashArray: Pure Storage FlashArrays support SNMP (Simple Network Management Protocol) versions v2c and v3. The primary use case for SNMP on the FlashArray is for integration with third-party monitoring tools (like SolarWinds, Nagios, or Zabbix) to provide a real-time health and performance heartbeat.

Performance Metrics (MIBs): The Pure Storage Management Information Base (MIB) specifically exposes high-level array performance metrics. These include the " Big Three " of storage performance: Latency (response time in microseconds), Bandwidth (throughput in bytes per second), and IOPS (I/O operations per second).

Scope of Monitoring: While the FlashArray GUI and CLI provide deep granularity (per host, per volume, or per pod), standard SNMP queries typically focus on array-wide performance and health status. Detailed " Host and volume performance " (Option B) is generally more effectively monitored via the Pure Storage REST API or the Pure1 VM Analytics, as SNMP is less efficient for pulling large tables of per-object data.

Capacity vs. Performance: While SNMP can report on capacity (Option C) through specific OIDs, the question specifically asks about performance statistics . In the context of Pure Storage monitoring documentation, the core performance metrics provided via SNMP traps and polling are latency, bandwidth, and IOPS.

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.

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.

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.

According to official Pure Storage documentation regarding Asynchronous Replication management, while replication throughput (bandwidth) can be viewed globally on the Analysis tab, the actual replication status for in-progress snapshot transfers is tracked and monitored on the replication target .

To monitor an in-progress asynchronous transfer from the GUI, a storage administrator must log into the target FlashArray, navigate to Storage - > Protection Groups , and look at the Transfers section within the Protection Group Snapshots panel. This view explicitly details the time the replicated snapshot was created on the source, the time the transfer started, and the current progress of the snapshot being received. If a transfer is currently in-progress, the " Completed " column will remain blank until the snapshot is fully safely written to the target array.

Here is why the other options are incorrect:

From the replication source (C): While the source orchestrates the creation of the snapshot and initiates the data push, the granular transfer completion status and historical transfer logs of the incoming snapshots are tracked on the target ' s Protection Group interface.

From the either the replication source or target (B): Because the specific " Transfers " tracking panel for asynchronous protection group snapshots is located on the receiving end (target), monitoring the granular completion status cannot be done symmetrically from either side in the UI.

In Pure1, the ability to simulate snapshot policies—particularly when assessing the capacity requirements and impact of enabling SafeMode—heavily relies on historical telemetry data. Pure1 uses the data from existing snapshots on the FlashArray to calculate the environment ' s daily data change rate, as well as the deduplication and compression ratios specific to those workloads.

By analyzing the footprint of existing snapshots, Pure1 ' s analytics engine can accurately project the future storage capacity required if you were to change your snapshot frequency or extend the retention period (for example, locking them down for 7 to 30 days under a SafeMode policy). If a FlashArray does not have any existing snapshots, Pure1 lacks the foundational baseline metrics needed to simulate and forecast the capacity impact of a proposed snapshot policy.