CKA Storage Practice Test 4 — 15 Questions

Question 1

Which TWO of the following are valid access modes for a PersistentVolume in Kubernetes? (Select two.)

Accepted Answer

ReadWriteOnce. (ReadWriteOnce) is correct because it is one of the three standard access modes defined in the Kubernetes PersistentVolume specification. ReadWriteOnce allows the volume to be mounted as read-write by a single node, which is the most common mode for stateful workloads like databases.

Answer

WriteMany

Answer

ReadOnlySingle

Answer

ReadWriteOncePerNode

Question 2

Which THREE of the following are valid ways to provide storage to a pod in Kubernetes? (Select three.)

Accepted Answer

hostPath. hostPath is a valid volume type that mounts a file or directory from the host node's filesystem into a pod. It is commonly used for accessing node-level resources like Docker sockets or log directories, but it is not suitable for production due to lack of portability across nodes.

Answer

secret

Answer

configMap

Question 3

Which TWO of the following statements about StorageClass are correct? (Select two.)

Accepted Answer

A StorageClass can be used for dynamic provisioning of PersistentVolumes.. A StorageClass is the primary mechanism for dynamic provisioning in Kubernetes. When a PVC requests storage without a specific PV, the cluster uses the StorageClass's provisioner (e.g., kubernetes.io/aws-ebs, csi-hostpath) to automatically create a new PersistentVolume that matches the PVC's requirements. This eliminates the need for an administrator to pre-provision PVs manually.

Answer

A StorageClass must have a provisioner field set to 'kubernetes.io/no-provisioner' to use static provisioning.

Answer

A StorageClass is a namespaced resource.

Answer

The reclaimPolicy in a StorageClass defaults to Retain.

Question 4

Which command creates a PersistentVolume named 'pv-data' that uses a hostPath volume located at '/mnt/data' with a storage capacity of 10Gi and access mode ReadWriteOnce?

Accepted Answer

kubectl apply -f pv.yaml. Because Kubernetes does not support creating PersistentVolumes imperatively via `kubectl create pv`, you must define the PV in a YAML file and create it using either `kubectl apply -f ` or `kubectl create -f `. To avoid having two correct options, Option D has been changed to a common syntax error: forgetting the `-f` flag (`kubectl create pv.yaml`). This leaves Option B as the only correct command.

Answer

kubectl create pv pv-data --capacity=10Gi --access-modes=ReadWriteOnce --hostpath=/mnt/data

Answer

kubectl run pv-data --image=nginx --hostpath=/mnt/data

Answer

kubectl create -f pv.yaml

Question 5

A StatefulSet named 'web' uses volumeClaimTemplates to create a PVC named 'data' with storage class 'ssd'. The StatefulSet has 3 replicas. After scaling down to 2 replicas, what happens to the PVC of the third pod (web-2)?

Accepted Answer

The PVC remains and must be manually deleted if not needed. When a StatefulSet is scaled down, the associated pods are terminated, but the PVCs created via volumeClaimTemplates are not automatically deleted. This is by design to prevent accidental data loss, as the PVCs may contain stateful data that should persist even if the pod is removed. Therefore, the PVC for web-2 remains in the cluster and must be manually deleted if it is no longer needed.

Answer

The PVC is detached but not deleted

Answer

The PVC's reclaim policy determines its fate

Answer

The PVC is automatically deleted along with the pod

Question 6

An administrator creates a PersistentVolume named 'pv-nfs' with a reclaim policy of 'Retain'. After a user deletes the PVC bound to this PV, what state does the PV enter?

Accepted Answer

Released. When a PVC bound to a PV with a reclaim policy of 'Retain' is deleted, the PV does not automatically become available for reuse. Instead, it enters the 'Released' state, indicating that the volume's data is still intact but the PV is no longer bound to a claim. The administrator must manually intervene to reclaim or delete the underlying storage before the PV can be made available again.

Answer

Available

Answer

Failed

Answer

Bound

Question 7

A pod uses a PersistentVolumeClaim named 'claim-log'. The PVC is pending. You run 'kubectl describe pvc claim-log' and see the event: 'waiting for a volume to be created, either by external provisioner or manually'. The StorageClass 'standard' has provisioner: 'kubernetes.io/no-provisioner'. What is the most likely cause?

Accepted Answer

The StorageClass 'standard' does not have a dynamic provisioner configured. The StorageClass 'standard' has provisioner: 'kubernetes.io/no-provisioner', which is a static provisioner that does not automatically create volumes. Since the PVC is pending with the event 'waiting for a volume to be created, either by external provisioner or manually', it indicates that no dynamic provisioner is available to automatically provision a PersistentVolume (PV) for the PVC. The most likely cause is that the StorageClass lacks a dynamic provisioner, so a PV must be manually created or an external provisioner must be configured.

Answer

The StorageClass is missing the volumeBindingMode

Answer

