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

Answer : A

Understanding Alert 51: On a Pure Storage FlashArray, Alert 51 signifies that a Protection Group's replication is lagging behind its scheduled completion time. This does not necessarily mean the connection is 'down,' but rather that the volume of data being sent is exceeding the available throughput or is being queued behind other tasks.

The Triage Process:

Open Alerts: You must check for related alerts (like Alert 20 for 'Replication Connection Down') to determine if the delay is caused by a total link failure or just congestion.

Replication Jobs in Progress: Because FlashArray uses a specialized engine to manage replication, having multiple large snapshots from different Protection Groups replicating simultaneously can saturate the 'replication pipe.' Checking active jobs helps determine if there is a scheduling 'traffic jam.'

Replication Bandwidth: Comparing the current outgoing replication throughput against the historical average or the physical limit of the replication ports helps identify if the delay is due to a sudden increase in Data Change Rate (churn) or a reduction in network performance.

Why Option B is incorrect: If a Protection Group were disabled, replication wouldn't be 'delayed'---it would be stopped, which triggers a different alert state. Cabling issues usually result in 'Connection Down' alerts rather than just 'Delayed' alerts.

Why Option C is incorrect: Disconnecting replication is a destructive troubleshooting step that will only increase the lag and RPO. You should always analyze the existing data flow before breaking the connection.

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

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.

Answer : A

In policy-driven data protection and disaster recovery architectures like Pure Protect //DRaaS, a 'Business Policy' dictates the critical Service Level Agreements (SLAs) for your environment, such as your Recovery Point Objective (RPO), replication frequency, and retention schedules. These policies are then assigned to 'Application Groups,' which act as logical containers for the specific virtual machines being protected and replicated to AWS.

As a fundamental safety mechanism built into the platform to prevent accidental exposure and SLA breaches, the system places a hard dependency lock on actively used policies. An administrator cannot delete a Business Policy if there are still Application Groups actively relying on it for their DR scheduling. To successfully delete the policy, the administrator must first modify all associated Application Groups and assign them to a different Business Policy, or completely remove the protection from those groups.

Here is why the other options are incorrect:

The administrator also needs DRaaS Cloud Admin access (C): The scenario explicitly states the user already has 'DRaaS Global Admin access.' In the Pure Protect //DRaaS Role-Based Access Control (RBAC) model, Global Admin is the highest tier of privilege and has full rights to manage and delete policies. A lack of permissions is not the issue here.

The Business Policy is marked as the Primary Policy (B): While a policy might be a default or primary template, the actual hard restriction that prevents deletion in the software is active resource assignment (the Application Groups), not just a 'Primary' label.

Answer : C

According to the official Pure Storage FlashArray Asynchronous Replication Configuration and Best Practices Guide, the proper and immediate method to halt an active, in-progress asynchronous replication transfer is by disallowing the protection group at the target.

When you navigate to the target FlashArray and disallow the specific Protection Group, Purity immediately breaks the replication authorization for that group. If there is an in-progress snapshot transfer occurring at that exact moment, the transfer is immediately stopped, and the partially transferred snapshot data is discarded on the target side.

Here is why the other options are incorrect:

Disabling the replication schedule (B): Toggling the replication schedule to 'Disabled' only prevents future scheduled snapshots from being created and sent. It does not kill or interrupt a replication transfer that is already currently in progress.

Removing the volume member from a protection group (A): Modifying the members of a protection group updates the configuration for the next snapshot cycle. It does not actively abort the transmission of the current point-in-time snapshot that the array is already busy sending over the WAN.

Answer : B

Logical vs. Physical Reclamation: When an administrator 'Eradicates' a volume, the FlashArray immediately removes the logical reference to that data. However, the physical blocks are not 'wiped' instantly. Instead, those blocks are marked as 'eligible for reclamation' by Purity's background Garbage Collection (GC) process.

Workload Prioritization: Purity is designed to prioritize Host I/O (production performance) over background system tasks. If the array is under an extremely high workload (high Load Meter percentage), Purity will automatically throttle the Garbage Collection process to ensure the application latency remains as low as possible.

The 'Reclamation Lag': If the incoming write rate from the hosts (new data being written) exceeds the speed at which the throttled GC process can reclaim space from the eradicated volume, the 'Used Space' metric will continue to trend upward. This is a common scenario when arrays are pushed to their performance or capacity limits simultaneously.

Why Option A is incorrect: The 24-hour safeguard applies to Destroyed volumes (the 'Pending Eradication' bucket). Once an administrator manually clicks Eradicate, that safeguard is bypassed, and the space should logically be freed. If the space is still not reflecting as 'Free,' it is a back-end processing delay, not a timer delay.

Why Option C is incorrect: In the Purity Operating Environment, the array does not require the host to 'unmount' or 'disconnect' before it can reclaim space. Once the volume is destroyed and eradicated on the array side, those blocks are gone from the array's perspective, regardless of the host's state (though the host will likely experience I/O errors).

Answer : B

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.