KCNA Container Orchestration Practice Question
A DevOps engineer wants to deploy a stateful application that requires stable network identities and persistent storage. Which Kubernetes resource is most appropriate?
⚠ Common exam trap
Watch out — candidates often confuse StatefulSet with Deployment, assuming Deployments can handle stateful workloads by adding persistent volumes, but they overlook the critical need for stable network identities and ordered Pod management that only StatefulSet provides.
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
✓
StatefulSet
StatefulSet is the correct choice because it is designed specifically for stateful applications that require stable, unique network identities (via headless Services and ordinal hostnames) and persistent storage (via PersistentVolumeClaims that persist across Pod rescheduling). Unlike Deployments, StatefulSet guarantees ordered, graceful deployment and scaling, which is essential for applications like databases or distributed systems that rely on stable identities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
DaemonSet
Why it's wrong here
A DaemonSet runs one pod per node for node-level functions, giving no stable identity or storage tied to an application instance. It is tempting because it guarantees pod placement across the cluster, and it would be correct for log shippers or monitoring agents, not stateful applications.
- ✓
StatefulSet
Why this is correct
StatefulSet gives each pod a stable, ordinal hostname and its own PersistentVolumeClaim, so replicas keep predictable network identities and storage across restarts and rescheduling. Deployments provide neither guarantee, making them unsuitable for the stable identity and persistence this stateful workload requires.
- ✗
Deployment
Why it's wrong here
Deployments manage stateless pods with ephemeral identities and no per-pod persistent volume binding, so they cannot provide the stable network identity or storage the application requires. They are intended for interchangeable replicas; a StatefulSet is the correct resource when each pod needs its own durable identity and volume.
- ✗
ReplicaSet
Why it's wrong here
A ReplicaSet only maintains a desired count of identical, interchangeable pods; it provides no stable per-pod network identity or persistent volume binding. It is tempting because it does manage pod replicas, and it would be correct for stateless workloads needing availability, not stateful ones.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-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 KCNA 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 KCNA exam.