Question 1

What is the primary function of the Portworx OCI monitor pod in a Kubernetes environment?

Accepted Answer

B

Explanation: The Portworx OCI monitor (px-oci-mon) is a critical component that runs as a container within the Portworx DaemonSet on each node. Its primary function is to act as a watchdog for the node's health from a storage perspective. It continuously monitors the state of the underlying OCI-compliant container runtime (like containerd or Docker) and the main Portworx service. If it detects that either of these essential services has become unresponsive, it will take corrective action, such as restarting the Portworx container, to restore the node's functionality and ensure the stability of the Portworx storage cluster.

Question 2

How should a Portworx administrator expose metrics to externally provisioned Prometheus?

Accepted Answer

A

Explanation: To expose Portworx metrics to an externally managed Prometheus instance, the administrator must modify the StorageCluster custom resource. The correct method is to set the exportMetrics flag to true under the spec.monitoring.prometheus path. This declarative approach instructs the Portworx Operator to create the necessary ServiceMonitor or PodMonitor resources that the external Prometheus Operator can discover, allowing it to scrape metrics from Portworx pods without deploying the Portworx-internal Prometheus stack.

Question 3

What command allows a Portworx admin to create a cloud credential for the Object Store?

Accepted Answer

C

Explanation: The pxctl credentials create command is the designated utility within the Portworx command-line interface for registering cloud provider credentials. This command allows an administrator to securely store access keys and other necessary authentication details for various cloud services, such as AWS S3, Azure Blob Storage, or Google Cloud Storage. These stored credentials are then used by Portworx for features that interact with the cloud, most notably for creating cloud snapshots and backing up volumes to an object store. The command requires specifying the provider and the relevant authentication parameters.

Question 4

What Kubernetes resource allows visibility of the Parent Volume and the snapshot ID?

Accepted Answer

A

Explanation: The VolumeSnapshot is a namespaced Kubernetes API resource that users create to initiate a snapshot of a PersistentVolumeClaim (PVC). The VolumeSnapshot object's specification (spec) contains a source field that explicitly references the parent volume by its persistentVolumeClaimName. Once the underlying storage provider, such as Portworx, successfully creates the snapshot, the status field of the VolumeSnapshot object is updated. This status includes a reference (boundVolumeSnapshotContentName) to the VolumeSnapshotContent object, which holds the unique snapshot identifier (snapshotHandle) from the storage system. Therefore, the VolumeSnapshot resource provides direct visibility to the parent volume (PVC) and an indirect link to the snapshot ID.

Question 5

What feature does a Portworx StorageClass provide to Kubernetes storage?

Accepted Answer

B

Explanation: A Portworx StorageClass in Kubernetes is a fundamental component for enabling dynamic volume provisioning. It allows administrators to define different tiers or profiles of storage, specifying parameters such as replication factor (repl), I/O profile (ioprofile), and encryption. When a user submits a PersistentVolumeClaim (PVC) that references a Portworx StorageClass, the Portworx provisioner automatically creates a corresponding PersistentVolume (PV) that matches the defined specifications, without requiring manual intervention. This process is the essence of automated storage provisioning.

Question 6

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?

Accepted Answer

B

Explanation: To deterministically control which nodes host the internal Portworx Key-Value Database (KVDB), an administrator must define node selection criteria within the StorageCluster custom resource specification. The spec.kvdb section is designed for this purpose. By using a selector, such as nodeAffinity or a nodeSelector, the Portworx Operator can be instructed to schedule the KVDB pods exclusively on the specified nodes. While the exact syntax in the option may be a simplification, the principle of modifying the StorageCluster spec with a node selector is the correct and necessary step to enforce this placement.

Question 7

Which Portworx CRD object is used to set up essential parameters for a Portworx installation?

Accepted Answer

B

Explanation: The StorageCluster is the primary Custom Resource Definition (CRD) used by the Portworx Operator to deploy and manage a Portworx cluster. This object's specification (spec) contains all the essential parameters for the installation, including the Portworx image version, storage device configurations, network interfaces, environment variables, and other cluster-wide settings. Administrators define the desired state of the Portworx installation within this single CRD object, and the Operator works to reconcile the cluster to match this state.

Question 8

