What option can a Portworx administrator use to perform snapshots of Repl 2 or 3 volumes when there is limited space on the cluster and no Object Store is configured?
Answer(s): A
Comprehensive and Detailed Explanation From Exact Extract:Skinny Snapshots are a space-efficient snapshot technique used by Portworx for replicated volumes (Repl 2 or 3) when storage capacity is limited and no external Object Store is configured. Unlike full snapshots that duplicate data blocks, skinny snapshots capture only the differences (deltas) since the last snapshot, minimizing space consumption. This method allows administrators to take frequent snapshots without significantly impacting storage availability. Skinny Snapshots are particularly useful for on-premises environments or clusters without access to cloud object storage, balancing snapshot granularity with resource constraints. Official Portworx snapshot documentation explains how skinny snapshots work internally, improving backup and recovery capabilities under tight storage conditions without requiring cloud integrationPure Storage Portworx Snapshot Guidesource.
When is a volume considered "Public"?
Answer(s): B
Comprehensive and Detailed Explanation From Exact Extract:In Portworx, a volume is considered "Public" when guest access is enabled. Guest access allows users and applications without explicit Portworx authentication credentials to access the volume. This setting is typically used in less restrictive environments where access control is relaxed, but it reduces security by exposing data to potentially unauthorized entities. Public volumes can be accessed by any entity with network connectivity and basic permissions, which is why enabling guest access is carefully controlled in secure deployments. Portworx documentation on security models and access controls stresses that public volumes should be used sparingly and monitored closely due to the elevated risk of data exposure and compliance violationsPure Storage Portworx Security Guidesource.
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?
Answer(s): C
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 clustersPure Storage Portworx Deployment Guidesource.
What is the minimum Stork version required to perform an Application Backup?
Comprehensive and Detailed Explanation From Exact Extract:Stork version 2.3 is the minimum version required to support Application Backup features in Portworx. Application Backup allows for consistent snapshots and restores of complex, multi-volume, and multi-pod stateful applications. This capability depends on enhancements introduced in Stork 2.3 that enable application-aware backup orchestration, coordination between Kubernetes and storage layers, and integration with backup policies. Earlier Stork versions lack these features, making them unsuitable for application-level backups. Portworx release notes and Stork documentation confirm that version 2.3 introduced key functionalities that underpin the reliable backup and restore workflows for stateful workloads, making it a baseline requirement for disaster recovery and business continuity implementations involving application backupsPure Storage Portworx Backup Docssource.
What are the main resource types for Portworx alerts?
Comprehensive and Detailed Explanation From Exact Extract:Portworx alerts are generated for several resource types within the storage cluster environment, primarily including Nodes, Disks, Pods, Namespaces, and Volumes. These alerts provide real-time notifications of events such as node failures, disk health degradation, volume status changes, pod crashes, or namespace-level issues affecting storage consumption or performance. Monitoring these resource types helps administrators proactively manage cluster health, maintain high availability, and troubleshoot faults before they impact applications. The Portworx alerting framework aggregates data from these resources and integrates with external monitoring systems for centralized alert management. Official Portworx observability and alerting documentation list these resource categories as the core focus of Portworx alerting mechanisms, critical for operational awareness and automationPure Storage Portworx Observability 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.