Regular Free Updates Portworx-Enterprise-Professional Dumps Real Exam Questions Test Engine May 19, 2026
Practice Test Questions Verified Answers As Experienced in the Actual Test!
NEW QUESTION # 25
A Portworx administrator wants to control which nodes will host a KVDB installation.
What steps must an administrator take to ensure that KVDB installs on NODE01, NODE03, and NODE05?
- A. It is not possible to configure the location of the KVDB prior to installation.
- B. Label NODE01, NODE03, and NODE05 with 'px1/metadata-node=true' prior to installation.
- C. Change the following in the 'StorageCluster' spec prior to installation:
spec:
kvdb:
selector:
matchNodeName:
- NODE01
- NODE03
- NODE05
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx provides a mechanism to control KVDB pod placement through the kvdb.selector.matchNodeName field in the StorageCluster Custom Resource Definition (CRD). This allows administrators to explicitly specify node names where KVDB pods will be deployed. By setting this selector to include NODE01, NODE03, and NODE05, KVDB pods will run exclusively on these nodes, ensuring better control of quorum, fault tolerance, and performance. Node labeling alone is insufficient unless the labels are properly referenced in the spec, making direct node name matching the most straightforward and reliable method. This configuration must be done prior to cluster installation to ensure proper pod placement. Official Portworx documentation on cluster deployment and KVDB configuration confirms this method as the recommended best practice for managing KVDB nodes, critical for maintaining database availability and consistency within the Portworx cluster【Pure Storage Portworx Install Guide source】.
NEW QUESTION # 26
How would an administrator schedule automatic backups of a volume using Portworx?
- A. Configure and apply schedule policies.
- B. Execute px backup volume.
- C. Use a cron job to execute pxctl snapshot create.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx provides a declarative method to schedule automatic backups by configuring schedule policies within its Backup and DR framework. These policies specify when and how frequently backups should occur, retention rules, and target storage locations. By applying schedule policies, administrators enable Portworx to perform backups automatically without manual intervention or external scripting. Using cron jobs to run pxctl snapshot create is possible but less integrated, error-prone, and not recommended for scalable environments. The command px backup volume is not a valid Portworx CLI command. The Portworx backup documentation encourages using native schedule policies for reliable, maintainable, and policy-driven backup automation, supporting compliance and disaster recovery strategies【Pure Storage Portworx Backup Guide source】.
NEW QUESTION # 27
What is a local snapshot in the context of Portworx?
- A. A snapshot that is automatically backed up to the cloud.
- B. A snapshot that is stored in a remote data center.
- C. A snapshot that is stored on the same cluster as the original volume.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
A local snapshot in Portworx refers to a point-in-time of a volume's data that is stored within the same storage cluster as the original volume. Local snapshots use efficient -on-write techniques to minimize storage overhead while preserving the volume state for backup, recovery, or rollback operations. Unlike cloud or remote snapshots, local snapshots do not require network transfer or object storage integration, enabling fast snapshot creation and restoration with low latency. They are ideal for short-term data protection, testing, or recovery scenarios where immediate access to snapshots is required. Portworx's snapshot documentation describes local snapshots as the foundational snapshot type, essential for operational backups and data consistency within Kubernetes clusters using Portworx storage【Pure Storage Portworx Snapshot Guide source】.
NEW QUESTION # 28
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 DataExport Cluster Resource that specifies the source and destination PVC.
- C. Create a busybox pod that connects to both the source and destination PVCs and run a cp command.
Answer: C
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 # 29
What Portworx swap requirement exists on a Portworx-enabled Linux host?
- A. Swap should be enabled.
- B. Portworx does not have a requirement for swap to be enabled or disabled.
- C. Swap should be disabled.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx requires swap to be disabled on Linux hosts where it runs. Disabling swap is necessary because swap usage can cause unpredictable latency and performance degradation for storage operations. Portworx relies on consistent and predictable I/O performance for managing block devices and volumes, which is incompatible with the potential delays caused by swapping memory pages to disk. Additionally, many Kubernetes environments recommend disabling swap to meet Kubernetes scheduler requirements, aligning with Portworx's needs. Portworx installation and system requirements documentation explicitly state that swap should be disabled on nodes running Portworx to ensure cluster stability, optimal performance, and predictable behavior of storage operations【Pure Storage Portworx System Requirements source】.
NEW QUESTION # 30
What command should the administrator run if Portworx logs report "Node is not in quorum"?
- A. The administrator should do nothing.
- B. The administrator should run pxctl service status.
- C. The administrator should check output of pxctl status on each storage node.
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
If Portworx logs indicate that a node is not in quorum, the administrator's first step is to verify the status of each storage node in the cluster using the command pxctl status. This command provides detailed information about node connectivity, quorum status, and cluster health. The quorum is critical for distributed consensus and cluster consistency. Checking each node's status helps identify network partitions, node failures, or communication issues causing quorum loss. Simply running pxctl service status provides service-level info but not the comprehensive node quorum details needed. The Portworx troubleshooting documentation stresses using pxctl status as the primary diagnostic tool when encountering quorum-related alerts to ensure cluster stability and resolve issues promptly【Pure Storage Portworx Troubleshooting Guide source】.
NEW QUESTION # 31
Which command shows a summary of the Portworx cluster status?
- A. helm list --px
- B. pxctl cluster status
- C. kubectl get pxstatus
Answer: B
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 # 32
What is the recommended practice for managing the lifecycle of snapshots in Portworx?
- A. Retain all snapshots indefinitely.
- B. Configure the retention policies.
- C. Manually delete old snapshots to free up space.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The recommended approach to managing Portworx snapshots is to configure retention policies that automatically govern the lifecycle of snapshots, including their expiration and deletion. These policies ensure that snapshots are retained only as long as needed, preventing uncontrolled accumulation that can consume excessive storage and degrade performance. By setting retention rules, administrators can automate snapshot cleanup, enforce compliance requirements, and optimize resource usage. Manual deletion is error-prone and inefficient at scale, and retaining all snapshots indefinitely can lead to capacity exhaustion and management challenges. Portworx documentation provides detailed guidance on defining snapshot retention schedules, including time-based expiration and count limits, enabling administrators to maintain a balance between data protection and storage efficiency【Pure Storage Portworx Snapshot Management Guide source】.
NEW QUESTION # 33
What are the three severity levels for Portworx alerts?
- A. INFO, WARNING, ERROR
- B. INFO, WARNING, ALARM
- C. INFO, WARNING, CRITICAL
Answer: C
Explanation:
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 management【Pure Storage Portworx Alerting Guide source】.
NEW QUESTION # 34
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/service=stop
- C. px/storage-node=false
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 # 35
What Portworx tool should be used to check the health of the storage cluster?
- A. helm
- B. kubectl
- C. pxctl
Answer: C
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 # 36
An infrastructure admin is troubleshooting a Portworx node that is down.
What should be run first to check the Kubernetes cluster status?
- A. pxctl status to check the status of Portworx on the node.
- B. kubectl get node -o wide to ensure cluster nodes are in the Ready status.
- C. journalctl -u kubelet to identify the problem on the node.
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 issues【Pure Storage Portworx Troubleshooting Guide source】.
NEW QUESTION # 37
What are the two components of Stork?
- A. Stork scheduler and an extender
- B. Stork object store and S3 bucket
- C. Stork snapshots and restores
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Stork (Storage Orchestrator for Kubernetes) is a Portworx utility designed to improve Kubernetes storage orchestration. Its two main components are the Stork scheduler and the Stork extender. The scheduler works by placing pods in Kubernetes clusters based on storage constraints, such as volume affinity and anti-affinity, improving application resiliency and data locality. The extender integrates with Kubernetes' default scheduler, influencing pod scheduling decisions to respect storage policies and optimize workload placement. Together, these components enable advanced features such as application-aware migration, snapshot management, and backup coordination. Portworx documentation explains that Stork's design helps maintain stateful application availability during scaling, upgrades, or disaster recovery scenarios by making Kubernetes scheduling storage-aware【Pure Storage Portworx Stork Guide source】.
NEW QUESTION # 38
What is a benefit of using Autopilot in Portworx environments?
- A. It facilitates the migration of containers across clusters.
- B. Provides enhanced security features for data protection.
- 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 # 39
What does the DriveStateChange alert indicate?
- A. Free volume space going below the recommended level of 5%
- B. Free disk space going below the recommended level of 10%
- C. Free disk space going below the recommended level of 20%
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
The DriveStateChange alert in Portworx indicates that free disk space on a storage device has fallen below the recommended threshold of 10%. This alert warns administrators that storage capacity on a particular disk is critically low and that immediate action may be needed to avoid performance degradation or failures. Monitoring disk space is essential to maintain cluster health and prevent data loss. Portworx automatically generates this alert as part of its proactive monitoring system, providing early warning so operators can add capacity, remove unnecessary data, or re-balance workloads. The alert documentation advises maintaining sufficient free space to ensure optimal performance and data durability in the Portworx cluster【Pure Storage Portworx Alerting Guide source】.
NEW QUESTION # 40
Which platform is supported by Portworx for deployment?
- A. AWS
- B. DCOS
- C. Docker Swarm
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx primarily supports deployment on Kubernetes and is well-integrated with major cloud platforms including Amazon Web Services (AWS). AWS offers native infrastructure and storage services that complement Portworx's capabilities for cloud-native storage, including integration with Elastic Block Store (EBS) and S3 Object Storage. While Portworx historically supported container orchestrators like Docker Swarm and Mesosphere DC/OS (DCOS), the primary and recommended platform for production deployments today is Kubernetes on cloud providers such as AWS, Azure, and Google Cloud. AWS's ecosystem allows Portworx to leverage scalable compute and storage infrastructure, advanced networking, and cloud security features, making it a preferred platform. Portworx official platform support documentation lists AWS as a key supported environment for its container storage solutions【Pure Storage Portworx Platform Support Guide source】.
NEW QUESTION # 41
......
Pass Pure Storage Portworx-Enterprise-Professional Exam in First Attempt Easily: https://passleader.dumpexams.com/Portworx-Enterprise-Professional-vce-torrent.html