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

Page: 1 / 14
Total 75 questions
Question 1

What is the primary benefit of using Dynamic Provisioning and Storage Classes in Portworx?



Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

Dynamic Provisioning in Kubernetes with Portworx StorageClasses enables automatic, on-demand creation of storage volumes as requested by applications through Persistent Volume Claims (PVCs). This eliminates the need for administrators to manually create and manage volumes, significantly improving operational efficiency and accelerating application deployment. StorageClasses encapsulate parameters such as replication, encryption, and IO profiles, ensuring consistent volume configuration. Dynamic Provisioning also supports scaling and workload agility by provisioning storage transparently based on application needs. This feature is central to cloud-native storage management and is well documented in both Kubernetes and Portworx installation guides. It contrasts with manual volume creation, which is labor-intensive and error-prone, thus dynamic provisioning enhances automation and simplifies storage lifecycle managementPure Storage Portworx Kubernetes Guidesource.


Question 2

Which flag in the Portworx StorageCluster spec enables telemetry?



Answer : B

Comprehensive and Detailed Explanation From Exact Extract:

Telemetry in Portworx refers to the automated collection and reporting of cluster performance and health metrics to Pure1 or other monitoring services. To enable telemetry, the spec.telemetry.enabled flag must be set to true in the StorageCluster Custom Resource Definition (CRD). This setting activates the telemetry pod on each node, which collects data such as resource usage, storage capacity, and errors, then securely uploads it to Pure Storage's management platform. Enabling telemetry helps administrators gain insights into cluster performance trends, preemptively identify issues, and optimize resource utilization. The Portworx operator respects this flag during installation and upgrades to ensure telemetry is consistently configured. Neither spec.autopilot.enabled (which controls the Autopilot feature) nor spec.csi.enabled (which controls CSI driver deployment) affects telemetry settings. Official Portworx documentation highlights this flag as critical for activating health monitoring and analytics features within Portworx clustersPure Storage Portworx Telemetry Guidesource.


Question 3

A Portworx administrator wants to create a storage class that can be used to create volumes with the following characteristics:

* Encrypted volume

* Two replicas

Which definition should the administrator use?



Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

To create a StorageClass in Kubernetes for Portworx volumes that are encrypted and replicated twice, the correct parameters are encrypted: 'true' to enable encryption and repl: '2' to specify two replicas. Option A accurately sets these parameters, ensuring volumes provisioned with this StorageClass will be encrypted at rest and maintain two replicas for data redundancy. Option B uses sharedv4: 'true', which relates to NFS-like sharing, not encryption. Option C uses secure: 'true', which is not the recognized parameter for enabling encryption in Portworx StorageClass definitions. The official Portworx StorageClass parameter documentation confirms encrypted as the correct flag for encryption and repl to specify replication factor, enabling administrators to enforce data security and availability policies declaratively through Kubernetes manifestsPure Storage Portworx StorageClass Guidesource.


Question 4

Which two CRDs are required for performing an ApplicationBackup?



Answer : C

Comprehensive and Detailed Explanation From Exact Extract:

To perform an ApplicationBackup in Portworx, two Kubernetes Custom Resource Definitions (CRDs) are essential: BackupLocation and ApplicationBackup. The BackupLocation CRD defines the target backup storage, such as an S3 bucket or NFS share, including credentials and endpoints. ApplicationBackup defines the specifics of the backup operation, including which application volumes to back up, schedules, and retention policies. Together, they enable declarative backup management within Kubernetes, allowing administrators to configure, automate, and monitor backups of stateful applications using Portworx. These CRDs provide flexibility and integration with Kubernetes-native tools, improving disaster recovery capabilities. Portworx backup documentation describes these CRDs as the foundation of its application-aware backup and restore systemPure Storage Portworx Backup Docssource.


Question 5

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 6

When upgrading Portworx on Kubernetes using the Operator, what step must the administrator take if using the px-versions configmap?



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.


Question 7

What solution should a Portworx administrator use to store snapshots of a critical application volume in an Object Store?



Answer : A

Comprehensive and Detailed Explanation From Exact Extract:

Cloud Snapshots are designed to store snapshots of critical application volumes directly into an external Object Store such as Amazon S3 or other S3-compatible storage. This solution provides offsite durability, disaster recovery capability, and long-term retention beyond the cluster's local storage capacity. Cloud Snapshots allow administrators to create consistent, incremental snapshots that are efficiently uploaded to cloud storage, enabling protection against data loss scenarios such as cluster failure or site outages. This contrasts with Local Snapshots, which remain on the cluster's local storage, and Backups, which may refer to full data copies. The Portworx documentation explains Cloud Snapshots as the recommended approach for storing critical volume snapshots securely and durably offsite, supporting business continuity strategiesPure Storage Portworx Cloud Snapshot Guidesource.


Page:    1 / 14   
Total 75 questions