EX280 Storage And Persistent Volumes Practice Test 5 — 15 Questions

Question 1

Which TWO methods can be used to populate data into a newly created PersistentVolumeClaim during provisioning?

Accepted Answer

Referencing an existing PersistentVolumeClaim in the PVC dataSource field for cloning.. PVCs can be populated using a VolumeSnapshot or another PersistentVolumeClaim (volume cloning) as a dataSource.

Answer

Setting volumeMode to Populate in the PVC spec.

Answer

Mounting a container image registry directly via PVC metadata.

Answer

Specifying an emptyDir template in the PVC spec.

Question 2

Which TWO volume types are considered ephemeral storage patterns native to Kubernetes and OpenShift?

Accepted Answer

Generic ephemeral inline volumes. emptyDir and generic ephemeral inline volumes provide ephemeral storage patterns tied to pod lifecycles.

Answer

NFS network shares

Answer

PersistentVolumeClaim

Answer

AWS EBS volumes

Question 3

Which THREE actions occur when a PersistentVolumeClaim with reclaimPolicy: Delete is deleted by a user?

Accepted Answer

The physical storage asset on the storage backend is deleted.. When reclaimPolicy is Delete, the PVC is removed, the PV object is deleted from Kubernetes API, and the physical storage asset is deleted on the backend storage.

Answer

The storage backend archives the data into an immutable snapshot.

Answer

The PV status changes to Released and remains indefinitely.

Question 4

Which TWO characteristics describe StorageClasses in OpenShift?

Accepted Answer

They specify the provisioner plugin responsible for creating volumes.. StorageClasses are cluster-scoped resources that define the provisioner and parameters for dynamic volume creation.

Answer

They store the actual application data files.

Answer

They are namespace-scoped and unique to each project.

Answer

They can only be created by unprivileged developer users.

Question 5

Which THREE items can be inspected using 'oc describe' when troubleshooting a failing storage attachment in OpenShift?

Accepted Answer

The PersistentVolumeClaim (to check binding status and provisioner errors). Describing the Pod, PVC, and PV provides comprehensive event logs and status information regarding volume attachment failures.

Answer

The cluster image registry configuration

Answer

The OAuth client credentials secret

Question 6

Which TWO conditions will prevent a pod from successfully mounting a PersistentVolumeClaim?

Accepted Answer

The PVC is in a Pending state because it failed to bind or provision.. Mismatched access modes and failure of the CSI driver to attach the volume to the node will prevent pod mounting.

Answer

The pod is running in the default project.

Answer

The StorageClass has allowVolumeExpansion set to true.

Answer

The pod namespace has excess CPU limits.

Question 7

Which THREE factors influence whether a pod requesting a storage volume can be successfully scheduled to a specific worker node when using topology-aware storage?

Accepted Answer

Volume accessibility constraints reported by the CSI driver. Topology-aware scheduling considers node topology labels, volume accessibility constraints, and availability zones matching the provisioned PV.

Answer

The cluster OAuth token expiration time

Answer

The number of container image layers in the pod spec

Question 8

An administrator needs to deploy a StorageClass that automatically provisions volumes only when a PersistentVolumeClaim is created and consumed by a Pod. Which StorageClass parameter determines this behavior?

Accepted Answer

volumeBindingMode: WaitForFirstConsumer. The volumeBindingMode parameter in a StorageClass controls when volume binding and dynamic provisioning should occur. Setting it to WaitForFirstConsumer delays volume binding and provisioning until a Pod using the PVC is scheduled.

Answer

reclaimPolicy: Retain

Answer

provisioningMode: Immediate

Answer

allowVolumeExpansion: true

Question 9

An application running in OpenShift requires scratch space that lives and dies strictly with the Pod lifecycle, but needs to be mounted from a high-performance cluster-managed storage backend rather than local ephemeral node storage. Which feature should an administrator configure?

Accepted Answer

Generic ephemeral inline volumes via a volume template in the Pod specification. Generic ephemeral inline volumes allow users to specify a volume template inline within the Pod spec. This creates a dedicated PVC and PV lifecycle directly tied to the Pod lifecycle.

Answer

