CKAD Application Observability and Maintenance Practice Question
Which THREE of the following are valid fields for configuring a probe in Kubernetes? (Select 3)
⚠ Common exam trap
It's easy for candidates to confuse `intervalSeconds` with `periodSeconds` and `retrySeconds` with `failureThreshold`, as the incorrect options sound plausible but do not exist in the Kubernetes API specification.
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 configuration (e.g., livenessProbe, readinessProbe, startupProbe). It defines the number of seconds after the container has started before the probe is initiated, allowing the application time to initialize before health checks begin.
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 this is correct
The field specifies the waiting period after the container starts before the kubelet begins running the probe. It is crucial for applications that need time to initialize, such as loading configuration or establishing connections. Without it, probes might fail prematurely, causing unnecessary restarts. The field is part of the probe specification along with periodSeconds, timeoutSeconds, successThreshold, and failureThreshold.
- ✗
retrySeconds
Why it's wrong here
This is not a valid field in Kubernetes probe configuration. The concept of retrying a probe is handled by failureThreshold, which defines the number of consecutive failures needed to mark the probe as failed. There is no "retrySeconds" field; instead, the periodSeconds controls the interval between probe attempts. Trying to set retrySeconds would result in a schema validation error.
- ✗
intervalSeconds
Why it's wrong here
The correct field name is periodSeconds, not intervalSeconds. periodSeconds defines how often the probe is executed, with a default of 10 seconds and a minimum of 1 second. Using intervalSeconds would be invalid because it doesn't exist in the probe spec, causing a YAML validation failure.
- ✓
periodSeconds
Why this is correct
This field sets the frequency of the probe execution, specifying the interval in seconds between consecutive probes. It defaults to 10 seconds and must be at least 1. The period begins after the initialDelaySeconds elapses, and the probe runs repeatedly at this interval until the pod's lifecycle ends. This field works in conjunction with timeoutSeconds to ensure timely health checks.
- ✓
timeoutSeconds
Why this is correct
This field defines the maximum time, in seconds, that the probe waits for a response from the container before considering the probe failed. The default is 1 second, and the value must be greater than 0. If the probe times out, it counts as a failure, which, if consecutive, triggers the failureThreshold and leads to a restart (for liveness) or removal from endpoints (for readiness). Note that the timeout is per probe attempt, not cumulative.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CKAD question from scratch — 826 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.