CKA Domain 4: Storage (10%) - Complete Study Guide 2026

What Domain 4 Storage Actually Tests

Storage sits at 10% of the CKA Certification exam weight, making it the second-smallest domain behind Workloads & Scheduling. That weight translates to approximately two or three performance-based tasks in a two-hour exam window. Do not let the low percentage fool you - these tasks are highly deterministic. Either you produce a correctly bound PersistentVolumeClaim or you do not. Partial credit is possible per task, but a misconfigured access mode or wrong reclaim policy can forfeit a significant portion of available points quickly.

The domain tests three interconnected competencies: understanding how Kubernetes abstracts storage through the PersistentVolume subsystem, knowing how StorageClasses enable dynamic provisioning, and being able to configure workloads (Pods and Deployments) to consume storage correctly. If you have read the CKA Exam Domains 2026: Complete Guide to All 5 Content Areas, you will recognize that Storage is the most self-contained domain on the entire exam - its tasks rarely overlap with networking or scheduling complexity, which means a focused preparation sprint can lock in most of the available points.

Core Storage Concepts You Must Master

Kubernetes storage is built on a deliberate abstraction chain. Administrators provision storage capacity (PersistentVolumes); developers claim it (PersistentVolumeClaims); StorageClasses bridge the two for dynamic workflows. The CKA exam tests all three layers - and expects you to move between them confidently under exam pressure.

The PersistentVolume Subsystem

A PersistentVolume (PV) is a cluster-scoped resource that represents a piece of actual storage - whether NFS, a cloud block device, a local disk, or an in-cluster hostPath. PVs exist independently of any individual Pod, which is the fundamental difference from an emptyDir or configMap volume. The CKA expects you to understand:

• How PVs are created manually (static provisioning) versus generated automatically by a provisioner (dynamic provisioning)
• The capacity field and how it interacts with claim requests
• The accessModes field and its three values
• The persistentVolumeReclaimPolicy and its impact on data lifecycle
• The volumeMode field (Filesystem vs Block)

Access Modes - A Frequent Exam Differentiator

Access modes are one of the most commonly misapplied concepts in Domain 4 exam tasks. The three modes are:

The exam task will often specify an access mode explicitly. If you provision a PV with ReadWriteOnce but the task calls for ReadWriteMany, the PVC will not bind. That is a zero-score outcome for that task. Memorize abbreviations - RWO, ROX, RWX - because exam tasks use both the full name and the short form in YAML.

Persistent Volumes and Persistent Volume Claims

The binding relationship between a PV and a PVC is central to every storage task on the CKA. Binding is automatic once Kubernetes finds a PV that satisfies a PVC's requirements. The matching algorithm checks: capacity (PV must be >= PVC request), access modes (must overlap), storageClassName (must match or both must be empty), selector labels if present, and volumeMode.

Writing PV and PVC YAML Under Exam Conditions

You will not have time to draft PV and PVC manifests from scratch on exam day. Your workflow should be: locate the correct documentation page in the Kubernetes docs (the exam is open-resource to approved materials inside the exam VM), copy the minimal example, and modify it surgically. Practice this flow repeatedly - knowing exactly which doc page contains a working PV/PVC example is worth minutes of time.

A minimal hostPath PV for exam practice looks like this:

• apiVersion: v1
• kind: PersistentVolume
• Key fields: metadata.name, spec.capacity.storage, spec.accessModes, spec.persistentVolumeReclaimPolicy, spec.storageClassName, and a backend stanza (e.g., spec.hostPath.path)

A corresponding PVC must match storageClassName, request a storage amount no greater than the PV capacity, and list an access mode the PV supports. After applying both manifests, immediately run kubectl get pv,pvc and confirm both show STATUS Bound. If a PVC shows Pending, the binding failed - diagnose before moving on.

Reclaim Policies

The persistentVolumeReclaimPolicy determines what happens to the underlying storage when a PVC is deleted. The CKA tests three values:

• Retain - PV moves to Released state; data is preserved; manual reclamation required
• Delete - PV and the underlying storage asset are deleted automatically (common with dynamic provisioning)
• Recycle - deprecated; basic scrub then made available again (rarely appears in current exam versions)

Exam tasks will often specify a reclaim policy. Setting the wrong policy will not prevent binding but will affect scoring if the evaluator checks the PV spec directly.

Storage Classes and Dynamic Provisioning

StorageClasses allow Kubernetes to provision PersistentVolumes on demand, without an administrator pre-creating them. When a PVC references a StorageClass by name, the configured provisioner creates a matching PV and binds it automatically. This is how most production clusters operate, and it is consistently tested in Domain 4.

A common exam task pattern: you are given a cluster with an existing provisioner and asked to create a StorageClass, then create a PVC that uses it, and finally mount that PVC into a Pod. The entire chain must work end-to-end for full credit.

