Question 1mediummultiple choice
Read the full Storage explanation →CKA Storage • Complete Question Bank
Complete CKA Storage question bank — all 0 questions with answers and detailed explanations.
You are managing a Kubernetes cluster with 3 worker nodes (node1, node2, node3). A stateful application named 'app-db' uses a StatefulSet with 3 replicas, each requiring a PersistentVolumeClaim (PVC) of 10Gi with access mode ReadWriteOnce. The cluster uses a StorageClass 'fast-ssd' with a CSI driver that provisions volumes on a shared SAN. The StorageClass has reclaim policy 'Delete' and volumeBindingMode 'WaitForFirstConsumer'.
Recently, node1 failed and is unrecoverable. The pod running on node1 (app-db-0) is in 'Pending' state because its PVC is still bound to a PV that exists only on node1's local storage (the CSI driver incorrectly pinned the volume to node1). The other two pods (app-db-1 and app-db-2) are running fine. The application is critical and must be restored as soon as possible. You cannot recover node1.
What is the best course of action to get app-db-0 running again?
apiVersion: v1
kind: Pod
metadata:
name: test-pod
spec:
containers:
- name: test
image: busybox
command: ["sleep", "3600"]
volumeMounts:
- name: cache
mountPath: /cache
volumes:
- name: cache
emptyDir:
medium: MemoryRefer to the exhibit. $ kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pv-data 10Gi RWO Retain Bound default/data-claim manual 5h $ kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-claim Bound pv-data 10Gi RWO manual 5h
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Store a key-value pair
Retrieve value for a key
Create a backup of the datastore
List all etcd cluster members
Check health of etcd endpoints
Drag a concept onto its matching description — or click a concept then click the description.
Update the cluster bootstrap tool
Update the node agent
Evict Pods gracefully before upgrade
Update API server, scheduler, controller-manager
Allow Pods to be scheduled again after upgrade
A cluster administrator creates a PersistentVolume with the following YAML:
apiVersion: v1 kind: PersistentVolume metadata: name: pv-example spec: capacity: storage: 1Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain hostPath: path: /data/pv
A user creates a PersistentVolumeClaim requesting 500Mi with access mode ReadWriteOnce and no storage class. The PVC remains in Pending state. What is the most likely cause?
A cluster administrator creates a StorageClass with the following YAML:
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: fast provisioner: kubernetes.io/aws-ebs parameters: type: gp2 reclaimPolicy: Delete volumeBindingMode: Immediate
A developer creates a PVC using this StorageClass. The PVC is created and remains in Pending state. What is the most likely cause?
A cluster administrator runs the following command to create a PersistentVolumeClaim:
kubectl create pvc mypvc --storage-class=fast --access-modes=ReadWriteOnce --storage=1Gi
However, the PVC is created but remains in Pending state. The StorageClass 'fast' uses provisioner 'kubernetes.io/no-provisioner' (a static provisioner). What is the most likely reason?
An administrator creates a PersistentVolume with the following YAML:
```yaml apiVersion: v1 kind: PersistentVolume metadata: name: pv-example spec: capacity: storage: 5Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Retain hostPath: path: /mnt/data ```
Which of the following is true about this PersistentVolume?
A user creates a PersistentVolumeClaim (PVC) with the following YAML:
```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: myclaim spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi ```
They then run 'kubectl get pvc' and see that the PVC is 'Pending'. Which is the most likely cause?