FlashArray Storage Professional Dumps PDF Free Download

QUESTION: 9

A FlashArray is set up with LDAP authentication. A user is a member of the groups associated with both Array Admin and Storage Admin.

What experience is expected for the user?

User will have Array Admin permissions.
User will not be able to login.
User will have Storage Admin permissions.

Answer(s): A

Explanation:

Similar to the previous question regarding directory services, Pure Storage Purity OS handles Role-Based Access Control (RBAC) overlaps by granting the most permissive role available to the user.

When configuring LDAP or Active Directory authentication on a FlashArray, administrators map directory groups to specific FlashArray roles (Array Admin, Storage Admin, Ops Admin, Read Only). If a user happens to be a member of multiple LDAP groups that are mapped to different roles on the array, Purity evaluates all mapped roles and automatically assigns the user the highest level of privilege during their session.

Since "Array Admin" has full administrative rights over the entire array (including hardware management, directory services configuration, and firmware upgrades) and sits higher in the hierarchy

than "Storage Admin" (which is restricted to provisioning and managing storage objects like volumes and hosts), the system will seamlessly grant the user Array Admin permissions.

Here is why the other options are incorrect:

User will not be able to login (B): Purity is designed to handle this exact scenario smoothly. It resolves the conflict by defaulting to the higher privilege, rather than throwing an error or denying access.

User will have Storage Admin permissions (C): The system does not default to the lowest privilege or restrict access when a higher-level group membership is present and valid.

Reveal Solution Next Question

QUESTION: 10

How are in-progress asynchronous snapshot transfers monitored from the UI?

From the replication target
From the either the replication source or target
From the replication source

Answer(s): A

Explanation:

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.

Reveal Solution Next Question

QUESTION: 11

A FlashArray//C R4 has ports Eth0 and Eth1 connected to a switch using 100Gb/s Direct Attach Copper (DAC) cables. The administrator is unable to configure these ports for iSCSI services.

Why is this occurring?

The ports are designated for Management connectivity.
The DAC cables are not compatible with the array's ports.
The ports are designated for DirectFlash Shelf connectivity.

Answer(s): C

Explanation:

On the Pure Storage FlashArray//C R4 (as well as the //XL and //E series architectures), the onboard 100Gb/s Ethernet LOM (LAN on Motherboard) ports--specifically eth0 and eth1--are purpose-built and strictly reserved for DirectFlash Shelf (DFS) connectivity.

Pure Storage uses these dedicated 100GbE ports to run NVMe over RoCE (RDMA over Converged Ethernet), effectively extending the array's internal PCIe backplane to additional backend storage shelves. Because these ports are hardcoded exclusively for back-end shelf expansion, the Purity operating environment fundamentally restricts them from being assigned IP addresses for front-end host I/O services. Therefore, an administrator will be completely unable to configure eth0 or eth1 for iSCSI, NVMe/TCP, or Replication. Front-end iSCSI services must instead be configured on the dedicated Host I/O PCIe cards (which typically appear as eth2, eth3, etc., depending on the slot configuration).

Here is why the other options are incorrect:

The ports are designated for Management connectivity (A): On modern FlashArrays, dedicated management ports are typically out-of-band 1GbE/10GbE RJ45 ports (often designated as vir0 or specific management eth ports on older hardware), not the ultra-high-speed 100Gb/s QSFP28 ports.

The DAC cables are not compatible with the array's ports (B): While incompatible cables can prevent a link from coming up physically, the specific reason the administrator cannot configure the ports for iSCSI in the Purity software is due to the port's hardcoded role (DFS), not the physical cable type.

Reveal Solution Next Question

QUESTION: 12

An administrator is running commands to verify NVME/TCP connectivity from the hosts to the FlashArray. They use the command ping -M do -s 8972 <ip_addr> from the initiator and it fails.

What should the administrator do to resolve the issue?

Engage support to enable NVME/ TCP services.
Check the MTU of 9000 is set on each hop to the FA.
Run the command from the target.

Answer(s): B

Explanation:

When configuring NVMe/TCP (or iSCSI) for optimal performance on a Pure Storage FlashArray, configuring Jumbo Frames (an MTU of 9000) end-to-end is a standard best practice.

The command ping -M do -s 8972 <ip_addr> is specifically used to verify Jumbo Frame configuration across the network.

The -M do flag sets the "Do Not Fragment" (DF) bit, meaning the network is not allowed to break the packet into smaller pieces.

The -s 8972 flag sets the ICMP data payload to 8972 bytes. When you add the standard 8-byte ICMP header and the 20-byte IP header, the total packet size equals exactly 9000 bytes.

If this ping command fails, it indicates that somewhere along the network path between the host (initiator) and the FlashArray (target), a switch port, router, or network interface is not configured to support an MTU of 9000. The packet is being dropped because it is too large and cannot be fragmented. The administrator must verify the MTU settings on every network hop (switches, routers, and host NICs) to resolve the issue.

Here is why the other options are incorrect:

Engage support to enable NVME/ TCP services (A): The failure of a Jumbo Frame ping test is a Layer 2/Layer 3 network configuration issue, not an indicator that the NVMe/TCP storage protocol service is disabled on the array.

Run the command from the target (C): While pinging from the FlashArray back to the host is a valid

secondary troubleshooting step, it will likely also fail if the network path doesn't support Jumbo Frames. The actual resolution is to fix the MTU on the network hops.

Reveal Solution Next Question

QUESTION: 13

Pure Protect //DRaaS is configured with a Business Policy to back up data to AWS. An administrator, with DRaaS Global Admin access, is trying to delete the policy but is unable to do so.

What is restricting the administrator from deleting the policy?

Application groups are currently protected under that policy.
The Business Policy is marked as the Primary Policy.
The administrator also needs DRaaS Cloud Admin access.

Answer(s): A

Explanation:

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.

Reveal Solution Next Question

QUESTION: 14

What should an administrator configure when setting up device-level access control in an NVMe/TCP network?

VLANs
NQN
LACP

Answer(s): B

Explanation:

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.

Reveal Solution Next Question

QUESTION: 15

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?

Pure Performance Monitoring
Pure1
FlashArray

Answer(s): 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.

Reveal Solution Next Question

QUESTION: 16

How would a FlashArray administrator view external latency for write requests for a specific volume?

Health > Network > Select the appropriate protocol > Select the appropriate port
Storage > Volumes > Select the appropriate volume > Details
Analysis > Performance > Volumes > Select the appropriate volume > Deselect "Read" and "Mirrored Write"

Answer(s): C

Explanation:

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.

Reveal Solution Next Question

Pure Storage Pure Certified FlashArray Storage Professional FlashArray Storage Professional Dumps in PDF

Free Pure Storage FlashArray Storage Professional Real Questions (page: 8)

QUESTION: 9

Explanation:

QUESTION: 10

Explanation:

QUESTION: 11

Explanation:

QUESTION: 12

Explanation:

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

QUESTION: 16

Explanation: