Important Pure Storage Portworx-Enterprise-Professional PEP Exam Questions

Answer: C

Explanation:

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.

Answer: A

Explanation:

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.

Answer: A

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

Using encrypted Persistent Volume Claims (PVCs) with Portworx requires that an administrator first configure a secret provider responsible for managing the encryption keys. The secret provider could be an external Key Management System (KMS) such as AWS KMS, Google Cloud KMS, Hashicorp Vault, or Kubernetes Secrets. This step is critical because encryption keys are essential to securely encrypt and decrypt data on volumes. Although enabling encryption in the StorageClass via parameters like secure: enabled is necessary to activate encryption on volumes, it is insufficient without a properly configured secret provider to manage the keys. The secret provider ensures keys are securely stored, rotated, and accessed, fulfilling compliance and security requirements. Portworx documentation stresses this as a foundational step to enable encrypted PVCs, highlighting that without a configured secret provider, encrypted volumes cannot be provisioned or used effectivelyPure Storage Portworx Encryption Docssource.

Answer: B

Explanation:

Comprehensive and Detailed Explanation From Exact Extract:

When troubleshooting a Portworx node that appears down, the first step is to verify the overall Kubernetes cluster health, particularly the node's readiness. Running kubectl get node -o wide provides detailed information about all cluster nodes, including their status, roles, and network details. Ensuring the affected node is marked ''Ready'' or identifying any abnormal conditions helps isolate whether the problem is at the Kubernetes level or specific to Portworx. If the node is not Ready, issues may lie with Kubernetes components or node-level hardware/network problems. After confirming node status, further investigation using pxctl status or examining kubelet logs with journalctl can pinpoint Portworx-specific or system-level failures. Portworx operational best practices recommend starting with Kubernetes node health checks before delving into Portworx or system logs to effectively triage issuesPure Storage Portworx Troubleshooting Guidesource.

Answer: A

Explanation:

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.