HostPath volumes mapped to a local directory on the worker node

Answer

A standard dynamically provisioned PVC with reclaimPolicy set to Delete

Answer

emptyDir with medium: Memory

Question 10

A cluster administrator has deleted a PersistentVolumeClaim, but the underlying PersistentVolume still exists in the cluster with a Released status and its data remains intact on the storage backend. What is the most likely cause of this behavior?

Accepted Answer

The persistentVolumeReclaimPolicy of the PersistentVolume was set to Retain.. The persistentVolumeReclaimPolicy of the PersistentVolume was set to Retain. When a PVC is deleted, Retain policy transitions the PV to Released rather than deleting or recycling the underlying storage asset.

Answer

The StorageClass associated with the PV has allowVolumeExpansion set to false.

Answer

The volume access mode was configured as ReadWriteMany instead of ReadWriteOnce.

Answer

The PVC was protected by a finalizer that prevented immediate deletion.

Question 11

An OpenShift administrator needs to allow users to expand the storage capacity of existing PersistentVolumeClaims without restarting their applications. Which action must be taken first to enable this capability?

Accepted Answer

Edit the StorageClass to set allowVolumeExpansion: true.. To allow PVC expansion, the associated StorageClass must have the allowVolumeExpansion field set to true.

Answer

Restart the csi-provisioner controller deployment in the openshift-cluster-storage-operator namespace.

Answer

Add the expansion-enabled annotation directly to each active Pod object.

Answer

Convert all existing static PersistentVolumes into dynamically provisioned volumes.

Question 12

A cluster administrator has created a VolumeSnapshotClass and a VolumeSnapshot object targeting an active PVC. However, the VolumeSnapshot status never shows ready to use, and the underlying storage provider logs indicate snapshot creation failed due to missing cluster permissions. Which core OpenShift operator is primarily responsible for managing volume snapshot controllers and CRDs in OpenShift 4.14?

Accepted Answer

The Cluster Storage Operator. The OpenShift Storage Operator or specialized CSI operator handles deployment of the snapshot controller, but the cluster-storage-operator or ODF operator manages the storage stack components. Specifically, snapshot validation and controller logic are typically driven by the external snapshot controller deployed via the Cluster Storage Operator or CSI addon operator.

Answer

The Ingress Operator

Answer

The Authentication Operator

Answer

The Machine Config Operator

Question 13

An application pod requires concurrent read and write access to the same storage volume from multiple worker nodes simultaneously. Which access mode must be specified in the PersistentVolumeClaim to satisfy this requirement?

Accepted Answer

ReadWriteMany. ReadWriteMany (RWX) allows the volume to be mounted as read-write by multiple nodes simultaneously.

Answer

ReadWriteOnce

Answer

ReadOnlyMany

Answer

WriteOncePod

Question 14

A developer needs to restore a previously captured VolumeSnapshot into a new PersistentVolumeClaim to revert application state. What key field must be specified in the new PVC definition to initiate the restore operation from the snapshot?

Accepted Answer

spec.dataSource referencing the VolumeSnapshot. To restore from a VolumeSnapshot, the dataSource or dataSourceRef field within the PVC spec must reference the target VolumeSnapshot object.

Answer

metadata.annotations['snapshot.storage.kubernetes.io/restore']

Answer

spec.resources.requests.storage matching the exact snapshot block ID

Answer

spec.volumeName matching the UUID of the snapshot storage backend

Question 15

An administrator is troubleshooting a storage performance issue on an OpenShift cluster using Container Storage Interface (CSI) drivers. Which THREE actions or diagnostic commands are effective for investigating CSI driver health and provisioner issues? (Choose THREE)

Accepted Answer

Verify the CSI driver configuration by checking the CSIDriver and CSINode cluster resources.. To troubleshoot CSI drivers, administrators should examine logs of the CSI provisioner and attacher pods, inspect StorageClass definitions, and check PersistentVolumeClaim events. Examining systemctl on nodes or editing container runtimes directly does not target CSI control plane logic.

Answer

Modify the kubelet configuration file on control plane nodes to increase storage timeout values.

Answer

Run systemctl restart csi-driver on every worker node to force reconnection to the storage array.