Courseiva

CKAD Application Observability and Maintenance Practice Question

Which THREE of the following are correct statements about the terminationGracePeriodSeconds field? (Select 3)

⚠ Common exam trap

CNCF often tests the exact default value (30 seconds) and the distinction between SIGTERM (graceful) and SIGKILL (forceful), so candidates must not confuse terminationGracePeriodSeconds with probe settings like readiness or liveness probe timeouts.

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

✓

The default value is 30 seconds

The Kubernetes documentation specifies that the default value for terminationGracePeriodSeconds is 30 seconds. This field is part of the PodSpec and controls the duration between sending SIGTERM to the container and forcefully killing it with SIGKILL. If not set, Kubernetes applies this default to ensure a reasonable window for graceful shutdown.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    The default value is 30 seconds

    Why this is correct

    The `terminationGracePeriodSeconds` field in a Pod spec defaults to 30 seconds when omitted. This value sets how long Kubernetes waits after sending SIGTERM to a container's main process before sending SIGKILL. It is a deliberate default to allow most workloads enough time to shut down cleanly without forcing an immediate hard kill.

  • ✓

    It gives the container time to shut down gracefully after receiving SIGTERM

    Why this is correct

    When Kubernetes begins terminating a Pod, it sends SIGTERM to the main process (PID 1) in each container. The `terminationGracePeriodSeconds` value gives that process a chance to close open connections, finish in-flight requests, flush metrics or logs, and release resources gracefully. If an application traps SIGTERM and exits within the window, the Pod ends cleanly before the timer expires.

  • ✓

    After the grace period expires, the container is forcefully killed with SIGKILL

    Why this is correct

    If a container's main process does not exit on its own after the grace period elapses, the kubelet escalates to SIGKILL. SIGKILL cannot be caught, blocked, or ignored, so the process is abruptly terminated by the kernel. This happens as a hard final step to guarantee the Pod is fully stopped, even if the application is hung or misbehaving.

  • ✗

    The default value is 0 seconds

    Why it's wrong here

    The default value is not 0 seconds; it is 30 seconds. A default of 0 would mean no time is allotted between SIGTERM and the forcible SIGKILL, making graceful shutdown practically impossible because any process that does not exit instantly would be killed. Kubernetes intentionally avoids this by defaulting to 30 seconds to support smooth termination.

  • ✗

    It is used to configure the readiness probe timeout

    Why it's wrong here

    This is incorrect because `terminationGracePeriodSeconds` is a Pod-level setting that controls the shutdown sequence after SIGTERM, whereas readiness probe timeouts are configured via the `timeoutSeconds` field inside a `readinessProbe` spec. The former is about how long to wait for graceful termination, while the latter is about how long to wait for a probe HTTP request or TCP connection to succeed. They belong to completely different phases of the Pod lifecycle.

About these practice questions

This CKAD question is part of Courseiva's 826-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.