Storage Solutions Flashcards
7 cards from real KCNA practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Storage Solutions flashcards as text
In a cloud-native architecture, which pattern best describes using object storage (like S3) instead of block storage for application data?
Answer: Externalizing state to a managed object store accessed via SDK or API
Cloud-native design favors externalized object storage accessed via API/SDK over block storage mounted in pods, enabling better scalability and decoupling.
What is the role of the 'node-driver-registrar' CSI sidecar?
Answer: It registers the CSI driver with the kubelet on each node using the kubelet plugin registration mechanism
The node-driver-registrar sidecar uses the kubelet plugin registration API to make the kubelet aware of the CSI driver on a given node.
Which of the following volume types is most appropriate for sharing temporary data between containers in the same pod?
Answer: emptyDir
emptyDir volumes are created when a pod starts and are shared among all containers in that pod, making them ideal for inter-container scratch space.
A storage administrator wants a PV to only be bound to a specific PVC before it is created. Which mechanism achieves this?
Answer: Pre-populating the claimRef field on the PV with the target PVC details
Pre-setting the claimRef on a PV with the namespace and name of the intended PVC ensures only that PVC can bind to it during static provisioning.
Which Kubernetes feature allows administrators to define storage capacity constraints per topology zone so the scheduler can make better pod placement decisions?
Answer: StorageCapacity API (CSIStorageCapacity objects)
CSIStorageCapacity objects let CSI drivers report available storage capacity per topology zone, enabling the Kubernetes scheduler to factor storage availability into pod placement.
What does the 'ReadWriteOncePod' (RWOP) access mode enforce compared to 'ReadWriteOnce' (RWO)?
Answer: RWOP restricts volume access to a single pod cluster-wide, while RWO allows multiple pods on one node
ReadWriteOncePod guarantees that only a single pod in the entire cluster can mount the volume with read-write access, providing stronger exclusivity than RWO.
Which approach is recommended for migrating from an in-tree volume plugin to its CSI equivalent in Kubernetes?
Answer: Enable the CSIMigration feature gates so existing PV/PVC objects are automatically handled by the CSI driver
CSI Migration feature gates transparently redirect in-tree volume plugin operations to the corresponding CSI driver without requiring users to recreate PVs or PVCs.