What command allows a Portworx admin to create a cloud credential for the Object Store?
C
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
.
【
】
Which command can be used to migrate volumes after cluster pairing is finished?
A
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
.
【
】
What feature does a Portworx StorageClass provide to Kubernetes storage?
B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
In Kubernetes, StorageClasses define how persistent volumes are dynamically provisioned. A
Portworx StorageClass enables automated provisioning of Portworx volumes in response to
Persistent Volume Claim (PVC) requests. This eliminates the need for administrators to manually
create volumes, improving agility and scalability. The StorageClass encapsulates volume parameters
such as replication factor, encryption, and IO profiles, ensuring consistent storage policies across
deployments. While Portworx offers monitoring and backup capabilities, these are outside the scope
of the StorageClass resource itself. Kubernetes and Portworx documentation detail the StorageClass
as a critical abstraction for enabling self-service storage provisioning, allowing applications to
request storage with specific attributes dynamically and Portworx to satisfy these requests
seamlessly
Pure Storage Portworx Kubernetes Guide†source
.
【
】
What are the two components of Stork?
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
.
【
】
Which Portworx component is used to co-locate volumes with pods?
C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Portworx’s Volume Placement Strategy ensures that persistent volumes are co-located with the pods
that use them, enhancing performance and reducing latency. This strategy involves applying
placement rules and constraints that guide Kubernetes scheduler and Portworx storage operations to
place data volumes on nodes close to or the same as the pods. Co-location improves I/O throughput
and application responsiveness by minimizing network hops between compute and storage
resources. While Autopilot automates scaling and Stork manages storage-aware scheduling, Volume
Placement Strategy specifically handles volume location relative to workloads. The Portworx
architecture documentation highlights this component as critical for optimizing storage efficiency
and workload performance in Kubernetes environments running Portworx storage
Pure Storage
【
Portworx Architecture Docs†source
.
】
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?
A
Explanation:
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 integration
Pure Storage Portworx Snapshot
【
Guide†source
.
】
When is a volume considered "Public"?
B
Explanation:
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 violations
Pure Storage Portworx Security
【
Guide†source
.
】
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?
C
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
.
【
】
What is the minimum Stork version required to perform an Application Backup?
C
Explanation:
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 backups
Pure Storage
【
Portworx Backup Docs†source
.
】
What are the main resource types for Portworx alerts?
A
Explanation:
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
automation
Pure Storage Portworx Observability Guide†source
.
【
】