An administrator is setting up FA File using the FlashArray GUI. The company is an NFS only shop and needs to configure their remote user authentication.Which of the following GUI locations should the administrator use to configure access?
Answer(s): B
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.
An administrator is attempting to add a volume to a volume group but it does not show up in the list of volumes available to move in, even though it does show up in the volumes pane.Why is the volume missing?
Answer(s): A
In the Pure Storage Purity operating environment, a volume can only be a member of one Volume Group at a time.When an administrator navigates to a Volume Group in the GUI and clicks to add members, the system filters the inventory and only displays volumes that are currently "unassigned" (not belonging to any Volume Group). If a volume is already residing inside another Volume Group, Purity intentionally hides it from this available list to prevent conflicting overlapping memberships. To resolve this, the administrator must first navigate to the volume's current Volume Group, remove the volume from that group, and then it will become available to add to the new one.Here is why the other options are incorrect:It is already part of a Protection Group (B): Protection Groups (pgroups) manage snapshot and replication schedules. A volume can absolutely be a standalone member of a Protection Group while simultaneously being added to a Volume Group. Being in a pgroup does not hide it from the vgroup selection list.It is protected by SafeMode (C): SafeMode is a ransomware protection feature that prevents the manual eradication of destroyed volumes and snapshots before their retention timer expires. It does not dictate or restrict logical organizational containers like Volume Groups.
An application engineer reports seeing high latency in their application running in a VMware instance.What is the best method to determine the source of the latency?
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.
A storage administrator is configuring a new volume and wants to provision 500GB. If the administrator accidentally selects PB, what will happen?
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 administratoraccidentally 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.
A customer with an X50R2 array connected to 110V power is due for an upgrade to the latest controller generation.What is required to allow this upgrade to proceed?
Answer(s): C
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.
A FlashArray//XL is used for NVMe-RoCE services. The array has been lightly loaded and has performed as expected. A new workload has been added to the array, which is within the array's performance envelope. The change has resulted in extreme latency and service outages for all workloads utilizing NVMe-RoCE.Which misconfiguration is this a symptom of?
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.
Twelve stretched pods are synchronously replicating between an ActiveCluster (AC) FlashArray pair. A new unstretched pod is created and then is stretched, but the operation fails.What is the most likely cause of the operation not completing successfully?
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 increasesthe maximum pod limit (some newer versions support more, but 12 is the classic threshold often tested in professional certifications).
Which storage protocol is best suited for a Hyper-V cluster in an ethernet-switched environment?
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.
Post your Comments and Discuss Pure Storage FlashArray Storage Professional exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the FlashArray Storage Professional content, but please register or login to continue.