- A
Init containers always run before app containers and must complete successfully for the pod to start.
Init containers run sequentially and must finish before app containers start.
- B
A pod with a nodeSelector that does not match any node will be evicted from the cluster.
Why wrong: The pod will remain pending indefinitely.
- C
If a pod with higher priority is pending and there are no resources, it will preempt pods with equal or lower priority.
Why wrong: Priority preemption only preempts pods with lower priority.
- D
Static pods are created by the API server based on a manifest file in the kubelet's manifest directory.
Why wrong: Static pods are created by kubelet, not the API server.
- E
DaemonSet pods are scheduled on all nodes, including nodes that are tainted, as long as the pod tolerates the taint.
DaemonSet pods ignore node unschedulable status and are scheduled on all nodes matching the toleration.
CKA Workloads & Scheduling Practice Question
This CKA practice question tests your understanding of workloads & scheduling. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
Which TWO statements about Kubernetes pod lifecycle and scheduling are correct? (Select two.)
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
Init containers always run before app containers and must complete successfully for the pod to start.
Init containers are specialized containers that run before any app containers in a pod. They must complete successfully (exit with code 0) before the pod's app containers are started. If an init container fails, Kubernetes restarts it until it succeeds, and the pod will not enter the Running phase until all init containers have succeeded. This is defined in the pod spec under `initContainers` and is a core mechanism for setup tasks like waiting for a service or database to be ready.
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.
- ✓
Init containers always run before app containers and must complete successfully for the pod to start.
Why this is correct
Init containers run sequentially and must finish before app containers start.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A pod with a nodeSelector that does not match any node will be evicted from the cluster.
Why it's wrong here
The pod will remain pending indefinitely.
- ✗
If a pod with higher priority is pending and there are no resources, it will preempt pods with equal or lower priority.
Why it's wrong here
Priority preemption only preempts pods with lower priority.
- ✗
Static pods are created by the API server based on a manifest file in the kubelet's manifest directory.
Why it's wrong here
Static pods are created by kubelet, not the API server.
- ✓
DaemonSet pods are scheduled on all nodes, including nodes that are tainted, as long as the pod tolerates the taint.
Why this is correct
DaemonSet pods ignore node unschedulable status and are scheduled on all nodes matching the toleration.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between static pods (kubelet-created) and regular pods (API server-created), and the trap here is that candidates confuse the kubelet's manifest directory with the API server's pod creation mechanism.
Detailed technical explanation
How to think about this question
Init containers can have different resource requests and limits than app containers, and they can use separate container images. A common real-world scenario is using an init container to run a database migration script before the main application starts. Under the hood, the kubelet tracks init container status in the pod's status field, and the pod's `status.phase` remains `Pending` until all init containers have succeeded. If an init container fails, the kubelet restarts it according to the pod's `restartPolicy` (default Always, but for init containers it effectively behaves as OnFailure).
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 & Scheduling — study guide chapter
Learn the concepts, then practise the questions
- →
Workloads & 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 & Scheduling — This question tests Workloads & Scheduling — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Init containers always run before app containers and must complete successfully for the pod to start. — Init containers are specialized containers that run before any app containers in a pod. They must complete successfully (exit with code 0) before the pod's app containers are started. If an init container fails, Kubernetes restarts it until it succeeds, and the pod will not enter the Running phase until all init containers have succeeded. This is defined in the pod spec under `initContainers` and is a core mechanism for setup tasks like waiting for a service or database to be ready.
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 30, 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.