CKA Workload Management and Scheduling Flashcards

What is the primary use case for a DaemonSet in Kubernetes?

Answer: Ensuring exactly one copy of a Pod runs on every (or selected) node

A DaemonSet guarantees that a Pod replica runs on each eligible node, making it ideal for node-level agents like log collectors or monitoring daemons.

Which workload type provides stable network identities and ordered, graceful deployment for stateful applications?

Answer: StatefulSet

A StatefulSet gives each Pod a persistent, stable hostname and ordinal index, and manages ordered startup and shutdown for stateful apps like databases.

What Kubernetes object should you use to run a task that executes to completion and then stops?

Answer: Job

A Job creates one or more Pods to run a task to completion, tracks successes, and stops creating new Pods once the desired completions are reached.

In a StatefulSet, what naming convention are Pod identities given?

Answer: Sequential ordinal suffixes (e.g., web-0, web-1, web-2)

StatefulSet Pods receive names combining the StatefulSet name and an ordinal index (0, 1, 2...), providing stable, predictable identities across restarts.

What happens to a Job's completed Pods by default after the Job finishes?

Answer: They remain in Completed state so their logs can be inspected

Completed Pods from a Job are retained in a Completed state by default, allowing administrators to retrieve logs, until the Job or Pods are manually deleted.

What field in a Job spec controls the maximum number of times a failed Pod will be retried before the Job is marked as failed?

Answer: spec.backoffLimit

The `backoffLimit` field sets the number of retries before a Job is declared failed, with an exponential back-off between each retry.