Aug 05, 2026 Updated FlashArray-Storage-Professional Dumps Questions For Pure Storage Exam
Best Value Available Preparation Guide for FlashArray-Storage-Professional Exam
Pure Storage FlashArray-Storage-Professional Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 40
A new array is directly connected to a host with Direct Attach Copper (DAC) cables. The link does not come up.
Which document can be used to help identify the issue?
- A. The Port Usage and Definitions article
- B. FlashArray Transceiver and Cable Support article
- C. The FlashArray User Guide
Answer: B
Explanation:
When physical links fail to establish-especially when using Direct Attach Copper (DAC) cables or Twinax-the most common culprit is a hardware compatibility mismatch. Pure Storage arrays have specific requirements for optics and cabling to ensure optimal signal integrity and performance.
The FlashArray Transceiver and Cable Support article (available on the Pure Storage Support portal) is the authoritative, verified resource for this scenario. It provides a comprehensive, constantly updated compatibility matrix detailing exactly which vendor DAC cables (e.g., Cisco, Brocade, Arista) and transceivers are officially validated and supported for use with specific FlashArray models and port types. If an unsupported DAC cable is used, the switch or host bus adapter (HBA) on the array might simply refuse to bring the link up.
Here is why the other options are incorrect for this specific issue:
The FlashArray User Guide (A): This guide is excellent for day-to-day administration (volume creation, host grouping, etc.) but is too broad to contain granular, constantly updating hardware compatibility matrices for specific cables.
The Port Usage and Definitions article (C): This document explains the logical and physical purpose of the ports on the back of the controllers (e.g., defining which ports are used for management, replication, or host connectivity), but it does not dictate hardware transceiver or cable interoperability.
NEW QUESTION # 41
RFC2307 enables cross-protocol support for which two protocols?
- A. NFS, S3
- B. S3, SMB
- C. NFS, SMB
Answer: C
Explanation:
Understanding RFC2307: RFC2307 is an extension to the LDAP (Lightweight Directory Access Protocol) schema that allows for the storage of Unix-style information (POSIX attributes) within a directory service, most commonly Microsoft Active Directory. These attributes include things like uidNumber (User ID), gidNumber (Group ID), and login shells.
The Cross-Protocol Challenge: In a Unified Storage environment where the same data needs to be accessed by both Windows clients (using the SMB protocol) and Linux/Unix clients (using the NFS protocol), the storage array must be able to map a Windows Security Identifier (SID) to a Unix UID/GID.
How Pure Uses It: When an administrator enables RFC2307 support in Purity//FA File Services, the FlashArray can query Active Directory to retrieve these POSIX attributes. This creates a 1:1 mapping between the Windows user and the Unix identity.
The Benefit: This mapping ensures that a user can create a file via SMB and another user (or the same user on a different system) can access or modify that same file via NFS while maintaining consistent permission enforcement and ownership records. Without this (or a similar mapping service like NIS or local files), cross-protocol access often results in permission "Mapping" errors or files being owned by "nobody."
NEW QUESTION # 42
What are the two types of FA File quota limits?
- A. Limited and Unlimited
- B. Enforced and Unenforced
- C. File and Block
Answer: B
Explanation:
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.
NEW QUESTION # 43
What FA File user authentication statement is correct?
- A. FA File can use either Microsoft Active Directory (AD) or OpenLDAP for authentication.
- B. FA File can use both Microsoft Active Directory (AD) and SSO for authentication.
- C. FA File can use either LDAP or SAML for authentication.
Answer: A
Explanation:
Supported Directory Services: Pure Storage FlashArray File Services (FA File) is designed to integrate seamlessly into existing enterprise identity infrastructures. To manage file permissions (SMB ACLs and NFS POSIX/NFSv4 permissions), Purity supports joining the array to a directory service.
Active Directory (AD): This is the most common integration for FA File, specifically for SMB environments. Purity allows the array to join an AD Domain, creating a computer account and enabling the resolution of SIDs to usernames.
OpenLDAP: For Linux/Unix-heavy environments using NFS, Purity supports OpenLDAP. This allows the array to look up UID/GID information and group memberships to enforce security across the file system.
Authentication vs. Management: It is important to distinguish between Data Access (FA File) and Management Access (GUI/CLI login).
FA File (Data Access): Uses AD and OpenLDAP to authorize users accessing shares/exports.
Management (GUI/CLI): Uses SAML (Option C) or LDAP for Single Sign-On (SSO) (Option B) to allow administrators to log into the array.
The "Either/Or" Logic: While a FlashArray can be configured with multiple directory services, for a specific File System/Export mapping, the system relies on the primary identity provider configured-either Microsoft AD or an LDAP-compliant service like OpenLDAP-to validate the users' identity.
NEW QUESTION # 44
An On-Premises ActiveCluster (AC) Mediator is installed on an ESXi server. The mediator was previously online but when the administrator checked the status of the ActiveCluster (AC) pods the mediator status was listed as "unreachable" for both FlashArrays in the ActiveCluster (AC) pair.
What is a possible cause of the mediator being unreachable from both FlashArrays?
- A. Fibre Channel (FC) zoning or network access has not been created properly for the host.
- B. The mediator does not reside within a Pure datastore.
- C. Outbound TCP port 80 is not allowed from the FlashArrays.
Answer: C
Explanation:
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.
NEW QUESTION # 45
What is unified storage for Pure?
- A. FlashArray runs both NFS and SMB protocols.
- B. FlashArray runs both iSCSI and Fibre Channel (FC) protocols.
- C. FlashArray runs both Block and File level protocols.
Answer: C
Explanation:
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.
NEW QUESTION # 46
How is SAN Time measured?
- A. Average time, measured in milliseconds, that an IO request spends waiting to synchronize to the peer array.
- B. Average time, measured in milliseconds, required to transfer data between the initiator and the array.
- C. Average time, measured in milliseconds, that an I/O request spends in the array waiting to be served.
Answer: B
Explanation:
Understanding Total Latency: In a FlashArray environment, total latency as seen by the host application is the sum of several components. Pure Storage breaks this down into Array Time and SAN Time to help administrators pinpoint where performance bottlenecks exist.
SAN Time Definition: SAN Time represents the latency introduced by the network infrastructure between the host (initiator) and the FlashArray (target). This includes the time spent traveling across Fibre Channel or Ethernet switches, cables, and host bus adapters (HBAs). It is calculated by taking the total round-trip time measured by the host and subtracting the time the FlashArray spent processing the I/O.
Metric Breakdown: * Array Time: The time the FlashArray takes to process the I/O once it hits the front-end ports (Option C describes internal array time).
SAN Time: The transit time for the request to reach the array and the response to return to the host (Option A).
Wait Time: In ActiveCluster environments, there is also "Mirror Latency," which is the time spent synchronizing data to a peer array (Option B).
Troubleshooting Value: If a user reports high latency but the FlashArray GUI shows very low Array Time, the administrator can look at the SAN Time metric. A high SAN Time indicates an issue with the fabric, such as a failing SFP, a congested switch port, or oversubscribed ISLs (Inter-Switch Links).
NEW QUESTION # 47
If an NFS client can mount the FA File export shares with the IP address, but not the fully qualified domain name, what is most likely causing the issue?
- A. Issue with the Active Directory (AD) controller
- B. Issue with the DNS
- C. Issue with the OpenLDAP
Answer: B
Explanation:
When an NFS client successfully mounts an export using the target's IP address, it proves that the fundamental network connectivity (routing, firewalls) and the storage protocol layer (NFS export policies, host access permissions) are functioning correctly.
However, if the exact same mount attempt fails when using the Fully Qualified Domain Name (FQDN) of the FlashArray file service, the issue lies entirely with name resolution. The Domain Name System (DNS) is responsible for translating human-readable FQDNs into the IP addresses required for network communication. If the client cannot reach the DNS server, or if the DNS server lacks the correct A or AAAA records for the FlashArray's file Virtual IP (VIP) addresses, the client won't be able to resolve the name to the IP, causing the mount command to fail.
Here is why the other options are incorrect:
Issue with the Active Directory (AD) controller (A): Active Directory is primarily used for directory services, user authentication, and authorization (such as mapping permissions for SMB or NFSv4). While AD environments usually include DNS, an "AD controller issue" in the context of storage protocols usually points to permission denials, not host name resolution failures. Furthermore, since the mount works via IP, basic access is already validated.
Issue with the OpenLDAP (C): Similar to AD, OpenLDAP provides directory services for user mappings (UID/GID) and authentication. It does not perform FQDN-to-IP resolution.
NEW QUESTION # 48
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?
- A. Analyze performance charts in vSphere for CPU, Memory, Network, and Storage Path for the user's data path.
- B. Analyze load metrics in Pure1 for each volume in the user's data path.
- C. Analyze performance in the VM Topology in Pure1 for each component in the user's data path
Answer: C
Explanation:
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.
NEW QUESTION # 49
What is the purpose of a Protocol Endpoint volume?
- A. It is required to set Host Protocol.
- B. It allows for volumes of the same name within host groups.
- C. It serves as a mount point for vVols.
Answer: C
Explanation:
In a VMware vSphere environment utilizing Virtual Volumes (vVols), a Protocol Endpoint (PE) acts as a crucial logical proxy or I/O access point between the ESXi hosts and the storage array.
Unlike traditional VMFS datastores where the host mounts a massive LUN and places all VM files inside it, vVols map individual virtual machine disks directly to native volumes on the FlashArray. Because a single ESXi host could potentially need to communicate with thousands of individual vVol volumes, it would be extremely inefficient to map every single one directly to the host. Instead, the ESXi host mounts the Protocol Endpoint, and the storage array uses this PE to dynamically route the I/O to the correct underlying vVol. On a Pure Storage FlashArray, creating and connecting a PE volume to your ESXi host groups is a mandatory prerequisite for setting up a vVol datastore.
Here is why the other options are incorrect:
It allows for volumes of the same name within host groups (A): Purity OS requires all volume names across the entire FlashArray to be completely unique, regardless of which host group they are connected to or whether a Protocol Endpoint is in use.
It is required to set Host Protocol (C): The host communication protocol (such as iSCSI, Fibre Channel, or NVMe-oF) is determined by the physical host bus adapters (HBAs), network interface cards (NICs), and the configuration of the Host object in Purity, not by the creation of a volume type like a PE.
NEW QUESTION # 50
During testing of an NFS share, the administrator notes that they are able to mount the share as root but are not able to access files as root.
Where is the incorrect setting causing the issue located?
- A. Export Policy
- B. Managed Directory
- C. File System
Answer: A
Explanation:
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.
NEW QUESTION # 51
Which protection group cannot be ratcheted for SafeMode?
- A. Protection groups with hosts or hostgroups
- B. A default protection group
- C. A protection group without a local snapshot schedule
Answer: C
NEW QUESTION # 52
A storage administrator needs to determine what actions were taken on the array by the previous shift and is only able to access the FlashArray via CLI.
Which command provides that information?
- A. pureaudit list -- puremessage
- B. puremessage list
- C. pureaudit list
Answer: C
Explanation:
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.
NEW QUESTION # 53
Which protection group cannot be ratcheted for SafeMode?
- A. Protection groups with hosts or hostgroups
- B. A default protection group
- C. A protection group without a local snapshot schedule
Answer: C
Explanation:
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.
NEW QUESTION # 54
How should an administrator configure initiator-to-target connections for zones with multiple initiators?
- A. Multiple initiator to multiple target zone sets
- B. Single target to multiple initiator zone sets
- C. Single initiator to multiple target zone sets
Answer: C
Explanation:
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.
NEW QUESTION # 55
What is the recommended Maximum Transmission Unit (MTU) size for the replication ports on a FlashArray?
- A. 0
- B. 1
- C. 2
Answer: C
Explanation:
Pure Storage strongly recommends an MTU size of 9000 (Jumbo Frames) for replication networks-such as those used for Asynchronous Replication, ActiveCluster, and ActiveDR-as well as for iSCSI and NVMe/TCP data networks.
A 9000-byte MTU significantly reduces protocol overhead and CPU processing load on the storage controllers by allowing a much larger payload of data to be transmitted inside a single network packet. During heavy replication, this drastically increases throughput and maximizes bandwidth efficiency.
Here is why the other options are incorrect:
1500 (B): While 1500 bytes is the standard default MTU for Ethernet and is exactly what Pure Storage recommends for the management ports (vir0), it is not the recommended optimization for high-throughput replication traffic. (Note: If your network cannot support 9000 end-to-end, 1500 must be used to prevent packet fragmentation, but 9000 remains the best-practice recommendation).
4200 (A): This is an arbitrary number and is not a standard network MTU size used in Pure Storage environments.
NEW QUESTION # 56
What does an asynchronous blackout window prevent?
- A. In progress transfers that started before the blackout window.
- B. New replication transfers from starting during the blackout window.
- C. New replication transfers that started before the blackout window.
Answer: B
Explanation:
Definition of a Blackout Window: In Purity//FA, a Blackout Window is a scheduled period during which asynchronous replication is suspended. This is typically used by administrators to preserve WAN bandwidth during peak business hours or to prevent replication traffic from competing with high-priority local workloads (like a massive database batch job).
The "In-Progress" Rule: One of the most important characteristics of a blackout window is that it is non-disruptive to active transfers. If a replication job started at 7:55 AM and the blackout window begins at 8:00 AM, Purity will allow that specific transfer to continue until it finishes.
The Prevention Mechanism: Once the clock hits the start of the blackout window, the replication scheduler is effectively "paused." No new snapshots will be queued for transfer, and no new replication sessions will be initiated until the window expires.
Why Option A is incorrect: Purity does not kill active transfers. Abruptly stopping a transfer would waste the bandwidth already consumed and require the entire delta-set to be re-calculated or re-sent later.
Why Option B is incorrect: The phrasing is logically inconsistent; you cannot prevent something that "started before" the window from being "new" during the window.
Best Practice: When configuring blackout windows, ensure that the "clear" time (the time between windows) is long enough to allow the array to catch up on the snapshots that were queued during the blackout, otherwise, you risk triggering Alert 51 (Replication Delayed).
NEW QUESTION # 57
Which command provides the negotiated port speed of an ethernet port?
- A. pureport list
- B. purehw list -- all -- type eth
- C. purenetwork eth list -- all
Answer: B
Explanation:
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.
NEW QUESTION # 58
A storage administrator has presented VMFS datastores from a FlashArray with 10TB of raw capacity.
Why would the administrator see system space when logging in to the FlashArray GUI?
- A. Virtual machines have not yet issued an unmap command.
- B. There is more than 2TB of reclaimable space on the FlashArray.
- C. More than 2TB of volume snapshots were destroyed.
Answer: B
Explanation:
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.
NEW QUESTION # 59
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?
- A. Settings > Access > Create Active Directory Account
- B. Settings > Access > Directory Services
- C. Settings > Access > File System
Answer: B
Explanation:
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.
NEW QUESTION # 60
What happens when you demote the original source pod?
- A. Replication is reversed.
- B. It saves a temporary copy of the source pod content in the eradication bin.
- C. Replication is paused.
Answer: A
Explanation:
ActiveCluster and Pod Roles: In a Pure Storage ActiveCluster or ActiveDR environment, a Pod is a management container for volumes. To move workloads or perform a planned failover between two arrays, you use the Promote and Demote commands.
The Reversal Process: When you have two pods in a replication relationship (Source and Target), data flows from the Promoted (Active/Source) pod to the Demoted (Passive/Target) pod.
When you Demote the current source, it transitions from a "read-write" state to a "read-only" (passive) state.
If the other pod in the pair is then Promoted, Purity automatically intelligently reverses the direction of replication. The array that was previously receiving data now begins sending incremental updates back to the original source.
Continuous Protection: This design ensures that you don't have to manually tear down and recreate replication schedules every time you switch production sites. The system tracks the metadata changes and ensures that only the delta (changed blocks) are sent in the new direction.
Why Option C is incorrect: If replication were simply paused, the two sites would quickly drift out of sync, making it impossible to fail back without a full baseline resync.
Why Option A is incorrect: Demoting a pod does not delete any data; it simply changes the access characteristics and replication role. The data remains fully intact on the storage media.
NEW QUESTION # 61
A storage administrator is tasked with providing real-time data and alerts to the Network Operations Center (NOC) dashboard.
What source should the information come from to provide real-time data?
- A. Pure Performance Monitoring
- B. Pure1
- C. FlashArray
Answer: C
Explanation:
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.
NEW QUESTION # 62
......
Full FlashArray-Storage-Professional Practice Test and 77 Unique Questions, Get it Now!: https://www.prepawayete.com/Pure-Storage/FlashArray-Storage-Professional-practice-exam-dumps.html