Guaranteed Accomplishment with Newest Dec-2025 FREE Pure Storage Portworx-Enterprise-Professional
Use Valid New Free Portworx-Enterprise-Professional Exam Dumps & Answers
NEW QUESTION # 43
What configuration steps should a Portworx Administrator perform to ensure that Portworx can use the S3 Object Store using a custom/3rd party (not signed by public CA) certificate?
- A. Create a secret containing the certificate and run pxctl certificate import command.
- B. Create a Kubernetes secret containing the certificate and reference it in the storagecluster via env variable.
- C. No additional configuration is necessary.
Answer: B
Explanation:
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 used【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 44
Portworx uses secrets to authenticate Kubernetes to the Portworx system.
When using the shared authentication method, where is that secret stored?
- A. In the 'default' namespace
- B. In the same namespace as the Portworx installation
- C. In the namespace that runs the application that needs to provision the storage resources
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When using shared authentication in Portworx, the Kubernetes secret that contains the authentication token or credentials is stored in the same namespace where the application requesting storage resides. This placement ensures that the application pods have access to the secret needed to authenticate to Portworx for volume provisioning and management. It enables a security boundary aligned with Kubernetes namespaces, restricting credentials to the scope of the application. Storing the secret in the default namespace or the Portworx installation namespace would be less secure or less flexible in multi-tenant clusters. Portworx authentication documentation highlights this design for efficient, secure access management in Kubernetes environments【Pure Storage Portworx Security Guide source】.
NEW QUESTION # 45
What are the three severity levels for Portworx alerts?
- A. INFO, WARNING, ALARM
- B. INFO, WARNING, CRITICAL
- C. INFO, WARNING, ERROR
Answer: B
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 # 46
What is the primary purpose of Stork in a Kubernetes cluster?
- A. To deploy applications automatically.
- B. To manage storage operations and migrations.
- C. To monitor network traffic.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Stork (Storage Orchestrator for Kubernetes) is a Portworx component designed to enhance Kubernetes storage management. Its primary purpose is to orchestrate storage-aware operations, including volume scheduling, migration, backup, and disaster recovery. Stork integrates deeply with Kubernetes to provide application-aware scheduling decisions that respect storage constraints such as volume locality and affinity. It also facilitates migration of stateful workloads by coordinating volume replication and failover. Stork simplifies complex storage workflows in Kubernetes environments, enabling seamless backup and restore of applications and improving overall resilience. Portworx's official documentation highlights Stork as a key enabler for business continuity by managing storage operations and migrations, making it essential for Kubernetes environments running critical stateful workloads with Portworx storage【Pure Storage Portworx Stork Guide source】.
NEW QUESTION # 47
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 # 48
When upgrading Portworx on Kubernetes using the Operator, what step must the administrator take if using the px-versions configmap?
- A. Delete the existing configmap.
- B. Update the version manifest.
- C. Create a new namespace for the configmap.
Answer: B
Explanation:
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 clusters【Pure Storage Portworx Upgrade Guide source】.
NEW QUESTION # 49
What are the two components of Stork?
- A. Stork scheduler and an extender
- B. Stork snapshots and restores
- C. Stork object store and S3 bucket
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 # 50
An infrastructure admin is troubleshooting a Portworx node that is down.
What should be run first to check the Kubernetes cluster status?
- A. kubectl get node -o wide to ensure cluster nodes are in the Ready status.
- B. pxctl status to check the status of Portworx on the node.
- C. journalctl -u kubelet to identify the problem on the node.
Answer: A
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 # 51
An infrastructure admin wants to restrict installing Portworx in two nodes.
What label does the node need to have?
- A. px/storage-node=false
- B. px/enabled=false
- C. px/service=stop
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Restricting Portworx installation on certain Kubernetes nodes is achieved by labeling those nodes with px/enabled=false. This label signals the Portworx Operator or installer to exclude these nodes from Portworx deployment. This allows admins to reserve nodes for other workloads or prevent Portworx from running on unsupported hardware. The label px/service=stop or px/storage-node=false are not recognized controls in the Portworx installation process. Portworx deployment guides consistently document the use of px/enabled=false for node exclusion, providing a simple, declarative way to control cluster topology and resource assignment during Portworx installations and upgrades【Pure Storage Portworx Deployment Guide source】.
NEW QUESTION # 52
An administrator needs to create a backup of a Portworx volume in an AWS S3 bucket and has already configured the secrets so Portworx can connect to the AWS S3 bucket.
What command is needed to create the backup?
- A. pxctl volume snapshot create -name <snapshot-name> <volume-name>
- B. pxctl credentials create -provider s3 -s3-access-key <AccessKey> -s3-secret-key <secretKey> -s3-region us-east-1 -s3-endpoint s3.amazonaws.com -bucket <bucket-name> <credentials-name>
- C. pxctl cloudsnap backup <volumename> -cred-id <credentials-name>
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
After configuring credentials for AWS S3 object storage, the administrator uses the command pxctl cloudsnap backup <volumename> -cred-id <credentials-name> to create a cloud snapshot backup of a Portworx volume. This command instructs Portworx to take a point-in-time snapshot of the specified volume and upload it securely to the configured S3 bucket using the referenced credentials. The command leverages Portworx's cloud snapshot feature for disaster recovery and long-term retention. Option B relates to creating credentials and is not the backup command. Option C creates a local snapshot but does not back it up to the cloud. The Portworx CLI documentation highlights pxctl cloudsnap backup as the core method to perform backups to cloud object storage, enabling data protection strategies aligned with cloud-native architectures【Pure Storage Portworx Cloud Snapshot Guide source】.
NEW QUESTION # 53
An infrastructure admin wants to restrict installing Portworx on two nodes.
What label does the node need to have?
- A. px/storage-node=false
- B. px/enabled=false
- C. px/service=stop
Answer: B
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 # 54
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. Create a directory, send a support signal to the Autopilot process, and the support bundle files.
- C. Delete the Autopilot pod, and then run pxctl service diags.
Answer: B
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 # 55
What is the correct procedure to upgrade a Portworx cluster from version 3.0 to 3.1 using the Portworx Operator?
- A. Edit the StorageCluster CR and update the .spec.image parameter from portworx/oci-monitor:3.0 to portworx/oci-monitor:3.1.
- B. Execute the 'pxctl cluster upgrade -version 3.1' command.
- C. No manual upgrade is needed as Portworx will automatically upgrade to the latest version.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Upgrading Portworx clusters managed by the Kubernetes Operator requires a declarative update to the StorageCluster Custom Resource Definition (CRD). Specifically, the administrator must edit the StorageCluster resource and update the .spec.image field to point to the new version image, such as changing portworx/oci-monitor:3.0 to portworx/oci-monitor:3.1. This change instructs the Operator to roll out the new image across the cluster nodes, performing a seamless upgrade with minimal downtime. The pxctl CLI does not perform upgrades in Operator-managed environments; it is primarily for direct cluster management. The Operator ensures orderly upgrade sequencing, node by node, handling pod restarts and health checks. Automatic upgrades without manual intervention are not currently supported to prevent unintentional disruptions. Official Portworx upgrade documentation details this procedure, emphasizing the importance of version pinning and controlled rollout for production stability and rollback capabilities during upgrades【Pure Storage Portworx Upgrade Guide source】.
NEW QUESTION # 56
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 # 57
What is a benefit of using Autopilot in Portworx environments?
- A. It automates the expansion of storage volumes based on predefined rules.
- B. Provides enhanced security features for data protection.
- C. It facilitates the migration of containers across clusters.
Answer: A
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 # 58
What is the purpose of setting a defragmentation schedule in Portworx?
- A. To monitor the health of the storage cluster.
- B. To improve performance by running defragmentation during low workload periods.
- C. To back up data to the cloud.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Defragmentation in Portworx reorganizes storage blocks to reduce fragmentation caused by frequent write and delete operations. Scheduling defragmentation during low workload periods ensures minimal impact on application performance while improving storage efficiency and I/O throughput. This optimization leads to faster read/write operations and prolongs the lifespan of storage devices by minimizing random I/O. Portworx provides administrators the ability to define defragmentation windows and recurrence policies within cluster configurations to automate this process. The official Portworx documentation explains that carefully timed defragmentation is critical to maintaining optimal cluster performance without disrupting business-critical workloads, making it an essential part of ongoing cluster maintenance and operational health【Pure Storage Portworx Performance Guide source】.
NEW QUESTION # 59
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. Label NODE01, NODE03, and NODE05 with 'px1/metadata-node=true' prior to installation.
- B. It is not possible to configure the location of the KVDB 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 # 60
What is the primary function of the telemetry pod added to each node when telemetry is enabled in Portworx?
- A. To monitor the health of the node.
- B. To upload Portworx diagnostics to Pure1.
- C. To manage network configurations.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When telemetry is enabled, Portworx deploys a telemetry pod on each node whose primary function is to collect diagnostic and performance data and securely upload it to Pure1, Pure Storage's cloud-based management and analytics platform. This pod gathers metrics such as resource utilization, error rates, and configuration changes, enabling proactive monitoring and predictive analytics. The data helps Pure1 provide customers with actionable insights, alerting, and automated support features, improving cluster reliability and reducing operational overhead. The telemetry pod does not directly monitor node health (which is the role of other components) nor manage network settings; its focus is on data collection and communication with Pure1. Official Portworx telemetry documentation highlights this pod as critical for enabling cloud-based health monitoring and customer support enhancements【Pure Storage Portworx Telemetry Guide source】.
NEW QUESTION # 61
Which storage type does Portworx primarily rely on for storage provisioning?
- A. Object Storage
- B. Network File System (NFS)
- C. Direct Attached Storage (DAS)
Answer: C
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 # 62
What is the recommended practice for managing the lifecycle of snapshots in Portworx?
- A. Configure the retention policies.
- B. Retain all snapshots indefinitely.
- C. Manually delete old snapshots to free up space.
Answer: A
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 # 63
What command can an administrator run to view Portworx alerts?
- A. pxctl cd list alerts
- B. Use Grafana to view alerts
- C. pxctl alerts show
Answer: C
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 # 64
What is the minimum kernel needed for Portworx?
- A. Kernel version 3.10 or greater
- B. Portworx works with any kernel
- C. Kernel version 4.15 or greater
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx requires a minimum Linux kernel version of 3.10 or greater to operate properly. This requirement stems from Portworx's dependencies on certain kernel features and modules that became standard from kernel version 3.10 onwards. The kernel version affects support for device-mapper, overlay filesystems, network stack enhancements, and other low-level capabilities essential for Portworx's block storage functionality and performance. Although newer kernels (like 4.15+) offer additional features and improvements, Portworx maintains compatibility back to 3.10 to support a wide range of enterprise Linux distributions such as RHEL, CentOS, and Ubuntu LTS releases. The official Portworx system requirements document explicitly states kernel 3.10 as the minimum supported version to ensure stability and compatibility in production environments【Pure Storage Portworx System Requirements source】.
NEW QUESTION # 65
What label can be used to migrate Network Policies with Asynchronous DR?
- A. skipNetworkPolicyCheck: false
- B. By default Network policies are migrated
- C. skipNetworkPolicyCheck: true
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
When using Portworx Asynchronous Disaster Recovery (DR) to migrate workloads and storage across clusters, network policies can sometimes interfere with seamless failover. The label skipNetworkPolicyCheck: true can be used to instruct the DR mechanism to bypass strict network policy checks during migration. This allows applications and volumes to migrate even if network policies differ or are incompatible between source and destination clusters. Without this label, migration might be blocked or fail due to network restrictions. By default, network policies are not always migrated, and strict checks are performed unless explicitly skipped. Portworx DR documentation details this option as a means to increase migration flexibility, reduce operational friction, and enable faster recovery during disaster scenarios while administrators work on aligning network configurations【Pure Storage Portworx DR Guide source】.
NEW QUESTION # 66
What is the minimum number of cores needed to run Portworx?
- A. 0
- B. 1
- C. 2
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx requires a minimum of 4 CPU cores per node to operate efficiently. This minimum ensures sufficient compute resources to handle storage management operations, volume I/O, replication, and metadata services without performance bottlenecks. While more cores can improve throughput and scalability, 4 cores is the documented baseline for supporting production workloads and maintaining cluster responsiveness. The Portworx system requirements specify this CPU baseline to guarantee stable operation alongside other Kubernetes node workloads. Deployments with fewer CPU resources may face degraded performance or instability. Official Portworx hardware requirements recommend 4 cores or more per node to meet performance and reliability objectives in typical enterprise environments【Pure Storage Portworx System Requirements source】.
NEW QUESTION # 67
An application team is preparing to deploy an ElasticSearch application and wants all Portworx volumes created in 6 specific Kubernetes nodes.
Which Portworx feature should they use to achieve this?
- A. Autopilot
- B. Volume placement strategy
- C. Stork
Answer: B
Explanation:
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 clusters【Pure Storage Portworx Deployment Guide source】.
NEW QUESTION # 68
......
Portworx-Enterprise-Professional Braindumps PDF, Pure Storage Portworx-Enterprise-Professional Exam Cram: https://www.testpdf.com/Portworx-Enterprise-Professional-exam-braindumps.html
New 2025 Portworx-Enterprise-Professional Sample Questions Reliable Portworx-Enterprise-Professional Test Engine: https://drive.google.com/open?id=1SYmvS1Hk4CYYB1f2AufFnprAgyL6aiMe