What is the purpose of setting a defragmentation schedule in Portworx?

Accepted Answer

A

Explanation: Portworx defragmentation is an I/O-intensive operation designed to reclaim space and improve the performance of volumes. Because of its resource-intensive nature, it can impact the performance of active applications. By setting a defragmentation schedule, administrators can automate this task to run during periods of low cluster workload, such as nights or weekends. This ensures that the performance benefits of defragmentation are achieved without negatively affecting production services during peak hours.

Question 9

A Portworx administrator wants to create a storage class that can be used to create volumes with the
following characteristics:
• Encrypted volume
• Two replicas
Which definition should the administrator use?

Accepted Answer

C

Explanation: To create a Portworx volume that is both encrypted and has two replicas using a Kubernetes StorageClass, the correct parameters must be specified. The repl: "2" parameter correctly sets the volume's replication factor to two. The secure: "true" parameter is the specific Portworx directive used within a StorageClass to enable per-volume encryption. This combination directly fulfills the administrator's requirements for creating volumes with these characteristics.

Question 10

An infrastructure admin wants to restrict installing Portworx on two nodes. What label does the node need to have?

Accepted Answer

B

Explanation: To prevent Portworx from being installed on a specific node, an administrator must apply the px/enabled=false label to that Kubernetes node. The Portworx Operator and DaemonSet are configured with a node affinity rule that actively avoids scheduling Portworx pods on any node carrying this specific label. This is the designated method for explicitly excluding nodes from a Portworx installation, ensuring that the Portworx components are never deployed to them.

Question 11

What is the minimum Stork version required to perform an Application Backup?

Accepted Answer

C

Explanation: The Application Backup feature in Stork, which enables the backup of both application data (PVCs) and its corresponding Kubernetes object configurations (such as Deployments, Services, and ConfigMaps), was introduced in Stork version 2.3. Versions prior to 2.3 only supported snapshotting Portworx volumes without the associated application context. Therefore, 2.3 is the minimum required version to perform an Application Backup.

Question 12

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?

Accepted Answer

A

Explanation: The pxctl cloudsnap backup command is used to initiate a backup of a Portworx volume to a pre-configured cloud location, such as an AWS S3 bucket. Since the administrator has already configured the necessary secrets (credentials), they would reference these credentials using the -cred-id flag followed by the credential's unique identifier when running the backup command. This action creates a "cloudsnap," which is Portworx's term for a backup stored in a cloud object store.

Question 13

After enabling security in Portworx, the pxctl command returns an “access denied” error. What action must be taken to allow pxctl to gain access again?

Accepted Answer

B

Explanation: When Portworx security is enabled, all pxctl commands require an authentication token. Portworx automatically generates a default administrator token and stores it in a Kubernetes secret named px-admin-token. To regain access, the administrator must retrieve this token from the secret and use it to create a new authenticated pxctl context. This context will then be used for all subsequent pxctl commands, providing the necessary authentication to interact with the secured cluster.

Question 14

What is the minimum number of cores needed to run Portworx?

Accepted Answer

C

Explanation: The official Portworx Enterprise documentation specifies the minimum hardware requirements for running a production-grade cluster. For the central processing unit (CPU), a minimum of 4 cores is recommended. This ensures that the node has sufficient computational resources to handle the Portworx services, which manage I/O, data replication, snapshots, and other storage operations, alongside the containerized applications and the Kubernetes agent (kubelet). While Portworx might run on fewer cores in a non-production or test environment, 4 cores is the established baseline for a stable and supported production deployment.

Question 15

What information is included in the Portworx diagnostics bundle (diags)?

Accepted Answer

A

Explanation: The Portworx diagnostics bundle (diags) is a compressed archive used for troubleshooting the Portworx Data Platform. Its primary purpose is to collect system-level information relevant to the Portworx service itself. This includes Portworx-specific logs (often retrieved via journalctl), the output of various pxctl CLI commands to capture the state of the cluster and volumes, and fundamental information about the underlying operating system and hardware environment (e.g., kernel version, memory, CPU, storage devices). This collection provides support engineers with a comprehensive snapshot of the Portworx environment to diagnose issues effectively.

Free Pure Storage Portworx-Enterprise-Professional Actual Exam Questions