CKA Storage Practice Question
What does the 'volumeMode: Block' setting in a PersistentVolume spec indicate?
⚠ Common exam trap
It's easy for candidates to confuse 'volumeMode: Block' with automatic filesystem formatting or encryption, when in fact it specifically means no filesystem is created and the device is exposed raw to the pod.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The volume will be presented as a raw block device to the pod
Setting 'volumeMode: Block' in a PersistentVolume spec tells Kubernetes to present the volume as a raw block device (e.g., /dev/sdb) inside the pod, rather than mounting a filesystem. This is defined in the Kubernetes PersistentVolume API and is used for applications that need direct access to the underlying storage, such as databases or software that manage their own filesystems.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The volume will be formatted with a filesystem automatically
Why it's wrong here
Setting volumeMode to Block explicitly bypasses the creation of any filesystem on the volume. Unlike the default Filesystem mode, which automatically formats the volume with a filesystem (like ext4 or xfs) before mounting, Block mode presents the storage as a raw, unformatted block device. The application or pod itself must manage any formatting or direct block writes.
- ✗
The volume will have encryption enabled by default
Why it's wrong here
The volumeMode parameter only dictates whether the storage is presented as a filesystem or a raw block device to the container. It does not govern security features such as encryption at rest or in transit. Encryption must be configured separately via the underlying StorageClass parameters, CSI driver configurations, or cloud provider settings.
- ✓
The volume will be presented as a raw block device to the pod
Why this is correct
When volumeMode is set to Block, Kubernetes integrates the volume into the pod as a raw block device without any filesystem layer. This allows high-performance applications, such as databases or custom storage engines, to read and write directly to the block storage. The device is exposed inside the container as a path in the dev filesystem rather than a mounted directory.
- ✗
The volume will be mounted using NFS protocol
Why it's wrong here
Network File System (NFS) is inherently a file-level sharing protocol that requires a Filesystem volume mode to operate correctly within Kubernetes. Raw block mode is incompatible with NFS because block storage requires direct access to sector-level operations, which are typically provided by protocols like iSCSI, Fibre Channel, or local NVMe drives.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
Key term
Volumes
In Kubernetes, a volume is a storage resource that outlives the pod it belongs to, enabling data to persist across container restarts and be shared between containers in the same pod.
About these practice questions
This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.