CKAD Application Observability and Maintenance Practice Question
You have a Deployment with a liveness probe that fails intermittently, causing the pod to restart. You want to reduce the sensitivity of the probe so that it only restarts after 3 consecutive failures. Which probe parameter should you adjust?
⚠ Common exam trap
It's easy for candidates to confuse `failureThreshold` with `periodSeconds`, thinking that reducing the probe frequency (period) will reduce sensitivity, but the correct way to require multiple consecutive failures is to increase the `failureThreshold` value.
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
✓
failureThreshold
The `failureThreshold` parameter defines the number of consecutive probe failures required before Kubernetes considers the probe to have failed and triggers the configured action (e.g., restarting the container). By default, this value is 3, but if it is set lower (e.g., 1), a single failure causes a restart. Increasing `failureThreshold` to 3 (or higher) ensures that the liveness probe only restarts the pod after three consecutive failures, thereby reducing sensitivity to transient issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
initialDelaySeconds
Why it's wrong here
initialDelaySeconds configures how long the kubelet waits after the container starts before executing the first liveness probe. It is meant to give the application time to become ready, but it does not influence how many consecutive probe failures are required to restart the container. Reducing or removing this value only changes when probing begins, not the sensitivity to intermittent failures.
- ✗
periodSeconds
Why it's wrong here
periodSeconds defines the time interval between successive probe executions, determining how frequently the kubelet checks the container's health. While increasing the period would make the probe run less often and potentially delay detection, it does not alter the failureThreshold counter that decides when a restart is triggered. Thus, adjusting this field cannot prevent a flapping probe from eventually reaching the required failure count.
- ✓
failureThreshold
Why this is correct
failureThreshold is the correct parameter to adjust because it specifies the number of consecutive liveness probe failures the kubelet must observe before restarting the container. By increasing this value from its default (often 1 for liveness) to 3, you require multiple failed probes in a row, making the restart decision less sensitive to transient errors. This directly addresses the problem of a probe that fails intermittently without causing immediate container restarts.
- ✗
successThreshold
Why it's wrong here
successThreshold determines how many consecutive successes must occur after a probe failure for the probe to be considered successful again, and for liveness probes Kubernetes requires this value to be 1. It does not affect the number of failures that trigger a restart, nor does it dampen the effect of intermittent failures. Since it only controls the recovery condition, adjusting it would not reduce the restart frequency when the probe occasionally fails.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CKAD question from scratch — 160 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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 CKAD 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 CKAD exam.