Volume Types and Configuration Patterns

Beyond the PV subsystem, Domain 4 expects candidates to configure workloads with several volume types directly in Pod specs. These do not always involve PVCs - some volumes are ephemeral and declared inline.

emptyDir

An emptyDir volume is created when a Pod is assigned to a node and deleted when the Pod is removed. It is used for scratch space, caching, or sharing files between containers in the same Pod. Exam tasks may ask you to add an emptyDir volume to a multi-container Pod so that a sidecar container can write logs that the main container reads.

configMap and secret Volumes

ConfigMaps and Secrets can be mounted as volumes, projecting their keys as files in a directory. You must know the difference between mounting the entire ConfigMap and projecting specific keys. This overlaps with Domain 2 (Workloads & Scheduling), but storage-focused tasks may specifically ask you to mount a Secret as a volume rather than inject it as environment variables.

hostPath

hostPath mounts a directory from the node's filesystem into the Pod. It is frequently used in CKA lab environments because most exam clusters do not have cloud-backed storage. Know its security implications and how to configure it in both Pod specs and PersistentVolume definitions.

Projected Volumes

A projected volume combines multiple volume sources (ServiceAccountToken, ConfigMap, Secret, DownwardAPI) into a single mount point. While less commonly the direct subject of a storage task, you may encounter it when troubleshooting - which connects to Domain 5. For the broader exam picture, see the CKA Domain 2: Workloads & Scheduling (15%) - Complete Study Guide 2026 for coverage of how volumes intersect with Pod configuration.

What Exam Tasks Look Like in Practice

The CKA delivers 15-20 performance-based tasks across a two-hour window. You are working entirely from a Linux command line inside a browser-based terminal. No graphical interfaces, no autocomplete beyond what kubectl provides. Tasks are weighted individually, and partial credit is possible. For a deeper look at difficulty across all domains, the How Hard Is the CKA Exam? Complete Difficulty Guide 2026 provides useful context.

Typical Domain 4 task structures include:

1. Create a PersistentVolume and PersistentVolumeClaim with specific parameters - you receive a table of required values (name, capacity, access mode, reclaim policy, storageClassName, backend type) and must produce two bound resources
2. Mount a PVC into an existing Deployment - you must edit a running Deployment to add a volume and a volumeMount, then verify the Pod restarts and mounts correctly
3. Create a StorageClass and use it in a PVC - you define a StorageClass with a given provisioner and binding mode, then create a PVC referencing it
4. Resize a PersistentVolumeClaim - if the StorageClass supports volume expansion (allowVolumeExpansion: true), edit the PVC's storage request upward and confirm the resize is accepted

How to Allocate Study Time for Domain 4

Given that Storage is 10% of the exam, it should not dominate your preparation schedule - but it should receive focused, hands-on practice because the tasks are highly reproducible. If you are following a structured preparation plan like the one in the CKA Study Guide 2026: How to Pass on Your First Attempt, dedicate a concentrated block of two to three days specifically to Storage after you have covered Cluster Architecture and Workloads.

The two Killer.sh simulator attempts included with your exam purchase are valuable for stress-testing your storage knowledge under realistic conditions. Save at least one attempt for the final week before your scheduled exam date.

Common Mistakes That Cost Points

Based on the structure of the domain and how binding logic works, several errors consistently prevent full task credit:

• storageClassName mismatch - PV has storageClassName: manual; PVC has storageClassName: "". They will not bind. Always verify both sides use identical values.
• Forgetting to add the volumeMount after adding the volume - adding a volume to a Pod spec without a corresponding volumeMounts entry in the container spec is a complete miss. Both must exist.
• Setting capacity on the PVC higher than the PV - Kubernetes will not bind a PVC that requests more storage than the PV offers. Keep the PVC request equal to or less than the PV capacity.
• Wrong namespace for PVCs - PVs are cluster-scoped, but PVCs are namespace-scoped. If the task specifies a namespace, create the PVC in that namespace. Binding a PV to a PVC in the wrong namespace means the Pod cannot find it.
• Not switching kubectl context - The CKA exam uses multiple clusters. Always run the context-switch command provided at the top of each task before starting work. A correctly configured storage object in the wrong cluster scores zero.

For perspective on where Storage fits in your overall preparation investment, reviewing the full domain breakdown at CKA Exam Domains 2026: Complete Guide to All 5 Content Areas is worthwhile - Troubleshooting at 30% deserves the most clock time, but Storage's deterministic nature means you can lock in most of its points with a shorter focused effort. You can also practice full-length exams at the CKA Exam Prep practice test site to gauge your readiness across all five domains simultaneously.

If you are evaluating whether the certification investment makes sense financially, the CKA Certification Cost 2026: Complete Pricing Breakdown covers the $445 exam fee structure, the included free retake, and the two Killer.sh simulator attempts in detail.

Frequently Asked Questions