Pure Storage Pure Certified Portworx Enterprise Professional Exam Portworx-Enterprise-Professional PEP Exam Questions

Page: 1 / 14
Total 75 questions
Question 1

What command should be used to add a new drive to an existing storage cluster?



Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Adding a new drive to an existing Portworx storage cluster involves bringing the physical device online for Portworx management. The correct command for this is pxctl service drive add -drive /dev/dm-1 -operation start. This command instructs Portworx to recognize and incorporate the new drive specified by the device path (e.g., /dev/dm-1) into its storage pool. After this operation, Portworx can use the drive for provisioning volumes or expanding capacity. The -operation start flag signals Portworx to initialize and prepare the drive for use. This method is part of Portworx's dynamic storage management capabilities, allowing flexible scaling of storage resources without downtime. Official CLI documentation outlines this command as the supported approach to adding drives to running clusters safely and efficientlyPure Storage Portworx CLI Guidesource.


Question 2

What option can a Portworx administrator use to perform snapshots of Repl 2 or 3 volumes when there is limited space on the cluster and no Object Store is configured?



Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Skinny Snapshots are a space-efficient snapshot technique used by Portworx for replicated volumes (Repl 2 or 3) when storage capacity is limited and no external Object Store is configured. Unlike full snapshots that duplicate data blocks, skinny snapshots capture only the differences (deltas) since the last snapshot, minimizing space consumption. This method allows administrators to take frequent snapshots without significantly impacting storage availability. Skinny Snapshots are particularly useful for on-premises environments or clusters without access to cloud object storage, balancing snapshot granularity with resource constraints. Official Portworx snapshot documentation explains how skinny snapshots work internally, improving backup and recovery capabilities under tight storage conditions without requiring cloud integrationPure Storage Portworx Snapshot Guidesource.


Question 3

What are the three severity levels for Portworx alerts?



Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Portworx classifies alerts into three main severity levels to help administrators prioritize response actions. These levels are INFO, WARNING, and CRITICAL. INFO alerts provide informational messages about non-critical events, such as configuration changes or normal operational milestones. WARNING alerts indicate potential issues that could impact performance or availability if left unaddressed, such as increased latency or approaching capacity limits. CRITICAL alerts signal severe problems requiring immediate attention, such as node failures or data corruption risks. This severity categorization supports effective alert management and escalation policies, allowing operational teams to focus on high-impact issues first. The Portworx observability and alerting guide explains these levels in detail and recommends integrating alerts with external monitoring systems for centralized managementPure Storage Portworx Alerting Guidesource.


Question 4

Which command should an administrator run to initiate the license expansion for a blue-green upgrade in a Portworx cluster?



Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

During blue-green upgrades or license expansions in Portworx clusters, administrators use the command pxctl license expand --start to initiate the license expansion process. This command signals Portworx to begin applying the new license, enabling additional nodes or features as permitted. The process is carefully managed to avoid disruption during the upgrade and ensure that new license entitlements are recognized. The Portworx upgrade and licensing documentation specify this command as the official method for license expansion, ensuring compliance and seamless cluster scaling during complex upgrade workflowsPure Storage Portworx License Management Guidesource.


Question 5

If a Portworx node is down and the Kubernetes cluster is healthy, which command should be used to check Portworx alerts on a healthy node?



Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

To check Portworx-specific alerts on a healthy node, administrators use the command pxctl alerts show. This command displays current alerts raised by Portworx, including warnings and critical notifications about storage, nodes, and cluster health. Even if one node is down, alerts from the healthy nodes can provide insights into cluster-wide issues or the status of the affected node. While journalctl displays system and service logs and kubectl describe node shows Kubernetes node info, neither provides aggregated Portworx alert data. The Portworx observability documentation recommends using pxctl alerts show for focused monitoring and alert management, enabling administrators to respond effectively to operational events within the Portworx clusterPure Storage Portworx Monitoring Guidesource.


Question 6

An administrator wants to check the size, availability, and usage of all pools in the cluster.

Which command should the administrator use?



Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

To view detailed information about storage pools in a Portworx cluster---including size, availability, usage, and health---administrators should use the command pxctl service pool show. This CLI command provides a comprehensive overview of all storage pools configured on cluster nodes, including pool IDs, device names, pool sizes, free space, and status. It helps administrators monitor resource utilization, detect degraded pools, and plan capacity expansions. While kubectl get storagecluster shows the overall cluster CRD status and pxctl cluster provision-status shows provisioning status, neither provides detailed pool-level insights. Portworx's operational documentation recommends pxctl service pool show as the definitive command for monitoring pool resources and ensuring storage health across the clusterPure Storage Portworx CLI Guidesource.


Question 7

Which Portworx CRD object is used to set up essential parameters for a Portworx installation?



Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

The StorageCluster Custom Resource Definition (CRD) is the central object used to configure and manage a Portworx installation on Kubernetes. It contains essential parameters including cluster-wide settings, KVDB configuration, storage pool definitions, security options, and CSI driver configurations. The StorageCluster resource declaratively defines how Portworx should be deployed, upgraded, and operated within the Kubernetes cluster. Administrators edit this object to adjust configurations, enabling features like telemetry, monitoring, and cloud integration. Unlike VolumeSnapshot (which manages snapshots) or ServiceAccount (which controls Kubernetes permissions), StorageCluster governs the overall lifecycle and parameters of the Portworx deployment. Portworx operator documentation identifies StorageCluster as the fundamental CRD for installation and configuration managementPure Storage Portworx Operator Guidesource.


Page:    1 / 14   
Total 75 questions