The PVC's access mode is incompatible with the StorageClass

Answer

The PVC requires a larger storage size than any available PV

Question 8

Which CSI driver feature must be supported by the driver to allow expanding a PVC while the pod using it is still running?

Accepted Answer

Volume expansion. To allow expanding a PVC while the pod is still running, the CSI driver must support volume expansion (e.g., ControllerExpandVolume and NodeExpandVolume RPCs). The in-use expansion capability is also controlled by the Kubernetes feature gate `ExpandInUsePersistentVolumes`, but that is not a CSI driver feature. Therefore, the correct answer is 'Volume expansion'.

Answer

Volume attach

Answer

Mount options

Answer

ExpandInUsePersistentVolume

Question 9

Which volume type is typically used to share configuration data with a pod as files, where the data is stored in the cluster as a resource?

Accepted Answer

configMap. A ConfigMap volume mounts ConfigMap data as files inside the pod.

Answer

secret

Answer

hostPath

Answer

emptyDir

Question 10

A pod uses a PVC with access mode RWO. The pod is scheduled on node A. You want to schedule another pod on node B that uses the same PVC. What will happen?

Accepted Answer

The second pod will be stuck in ContainerCreating state until the first pod releases the volume. A PVC with access mode RWO (ReadWriteOnce) can only be mounted as a block device or filesystem by a single node at a time. When the first pod on node A has the volume attached, the second pod on node B cannot attach the same volume because the underlying storage (e.g., an AWS EBS volume or GCE Persistent Disk) does not support multi-node attachment. The second pod will remain in ContainerCreating state with a 'Multi-Attach error' until the first pod releases the volume (e.g., by being deleted or rescheduled).

Answer

Both pods will mount the volume and share it without issues

Answer

The second pod will successfully mount the volume as read-only

Answer

The first pod will be evicted to allow the second pod to use the volume

Question 11

A developer creates a PVC with storageClassName: "" (empty string). What does this mean?

Accepted Answer

The PVC will only bind to PVs that also have storageClassName: "". When a PVC has `storageClassName: ""` (empty string), it explicitly disables dynamic provisioning and static binding to a PV that also has `storageClassName: ""`. This means the PVC will only bind to a pre-existing PV that has its `storageClassName` set to an empty string, bypassing any default StorageClass. It does not remain pending indefinitely, nor does it use or trigger the default StorageClass.

Answer

The PVC will remain pending indefinitely

Answer

The PVC will use the default StorageClass

Answer

The PVC will be dynamically provisioned using the cluster's default StorageClass

Question 12

Which resource type is used to define a template for dynamically provisioning PersistentVolumes?

Accepted Answer

StorageClass. StorageClass is the correct resource because it defines a 'class' of storage with a provisioner (e.g., kubernetes.io/aws-ebs) and parameters that Kubernetes uses to dynamically create PersistentVolumes when a PersistentVolumeClaim requests storage. Without a StorageClass, dynamic provisioning cannot occur, as the cluster needs a template to know which storage backend to use and how to configure it.

Answer

PersistentVolume

Answer

VolumeAttachment

Answer

PersistentVolumeClaim

Question 13

Which THREE of the following are correct about using a hostPath volume in Kubernetes? (Select THREE)

Accepted Answer

It is recommended for testing and development only. HostPath volumes are tied to a specific node's filesystem, making them unsuitable for production environments where pods may be rescheduled to different nodes. The Kubernetes documentation explicitly recommends hostPath volumes for testing and development only, as they lack the portability and reliability required for production workloads.

Answer

It supports ReadWriteMany access mode across multiple nodes

Answer

It is suitable for production workloads that require persistence across nodes

Question 14

Which TWO of the following are required fields in a PersistentVolumeClaim spec? (Select TWO)

Accepted Answer

accessModes. `accessModes` is a required field in a PersistentVolumeClaim (PVC) spec. It defines how the volume can be mounted by pods (e.g., ReadWriteOnce, ReadOnlyMany, ReadWriteMany) and must match the access modes of the underlying PersistentVolume (PV) for binding to succeed. Without specifying accessModes, the PVC cannot be created.

Answer

storageClassName

Answer

selector

Answer

volumeMode

Question 15

A pod is using a PersistentVolumeClaim (PVC) named 'mypvc' which is bound to a PersistentVolume (PV) with reclaim policy 'Retain'. The pod is deleted and then the PVC is deleted. What happens to the PV?

Accepted Answer

The PV remains but is in 'Released' state.. When a PVC is deleted, the associated PV with a 'Retain' reclaim policy is not automatically deleted or recycled. Instead, the PV transitions to a 'Released' state, indicating that its data is preserved but it is no longer bound to a PVC. The PV remains in the cluster until an administrator manually reclaims it by removing the claimRef or deleting the PV.

Answer

The PV is automatically deleted.

Answer

The PV is immediately bound to another PVC.

Answer

The PV is recycled for reuse.