Certified Kubernetes Application Developer (CKAD) Practice Test

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Certified Kubernetes Application Developer (CKAD) Exam. Gain confidence with flashcards and multiple-choice questions, complete with hints and explanations. Achieve your certification with ease!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


How do you set the maximum number of failures for a probe in Kubernetes?

  1. By adjusting the successThreshold property

  2. By modifying the failThreshold property

  3. By using the maxFailures property under the probe

  4. By changing the failureThreshold property

The correct answer is: By changing the failureThreshold property

The correct approach to set the maximum number of failures for a probe in Kubernetes is by modifying the failureThreshold property. This property specifically defines the minimum consecutive failures for the probe to be considered failed. It allows you to specify how many times a pod must fail the probe before Kubernetes takes action, such as restarting the container or marking the pod as unhealthy. Understanding the function of failureThreshold is crucial because it directly impacts the responsiveness of the system in terms of detecting and responding to issues with pods. If this value is set too low, it could lead to unnecessary restarts, while setting it too high might delay the detection of a real problem, potentially affecting application reliability. In contrast, adjusting the successThreshold property pertains to readiness probes and defines how many consecutive successful probes must occur before a pod is considered ready. The maxFailures property does not exist in the Kubernetes probe specifications, making it an invalid option in this context. The failureThreshold property, as mentioned, is the actual attribute used for configuring how many times a failure must occur before acknowledging that there is a problem with the pod.