- A
StatefulSets support rolling updates but not canary deployments
Why wrong: StatefulSets support rolling updates and can also support partitioned updates (canary-like) using the .spec.updateStrategy.rollingUpdate.partition field.
- B
StatefulSets automatically create a Service for each pod
Why wrong: StatefulSets require a headless Service to be created manually; they do not automatically create services.
- C
StatefulSets cannot use PersistentVolumeClaims
Why wrong: StatefulSets commonly use volumeClaimTemplates to create unique PVCs per pod.
- D
StatefulSets maintain a sticky identity for each pod, including stable hostnames and persistent storage
Each pod in a StatefulSet gets a unique ordinal index and stable hostname, and retains its storage across rescheduling.
CKA Workloads and Scheduling Practice Question
This CKA practice question tests your understanding of workloads and scheduling. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You have a Deployment 'db' with 3 replicas. Each pod writes to a PersistentVolumeClaim (PVC). A StatefulSet is required for stable network identities and ordered pod management. Which of the following is a key characteristic that differentiates a StatefulSet from a Deployment?
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
StatefulSets maintain a sticky identity for each pod, including stable hostnames and persistent storage
Option D is correct because StatefulSets assign each pod a unique, stable network identity (e.g., a hostname derived from the StatefulSet name and ordinal index) and guarantee that each pod's PersistentVolumeClaim is bound to the same PersistentVolume across rescheduling. This ensures that each pod retains its identity and data, which is critical for stateful applications like databases. Deployments, in contrast, treat pods as interchangeable and do not guarantee stable hostnames or persistent storage binding.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
StatefulSets support rolling updates but not canary deployments
Why it's wrong here
StatefulSets support rolling updates and can also support partitioned updates (canary-like) using the .spec.updateStrategy.rollingUpdate.partition field.
- ✗
StatefulSets automatically create a Service for each pod
Why it's wrong here
StatefulSets require a headless Service to be created manually; they do not automatically create services.
- ✗
StatefulSets cannot use PersistentVolumeClaims
Why it's wrong here
StatefulSets commonly use volumeClaimTemplates to create unique PVCs per pod.
- ✓
StatefulSets maintain a sticky identity for each pod, including stable hostnames and persistent storage
Why this is correct
Each pod in a StatefulSet gets a unique ordinal index and stable hostname, and retains its storage across rescheduling.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the automatic creation of a Headless Service (which is required but not automatically created) with the automatic creation of a Service for each pod, leading them to incorrectly select Option B.
Detailed technical explanation
How to think about this question
Under the hood, StatefulSet pods are named with a predictable pattern like `<statefulset-name>-<ordinal>` (e.g., `db-0`, `db-1`, `db-2`), and each pod's hostname is set to this name via the `hostname` field in the pod spec. The stable storage is achieved through `volumeClaimTemplates`, which generate a separate PVC for each pod, and the PVC is bound to a PersistentVolume using a `selector` or dynamic provisioning. In a real-world scenario, a Cassandra cluster using a StatefulSet ensures that each node retains its data and identity even after a pod is deleted and recreated, preventing data loss and maintaining cluster membership.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CKA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Workloads and Scheduling — study guide chapter
Learn the concepts, then practise the questions
- →
Workloads and Scheduling practice questions
Targeted practice on this topic area only
- →
All CKA questions
1,005 questions across all exam domains
- →
Certified Kubernetes Administrator CKA study guide
Full concept coverage aligned to exam objectives
- →
CKA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CKA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cluster Architecture, Installation and Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation and Configuration.
Services and Networking practice questions
Practise CKA questions linked to Services and Networking.
Workloads and Scheduling practice questions
Practise CKA questions linked to Workloads and Scheduling.
Storage practice questions
Practise CKA questions linked to Storage.
Troubleshooting practice questions
Practise CKA questions linked to Troubleshooting.
Cluster Architecture, Installation & Configuration practice questions
Practise CKA questions linked to Cluster Architecture, Installation & Configuration.
Workloads & Scheduling practice questions
Practise CKA questions linked to Workloads & Scheduling.
Services & Networking practice questions
Practise CKA questions linked to Services & Networking.
CKA fundamentals practice questions
Practise CKA questions linked to CKA fundamentals.
CKA scenario practice questions
Practise CKA questions linked to CKA scenario.
CKA troubleshooting practice questions
Practise CKA questions linked to CKA troubleshooting.
Practice this exam
Start a free CKA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CKA question test?
Workloads and Scheduling — This question tests Workloads and Scheduling — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: StatefulSets maintain a sticky identity for each pod, including stable hostnames and persistent storage — Option D is correct because StatefulSets assign each pod a unique, stable network identity (e.g., a hostname derived from the StatefulSet name and ordinal index) and guarantee that each pod's PersistentVolumeClaim is bound to the same PersistentVolume across rescheduling. This ensures that each pod retains its identity and data, which is critical for stateful applications like databases. Deployments, in contrast, treat pods as interchangeable and do not guarantee stable hostnames or persistent storage binding.
What should I do if I get this CKA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.