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

Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

During Portworx upgrades via the Kubernetes Operator, if the deployment uses a px-versions ConfigMap to manage available Portworx versions, the administrator must update the version manifest within this ConfigMap to include the new version. This update informs the Operator of the target version for upgrades and ensures that the correct container images are pulled and deployed. Simply creating a new namespace or deleting the ConfigMap is insufficient and can cause upgrade failures or inconsistent version deployments. The Portworx Operator upgrade documentation emphasizes updating the px-versions ConfigMap manifest as a necessary step in orchestrated upgrades, enabling controlled, predictable version management within Kubernetes clustersPure Storage Portworx Upgrade Guidesource.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

To verify a Portworx upgrade on Kubernetes, administrators use the pxctl get storagenodes command. This Portworx CLI command lists all storage nodes with detailed information including version, status, and health. By inspecting the version column, administrators can confirm whether all nodes have been successfully upgraded to the desired Portworx release. This command specifically queries Portworx daemons for accurate cluster version details, unlike kubectl get nodes which shows Kubernetes node info but not Portworx versioning. Portworx upgrade best practices stress using pxctl commands for detailed verification after an upgrade to ensure consistent cluster software versions and successful upgrade completionPure Storage Portworx Upgrade Guidesource.

Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

To ensure Portworx volumes for an ElasticSearch application are created only on specific Kubernetes nodes, the Volume Placement Strategy feature is used. This feature allows administrators to define node affinity or anti-affinity rules that restrict volume provisioning to a subset of nodes. By tagging the six nodes with appropriate labels and configuring the StorageClass or volume parameters to respect these labels, Portworx guarantees that volumes will only be provisioned on those nodes. This targeted volume placement is critical for performance optimization, data locality, and compliance with infrastructure constraints. Autopilot automates scaling and Stork manages storage-aware scheduling but does not directly control volume node placement. The Portworx deployment documentation highlights Volume Placement Strategy as the tool for precise volume-to-node mapping in Kubernetes clustersPure Storage Portworx Deployment Guidesource.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

When integrating Portworx with an S3 Object Store secured by a custom or third-party certificate that is not signed by a public Certificate Authority (CA), administrators must manually provide the relevant CA certificate to Portworx. This involves creating a Kubernetes secret that contains the custom CA certificate and referencing this secret in the StorageCluster manifest through environment variables. This allows Portworx components to trust the certificate during TLS handshake with the S3 endpoint, avoiding connection failures due to untrusted certificates. Without this step, Portworx cannot securely communicate with the object store. The Portworx security and installation documentation highlights this practice as essential for secure Object Store integration in private or regulated environments where internal or custom PKIs are usedPure Storage Portworx Security Guidesource.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Once two Portworx clusters are paired, for example in disaster recovery setups, data migration between them can be initiated. The command pxctl cloudmigrate start triggers this migration process. It synchronizes volumes, ensuring that data is copied securely and consistently from the source cluster to the destination. This migration is transparent to applications and supports incremental syncs, which helps reduce downtime. The CLI command also provides operational feedback and logs for administrators to monitor progress. Portworx's documentation on disaster recovery workflows emphasizes this command as essential for starting volume migration post-cluster pairing, streamlining data protection and business continuity strategies across multiple sites or cloud regionsPure Storage Portworx Disaster Recovery Guidesource.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

To migrate data from an existing PVC backed by another storage provider to a new Portworx PVC, the administrator typically creates a temporary pod (often using a lightweight container like busybox) that mounts both the source and destination PVCs. Within this pod, standard Linux file commands such as cp or rsync are used to transfer data between volumes. This approach leverages Kubernetes volume mounting capabilities and avoids downtime by enabling data migration without removing the source volume immediately. Portworx does not provide a direct pxctl import command, nor does it use a DataExport Cluster Resource for PVC data migration. This manual method is widely documented and recommended for stateful data migration tasks involving Kubernetes PVCs across different storage backendsPure Storage Portworx Data Migration Guidesource.

Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

An Autopilot rule in Portworx consists of four main parts: Selector, Namespace Selector, Conditions, and Actions. The Selector defines the set of volumes or pods the rule applies to, often using labels. Namespace Selector further narrows the scope to specific Kubernetes namespaces, allowing targeted policy application. Conditions specify triggers or thresholds such as capacity utilization, I/O metrics, or time-based schedules. When conditions are met, the Actions section defines automated responses such as volume expansion, migration, or alerting. This modular rule design enables flexible, policy-driven automation for storage management, helping maintain cluster health and performance without manual intervention. The Portworx Autopilot documentation provides detailed schema and examples, emphasizing these components as foundational for dynamic, autonomous cluster operationPure Storage Portworx Autopilot Guidesource.