Which scenario best fits the use of StatefulSets?

Which scenario best fits the use of StatefulSets?

• A. Stateless front-end services that scale independently
• B. Batch jobs that run to completion
• C. Stateful applications requiring stable network IDs and storage
• D. DaemonSets that run on every node

Answer: (C)

StatefulSets are designed for workloads that need stable, unique network identities and durable storage across restarts. Each pod in a StatefulSet gets a predictable, fixed hostname (for example, appname-0, appname-1) that remains the same even if the pod is rescheduled. In addition, StatefulSets create per-pod storage that persists beyond the life of any single pod via volume claims, so data survives restarts and rescheduling. This combination is essential for stateful applications like databases or distributed services that must be reliably located by a stable name and must preserve data locally. That makes the scenario involving a stateful application requiring stable network IDs and storage the best fit for a StatefulSet. It’s worth noting that stateless front-end services, which can scale with Deployments, do not need stable identities or persistent storage. Batch jobs that run to completion are better modeled by Jobs, and per-node tasks that must run on every node are suited to DaemonSets.

StatefulSets are designed for workloads that need stable, unique network identities and durable storage across restarts. Each pod in a StatefulSet gets a predictable, fixed hostname (for example, appname-0, appname-1) that remains the same even if the pod is rescheduled. In addition, StatefulSets create per-pod storage that persists beyond the life of any single pod via volume claims, so data survives restarts and rescheduling. This combination is essential for stateful applications like databases or distributed services that must be reliably located by a stable name and must preserve data locally.

That makes the scenario involving a stateful application requiring stable network IDs and storage the best fit for a StatefulSet. It’s worth noting that stateless front-end services, which can scale with Deployments, do not need stable identities or persistent storage. Batch jobs that run to completion are better modeled by Jobs, and per-node tasks that must run on every node are suited to DaemonSets.