Pure Storage Pure Certified FlashArray Storage Professional FlashArray-Storage-Professional Exam Questions

Answer : B

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.

Answer : B

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.

Answer : C

In the Pure Storage FlashArray GUI, granular performance metrics (Latency, IOPS, Bandwidth) are located under the Analysis > Performance tabs. When you navigate to the Volumes sub-tab and select a specific volume, Purity displays a unified line graph tracking the performance of that volume over time.

By default, the Latency graph simultaneously plots Read, Write, and Mirrored Write (for volumes participating in an ActiveCluster or synchronous replication pod) latencies. Because these lines can overlap or compress the Y-axis (especially if one metric spikes), isolating a specific metric requires interacting with the graph's legend.

To view the exact, un-obscured latency for standard write requests to that volume, the administrator should click on 'Read' and 'Mirrored Write' in the chart's legend. This deselects those metrics, effectively hiding their lines from the graph and automatically rescaling the view to exclusively display the host write latency.

Here is why the other options are incorrect:

Health > Network (A): The Health tab is used to check the hardware status of the physical controller ports, including link state and errors. While you might see port-level throughput or queue depth here, it does not provide volume-specific application latency.

Storage > Volumes > Details (B): The Storage tab is primarily used for provisioning and configuration management. Clicking on a volume here will show its size, data reduction ratio, snapshot policies, and connected hosts, but it does not provide detailed interactive performance graphs.

Answer : A

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.

Answer : 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.

Answer : A

Ratcheted Protection Groups: A 'ratcheted' protection group is a security feature used to enforce data retention and prevent the accidental or malicious removal of volumes from a protection policy. Once a protection group is ratcheted, the configuration is essentially 'locked.'

The 'Ratchet' Mechanism: When a protection group is ratcheted, Purity prevents any modifications that would decrease the level of protection. This includes preventing the removal of volumes from the group, as removing a volume would stop its scheduled snapshots and replication, thus violating the established security posture.

Security and Compliance: Because ratcheting is often used for compliance (such as SEC Rule 17a-4 or HIPAA) or as a defense against ransomware, it is designed to be difficult to reverse. Neither the standard GUI (Option C) nor the standard CLI (Option B) provides a self-service 'unlock' button for a ratcheted group.

The Recovery Path: To remove a volume or change the settings of a ratcheted protection group, a FlashArray administrator must Contact Pure Storage Support. Support engineers have specific, high-level challenge-response procedures to verify the administrator's identity and intent before performing the back-end operations required to 'un-ratchet' or modify the group.

Answer : A

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