CKAD Application Observability and Maintenance Practice Question
Which field in the container spec controls the time Kubernetes waits after sending SIGTERM before sending SIGKILL during pod shutdown?
⚠ Common exam trap
Test-takers frequently confuse `terminationGracePeriodSeconds` with probe-related fields like `timeoutSeconds` or `periodSeconds`, or with Job-level fields like `activeDeadlineSeconds`, because all involve time-based configuration but serve entirely different purposes in the lifecycle of a Pod.
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
✓
terminationGracePeriodSeconds
`terminationGracePeriodSeconds` is the field in the Pod spec that defines the duration Kubernetes waits after sending SIGTERM to the main process in each container before forcefully sending SIGKILL. This grace period allows the application to perform clean shutdown tasks, such as closing connections or flushing data. The default value is 30 seconds if not specified.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
timeoutSeconds
Why it's wrong here
timeoutSeconds is a probe parameter that specifies the maximum time in seconds allowed for a single liveness, readiness, or startup probe to complete and return a response. It is unrelated to pod shutdown behavior because probes are periodic health checks, not lifecycle termination controls. Setting this value affects how quickly Kubernetes interprets a container as unhealthy, but it has no influence on the grace period before SIGKILL is sent.
- ✗
periodSeconds
Why it's wrong here
periodSeconds controls how frequently a probe is executed, defining the interval between consecutive liveness, readiness, or startup checks. It is a timer for the probe loop, not a shutdown timer, so it cannot delay or extend the termination of a pod. While both periodSeconds and terminationGracePeriodSeconds are measured in seconds, the former is about health monitoring cadence and the latter about pre-kill cleanup time.
- ✓
terminationGracePeriodSeconds
Why this is correct
terminationGracePeriodSeconds is actually a Pod-level field in the pod spec, not a container-level field, and it controls the duration Kubernetes waits after sending SIGTERM to containers before forcefully sending SIGKILL. This grace period gives processes time to save state, close connections, and complete cleanup handlers. After the period elapses, the kubelet forcibly terminates any containers that have not exited, and overriding it on a per-container basis is impossible.
- ✗
activeDeadlineSeconds
Why it's wrong here
activeDeadlineSeconds is a PodSpec field that sets a hard upper bound on the total time a pod is allowed to run, primarily used by batch workloads like Jobs to prevent them from hanging indefinitely. When the deadline is reached, Kubernetes terminates the pod with a failed status, often using a forced kill rather than a graceful shutdown sequence. It does not define how long a pod waits between SIGTERM and SIGKILL; rather, it decides whether the pod may continue running at all.
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.