CKAD Application Observability and Maintenance Practice Question
Which TWO parameters can be configured for a probe to control its behavior? (Choose two.)
⚠ Common exam trap
CNCF often tests the distinction between probe parameters and unrelated concepts like retry logic or backoff strategies, leading candidates to confuse fields from other systems (e.g., Spring Boot retry) with Kubernetes probe configuration.
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
✓
timeoutSeconds
`timeoutSeconds` defines the maximum time a probe waits for a response before considering the probe failed. Option E is correct because `initialDelaySeconds` configures the delay before the probe starts after the container starts, allowing the application to initialize. Both are standard fields in the Kubernetes probe specification (liveness, readiness, startup).
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
The `maxRetries` parameter does not exist in the Kubernetes Probe API. The closest concept is `failureThreshold`, which defines how many consecutive probe failures are required for the kubelet to consider the container unhealthy. Each probe is a single HTTP, TCP, or exec check; there is no automatic per-probe retry, as retries are controlled by periodically issuing new probes according to `periodSeconds`.
- ✗
backoffSeconds
Why it's wrong here
Kubernetes Probe configuration does not include a `backoffSeconds` parameter. While the kubelet applies an exponential backoff to container restarts (CrashLoopBackOff), that delay is managed internally by the container runtime and is unrelated to probe execution. Probe timing is strictly governed by `initialDelaySeconds`, `periodSeconds`, `timeoutSeconds`, and thresholds, with no probe-specific backoff mechanism.
- ✗
retryIntervalSeconds
Why it's wrong here
This is not a recognized probe field. The frequency of probe attempts is determined by `periodSeconds`, which tells the kubelet how often to run the probe after the initial delay. There is no separate `retryIntervalSeconds`; if a probe fails or times out, the next check is simply scheduled after the next `periodSeconds` interval, not after an immediate retry.
- ✓
timeoutSeconds
Why this is correct
The `timeoutSeconds` parameter is a valid probe setting that defines the maximum duration (in seconds) allowed for a single probe to complete before it is considered failed. This prevents the kubelet from waiting indefinitely on a hanging check. Setting `timeoutSeconds` too high can delay failure detection, while setting it too low may cause false failures for slow applications.
- ✓
initialDelaySeconds
Why this is correct
The `initialDelaySeconds` parameter is a valid probe setting that tells the kubelet to wait a specified number of seconds after the container's start before executing the first probe. It gives the application time to initialize and listen on its port, reducing the chance of false negatives. This is especially critical for liveness probes, where premature probing can lead to unnecessary container restarts.
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.