Pure Storage FlashArray-Storage-Professional Exam Dumps

Purity Active/Active Architecture: Pure Storage FlashArrays use an Active/Active controller architecture. Under normal operating conditions, both controllers (CT0 and CT1) are healthy and independently serve I/O through their respective physical Fibre Channel ports.

The Scenario (Controller Failover): The output provided shows that the host initiator is seeing target WWNs associated with both CT0 and CT1, but the 'Target' column indicates they are all being reached via the paths currently managed by one controller or through a specific failover mechanism.

Virtual WWNs and Transparency: In a controller failover or maintenance scenario, Pure Storage utilizes a feature where the WWNs of the 'failed' or 'offline' controller are logically moved to or presented by the 'surviving' controller. This ensures that the host's MPIO (Multi-path I/O) software does not see a permanent 'Path Down' error for those specific WWNs, but rather a transition.

Analyzing the Output: When you see CT1 port WWNs (e.g., 52:4A:93:78:55:2D:E3:10) appearing in the connectivity table in a way that implies they are being routed or presented through the physical infrastructure of CT0, it indicates that the array is in a state where one controller is assuming the identity/connectivity of the other. This is a key troubleshooting indicator that the array is likely undergoing a controller reboot, a Purity upgrade, or has experienced a controller hardware failure.

Why A and B are incorrect: * Option A: Multipathing software on the host handles path failures, but it wouldn't cause the array to report WWNs in this specific 'cross-presented' manner in a connectivity log.

Option B: If there were a total outage on CT1 without this presentation mechanism, the paths would simply show as 'Disconnected' or be missing from the initiator's view entirely.

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.

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.

In Pure Storage Purity OS, the absolute best practice and proper configuration method for sharing a single volume across multiple hosts---such as a VMware ESXi cluster or a Microsoft Windows Server Failover Cluster (WSFC)---is to connect the volume to a Host Group.

When you create a Host Group, you add the individual Host objects (which contain the WWPNs, IQNs, or NQNs) into that group. When a volume is then connected to the Host Group, Purity automatically ensures that the volume is presented to every host in that group using the exact same LUN ID. Consistent LUN IDs across all nodes in a cluster are a strict requirement for clustered file systems like VMFS and Cluster Shared Volumes (CSV) to function correctly and prevent data corruption.

Here is why the other options are incorrect:

Connect the volume to each individual host (C): This is known as creating 'private connections.' If you manually connect a shared volume to multiple hosts individually, Purity might assign a different LUN ID to the volume for each host. Inconsistent LUN IDs will cause clustered operating systems to fail to recognize the disk as a shared resource. Private connections should only be used for boot LUNs or standalone standalone servers.

Connect a volume group to the host (B): In Purity, a 'Volume Group' is a logical container used for applying consistent snapshot policies, replication schedules, or ActiveCluster configurations to a set of related volumes (like a database and its log files). Volume groups are not used for host presentation or access control.

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 administrator accidentally 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.