CKAD Application Observability and Maintenance Practice Question
Which THREE of the following are valid parameters for a probe?
⚠ Common exam trap
It's easy for candidates to confuse Kubernetes probe parameters with similar concepts from other systems (e.g., retry logic or backoff strategies) and assume `maxRetries` or `backoffSeconds` are valid, when in fact Kubernetes uses `failureThreshold` and fixed-interval polling instead.
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
✓
initialDelaySeconds
`initialDelaySeconds` is a valid field in a Kubernetes probe specification that defines the number of seconds to wait before initiating the first probe after the container starts. This allows the application time to initialize before health checks begin, preventing premature failures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
maxRetries
Why it's wrong here
This is not a valid Kubernetes probe parameter. The probe specification uses `failureThreshold`, which defines how many consecutive failures are required to change the probe state, rather than a `maxRetries` field. This confusion often arises from other health-check systems that implement retry counters, but the kubelet relies solely on the threshold-based mechanism.
- ✓
initialDelaySeconds
Why this is correct
This is a valid parameter in the Kubernetes probe specification. It sets the number of seconds the kubelet waits after the container starts before performing the first probe, giving the application time to initialize. Properly setting this value is critical for liveness probes to avoid restarting containers that are still starting up.
- ✓
timeoutSeconds
Why this is correct
This is a valid probe parameter that specifies the maximum time, in seconds, allowed for each individual probe check to complete. If a probe exceeds this timeout, the kubelet treats that check as failed, and the failure is counted against the `failureThreshold`. This prevents hung or unresponsive applications from blocking the probe loop indefinitely.
- ✗
backoffSeconds
Why it's wrong here
This is not a parameter of the Kubernetes probe definition. There is no `backoffSeconds` field in the probe specification; instead, probes run at a fixed interval governed by `periodSeconds`. The kubelet's restart policy does use exponential backoff (leading to CrashLoopBackOff), but that mechanism is independent of the probe configuration and is not specified within a probe.
- ✓
periodSeconds
Why this is correct
This is a valid probe parameter that controls the frequency of probe execution. It specifies the interval, in seconds, between consecutive probes after the `initialDelaySeconds` period has elapsed. Adjusting this value lets you trade off detection latency against resource usage and API server load, and it applies uniformly to liveness, readiness, and startup probes.
Go deeper
Related to this question
About these practice questions
One of 826 original CKAD practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.