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 ?
Answer(s): C
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 standardsPure Storage Portworx Security Guidesource.
An infrastructure admin is troubleshooting a Portworx node that is down. What should be run first to check the Kubernetes cluster status?
Answer(s): B
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 issuesPure Storage Portworx Troubleshooting Guidesource.
What is the purpose of setting a defragmentation schedule in Portworx?
Answer(s): A
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 healthPure Storage Portworx Performance Guidesource.
An administrator wants to check the size, availability, and usage of all pools in the cluster.Which command should the administrator use?
Comprehensive and Detailed Explanation From Exact Extract:To view detailed information about storage pools in a Portworx cluster--including size, availability, usage, and health--administrators should use the command pxctl service pool show. This CLI command provides a comprehensive overview of all storage pools configured on cluster nodes, including pool IDs, device names, pool sizes, free space, and status. It helps administrators monitor resource utilization, detect degraded pools, and plan capacity expansions. While kubectl get storagecluster shows the overall cluster CRD status and pxctl cluster provision-status shows provisioning status, neither provides detailed pool-level insights. Portworx's operational documentation recommends pxctl service pool show as the definitive command for monitoring pool resources and ensuring storage health across the clusterPure Storage Portworx CLI Guidesource.
What command should an administrator run to verify a Portworx upgrade on Kubernetes?
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.
Post your Comments and Discuss Pure Storage Portworx-Enterprise-Professional exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Portworx-Enterprise-Professional content, but please register or login to continue.