Pass Pure Storage Portworx-Enterprise-Professional Exam with Guarantee Updated 77 Questions
Latest Portworx-Enterprise-Professional Pass Guaranteed Exam Dumps Certification Sample Questions
NEW QUESTION # 30
What does an administrator need to do if a drive fails and the pool contains metadata?
- A. Reformat the disk and reuse it.
- B. Delete the pool.
- C. Decommission the node.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
If a drive fails and the associated storage pool contains critical metadata, the safest and recommended action is to decommission the entire node. Metadata loss can compromise the integrity of volume allocations and cluster state. Decommissioning the node allows Portworx to safely remove the node from the cluster, replicate data, and redistribute workloads, preventing data loss or corruption. Deleting the pool or reformatting the disk without proper precautions risks losing metadata and causing cluster inconsistencies. Portworx's operational guidelines emphasize that nodes with failed drives holding metadata require careful decommissioning procedures to maintain cluster health and data durability, ensuring data is rebalanced and availability is preserved【Pure Storage Portworx Operations Guide source】.
NEW QUESTION # 31
What command can an administrator run to view Portworx alerts?
- A. pxctl alerts show
- B. pxctl cd list alerts
- C. Use Grafana to view alerts
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
To view current alerts raised by Portworx within the cluster, the primary command is pxctl alerts show. This CLI command lists all active alerts with details such as severity, affected resources, and timestamps. It helps administrators quickly identify issues impacting cluster health, storage pools, volumes, or nodes. While Grafana is a powerful visualization tool often used alongside Prometheus for monitoring, it requires additional setup and does not directly replace the immediate, real-time alert query functionality of pxctl. The pxctl cd list alerts is not a valid command. Portworx documentation emphasizes pxctl alerts show as the go-to tool for alert inspection during operational checks and troubleshooting, offering a concise and focused alert view integrated with Portworx's internal alerting system【Pure Storage Portworx Alerting Guide source】.
NEW QUESTION # 32
What is the primary command used to back up a volume in Portworx?
- A. pxctl volume snapshot create
- B. pxctl backup volume
- C. pxctl volume save
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The primary command to back up a volume in Portworx is pxctl volume snapshot create. This command creates a point-in-time snapshot of the specified volume, capturing its state for backup or recovery purposes. Snapshots can be local or uploaded to cloud object stores as part of disaster recovery strategies. The snapshot operation is efficient and minimally intrusive, using -on-write mechanisms to avoid full data duplication. Although other commands like pxctl volume save or pxctl backup volume might exist in other storage systems, Portworx explicitly uses pxctl volume snapshot create as its core volume backup command. The Portworx CLI documentation details this command as fundamental for data protection and snapshot lifecycle management in the cluster【Pure Storage Portworx CLI Guide source】.
NEW QUESTION # 33
What is the correct procedure to collect a support bundle for Autopilot in a Portworx cluster?
- A. Restart the Autopilot pod, and then run kubectl get logs.
- B. Delete the Autopilot pod, and then run pxctl service diags.
- C. Create a directory, send a support signal to the Autopilot process, and the support bundle files.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
To collect a comprehensive support bundle for Portworx Autopilot, the proper procedure is to create a dedicated directory, send a support signal to the running Autopilot process to trigger diagnostics collection, and then the generated support bundle files from that directory. This approach ensures all relevant Autopilot logs, configuration files, and runtime metrics are gathered in a structured way, enabling effective troubleshooting and root cause analysis. Simply restarting or deleting pods is insufficient, as it does not guarantee a full diagnostics capture. The Portworx troubleshooting and support documentation outlines this method as the standard for collecting detailed Autopilot support information, facilitating accelerated support response and issue resolution in production clusters【Pure Storage Portworx Support Guide source】.
NEW QUESTION # 34
A cluster administrator wants to define an Autopilot rule for Portworx.
What are the 4 main parts of an Autopilot rule?
- A. Enforcement, Match Expressions, Topology Key and Weight
- B. Selector, Namespace Selector, Conditions and Actions
- C. Replica, I/O profile, Secure, Placement Strategy
Answer: B
Explanation:
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 operation【Pure Storage Portworx Autopilot Guide source】.
NEW QUESTION # 35
A Portworx administrator wants to enable security without guest access on a new storage cluster using the Portworx Kubernetes operator.
What configuration items should be added to the StorageCluster configuration ?
- A. spec:
security:
enabled: true
auth:
guestAccess: 'Disabled' - B. spec:
security: 'Enabled' - C. spec:
security:
enabled: true
auth:
guestAccess: false
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Enabling security in Portworx without allowing guest access involves explicitly setting both enabled: true under the security section and guestAccess: false within the auth subsection of the StorageCluster spec. This configuration activates Portworx security features, enforcing authentication and encryption while preventing unauthenticated (guest) access to volumes. The guestAccess flag controls whether clients without valid credentials can access storage resources; setting it to false tightens security by requiring all access to be authenticated. This declarative setup is managed via the Kubernetes operator, ensuring consistent enforcement across cluster restarts and upgrades. Portworx's security documentation stresses this dual setting to harden clusters against unauthorized access while maintaining operational capabilities for authorized users, aligning with enterprise security policies and compliance standards【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 36
What command should be used to add a new drive to an existing storage cluster?
- A. pxctl service pool update -resize new-disk 150
- B. pxctl sv nw -a
- C. pxctl service drive add -drive /dev/dm-1 -operation start
Answer: C
Explanation:
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 efficiently【Pure Storage Portworx CLI Guide source】.
NEW QUESTION # 37
When updating the Portworx StorageCluster object to mount the SSL certificate secret, which path should be specified for the AWS_CA_BUNDLE environment variable?
- A. /etc/pwx/objectstore-cert/px-s3-certs
- B. /etc/pwx/objectstore-cert/objectstore.pem
- C. /opt/certs/objectstore.pem
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When configuring Portworx to communicate securely with an AWS S3-compatible Object Store using custom SSL certificates, the AWS_CA_BUNDLE environment variable must point to the mounted certificate file location. The correct path for this in the StorageCluster spec is /opt/certs/objectstore.pem. This file contains the Certificate Authority (CA) bundle trusted by Portworx to validate TLS connections to the object store. Ensuring this path is correctly specified and the certificate secret properly mounted is critical to prevent TLS handshake failures and enable secure communication. Portworx documentation and configuration samples specify /opt/certs/objectstore.pem as the standard path for the CA bundle within Portworx containers when integrating with custom or private certificate authorities【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 38
What command can be used to list all Autopilot rule objects in all namespaces in a Portworx cluster?
- A. pxctl list autopilotrules
- B. kubectl get autopilotruleobjects --all-namespaces
- C. kubectl describe autopilotrules
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The command pxctl list autopilotrules is used to list all Autopilot rule objects across namespaces within a Portworx cluster. Autopilot rules define automated policies for storage operations like scaling and volume migration. This CLI command queries the Portworx control plane to retrieve and display all configured Autopilot rules, regardless of the Kubernetes namespace they reside in. Using kubectl commands alone is insufficient because Autopilot rules are managed internally by Portworx and may not correspond directly to Kubernetes resources. Official Portworx CLI documentation confirms pxctl list autopilotrules as the primary command for comprehensive Autopilot rule enumeration, enabling administrators to audit and manage storage automation policies efficiently【Pure Storage Portworx Autopilot Guide source】.
NEW QUESTION # 39
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?
- A. kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: px-encrypted
provisioner: kubernetes.io/portworx-volume
parameters:
secure: "true"
repl: "2" - B. kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: px-encrypted
provisioner: kubernetes.io/portworx-volume
parameters:
sharedv4: "true"
repl: "2" - C. kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: px-encrypted
provisioner: kubernetes.io/portworx-volume
parameters:
encrypted: "true"
repl: "2"
Answer: C
Explanation:
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 manifests【Pure Storage Portworx StorageClass Guide source】.
NEW QUESTION # 40
What is a benefit of using Autopilot in Portworx environments?
- A. Provides enhanced security features for data protection.
- B. It facilitates the migration of containers across clusters.
- C. It automates the expansion of storage volumes based on predefined rules.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Autopilot is a key feature in Portworx designed to automate operational tasks such as capacity management and volume resizing. One of its primary benefits is automating the expansion of storage volumes based on predefined rules and thresholds. This means that when a volume approaches its storage limit, Autopilot can automatically trigger volume expansion without manual intervention, ensuring applications have uninterrupted access to storage resources. This automation reduces operational overhead, eliminates manual errors, and helps maintain application performance and availability. While Autopilot doesn't directly handle container migration or security enhancements, its dynamic volume management capabilities play a critical role in operational efficiency and business continuity. The Portworx documentation highlights Autopilot as a tool for intelligent, policy-driven storage management that adapts to workload demands in real time【Pure Storage Portworx Autopilot Guide source】.
NEW QUESTION # 41
Which CRD object can be used to restore an existing ApplicationBackup?
- A. VolumeSnapshot
- B. ApplicationRestore
- C. Migration
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The ApplicationRestore Custom Resource Definition (CRD) object in Portworx is specifically designed to restore an application from an existing ApplicationBackup. This object orchestrates the process of recovering a consistent snapshot of an application, including all its associated volumes, in Kubernetes environments. Using ApplicationRestore, administrators can define the source backup, restore location, and any necessary transformations during restoration. This facilitates disaster recovery, migration, or rollback scenarios for complex stateful applications. The Portworx backup and restore documentation clearly defines ApplicationRestore as the controller responsible for application-level recovery operations, ensuring data integrity and consistency throughout the restore workflow【Pure Storage Portworx Backup and Restore Guide source】.
NEW QUESTION # 42
What command allows a Portworx admin to create a cloud credential for the Object Store?
- A. pxctl service credentials create
- B. pxctl credentials create
- C. pxctl credentials generate
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
In Portworx, managing credentials for cloud object stores is vital to enable features like cloud snapshots and backups. The command pxctl credentials create is used to create and register cloud credentials with the Portworx cluster. This command allows administrators to specify provider details such as AWS, Google Cloud, or Azure, and input necessary access keys, secret keys, regions, and endpoints. Proper credential configuration enables Portworx to authenticate with external object stores securely, ensuring reliable data movement and disaster recovery operations. The CLI facilitates easy credential management, including listing, updating, and deleting credentials as needed. Official Portworx documentation highlights pxctl credentials create as the authoritative command for establishing cloud storage access, ensuring security best practices by managing credentials centrally within the Portworx control plane【Pure Storage Portworx CLI Guide source】.
NEW QUESTION # 43
Which command shows a summary of the Portworx cluster status?
- A. pxctl cluster status
- B. helm list --px
- C. kubectl get pxstatus
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The command pxctl cluster status provides a concise summary of the Portworx cluster's health and operational status. This includes node states, storage pool information, volume statuses, and quorum information. It is the primary CLI command for administrators to quickly assess cluster health and detect any issues affecting storage availability or performance. helm list --px is a Helm package management command unrelated to cluster status, and kubectl get pxstatus is not a valid Kubernetes or Portworx command. Portworx documentation recommends pxctl cluster status as an essential monitoring command during routine operations and troubleshooting to ensure the cluster is functioning properly and that all nodes are communicating and healthy【Pure Storage Portworx CLI Guide source】
NEW QUESTION # 44
Which command can be used to migrate volumes after cluster pairing is finished?
- A. kubectl cloudmigrate
- B. pxctl cloudmigrate start
- C. strokctl cloudmigrate start
Answer: B
Explanation:
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 regions【Pure Storage Portworx Disaster Recovery Guide source】.
NEW QUESTION # 45
After enabling security in Portworx, the pxctl command returns an "access denied" error.
What action must be taken to allow pxctl to gain access again?
- A. The administrator must create a new pxctl context by running pxctl context create and passing the -token command line parameter.
- B. Authentication is impossible because an authentication token was not generated before enabling security on the cluster.
- C. Pass both the --user and --password command line flags to the pxctl command. Username and password combination can be found in the px-admin-token secret.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When security is enabled in Portworx, all commands, including those issued via the pxctl CLI, require authentication to access the cluster. If pxctl returns an "access denied" error, it means the CLI does not have valid credentials. To regain access, administrators must provide authentication details using the --user and --password flags or configure a context with an authentication token. The username and password are stored securely within the Kubernetes secret px-admin-token. Using these credentials ensures pxctl commands are authorized to perform management operations. Without authentication, Portworx enforces strict access controls to protect sensitive storage operations and data. While creating new contexts via pxctl context create is a valid method, initially supplying credentials is mandatory. Failure to authenticate prevents any management activity, reinforcing Portworx's security posture. Official security guides outline these steps as fundamental to transitioning from unsecured to secured cluster operation and managing authenticated access effectively【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 46
An infrastructure admin wants to restrict installing Portworx on two nodes.
What label does the node need to have?
- A. px/enabled=false
- B. px/storage-node=false
- C. px/service=stop
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx uses node labeling as a mechanism to control on which Kubernetes nodes Portworx is installed and allowed to operate. To restrict Portworx installation on specific nodes, those nodes should be labeled with px/enabled=false. This label tells the Portworx Operator or installation scripts to exclude these nodes from Portworx deployment, preventing Portworx daemons from running there. This feature is useful for reserving nodes for non-storage workloads or avoiding unsupported hardware. Labels like px/service=stop or px/storage-node=false are not recognized by Portworx as controls for installation exclusion. The official Portworx deployment and node labeling documentation specify px/enabled=false as the standard method for controlling node participation in the storage cluster, offering administrators fine-grained control over cluster topology and resource allocation【Pure Storage Portworx Deployment Guide source】.
NEW QUESTION # 47
Which storage type does Portworx primarily rely on for storage provisioning?
- A. Direct Attached Storage (DAS)
- B. Object Storage
- C. Network File System (NFS)
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx primarily relies on Direct Attached Storage (DAS) for its storage provisioning. DAS refers to physical disks or SSDs directly connected to the nodes running Portworx. Using DAS enables high-performance, low-latency access to storage resources, crucial for stateful containerized applications. Portworx aggregates and abstracts these local devices into distributed storage pools, providing features like replication, encryption, and snapshots. While Portworx integrates with Object Storage for cloud snapshots and disaster recovery, and can support NFS for certain use cases, the core storage provisioning and volume management depend on DAS. The Portworx architecture documentation clarifies that leveraging local node storage is essential for delivering performant, resilient, and scalable persistent storage in Kubernetes environments【Pure Storage Portworx Architecture Guide source】.
NEW QUESTION # 48
Which flag in the Portworx StorageCluster spec enables telemetry?
- A. spec.autopilot.enabled
- B. spec.telemetry.enabled
- C. spec.csi.enabled
Answer: B
Explanation:
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 clusters【Pure Storage Portworx Telemetry Guide source】.
NEW QUESTION # 49
A Kubernetes administrator would like to transfer data from an existing Persistent Volume Claim (PVC) from another storage provider to a new Persistent Volume Claim (PVC) being provided by Portworx.
After creating the new PVC on Portworx, what must the administrator do to import the data?
- A. Run the pxctl import <SOURCE_PVC> <DESTINATION_PVC> command.
- B. Create a busybox pod that connects to both the source and destination PVCs and run a cp command.
- C. Create a DataExport Cluster Resource that specifies the source and destination PVC.
Answer: B
Explanation:
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 backends【Pure Storage Portworx Data Migration Guide source】.
NEW QUESTION # 50
Which 3 secret stores are supported by Portworx?
- A. AWS KMS, Google Cloud KMS, Kubernetes Secrets
- B. IBM KMS, Hashicorp Vault, Gemalto SafeNet KeySecure
- C. AWS KMS, Oracle Key Vault, Hashicorp Vault
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx integrates with three primary external secret stores to manage encryption keys securely: AWS Key Management Service (AWS KMS), Google Cloud Key Management Service (Google Cloud KMS), and Kubernetes Secrets. AWS KMS enables secure key storage and management for workloads running in AWS, leveraging native cloud security features. Google Cloud KMS provides similar key management for Google Cloud environments, allowing seamless integration with Google's security infrastructure. Kubernetes Secrets provide an on-premises or hybrid cloud method to store encryption keys and sensitive configuration securely within Kubernetes clusters, suitable for private data centers or cloud-agnostic deployments. This multi-cloud and hybrid cloud compatibility enable Portworx to meet diverse customer requirements for key management and regulatory compliance. Portworx security documentation details the setup, configuration, and best practices for each supported secret store to ensure data encryption keys are managed securely and efficiently across environments【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 51
What Portworx tool should be used to check the health of the storage cluster?
- A. pxctl
- B. kubectl
- C. helm
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The pxctl command-line interface is the primary tool for managing and monitoring Portworx clusters. It provides detailed health information, including node status, volume health, storage pools, and alerts. Running commands like pxctl status or pxctl cluster status offers real-time visibility into the cluster's operational state. While kubectl manages Kubernetes resources and helm handles package deployment, neither provides the specialized insight into Portworx storage internals that pxctl delivers. Portworx operational best practices emphasize using pxctl for health checks, troubleshooting, and maintenance tasks to ensure cluster reliability and performance【Pure Storage Portworx CLI Guide source】.
NEW QUESTION # 52
......
Pure Storage Portworx-Enterprise-Professional Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
New Portworx-Enterprise-Professional Test Materials & Valid Portworx-Enterprise-Professional Test Engine: https://www.realexamfree.com/Portworx-Enterprise-Professional-real-exam-dumps.html
Portworx-Enterprise-Professional Updated Exam Dumps [2026] Practice Valid Exam Dumps Question: https://drive.google.com/open?id=1olMiNUntWv7J2NZgAxhTJVsTjwVWw2xd
