Recreate update strategy in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens during a Recreate update strategy in Kubernetes?

In Kubernetes, when you use the Recreate update strategy for a Deployment, what is the behavior during an update?

A Kubernetes deletes all existing pods before creating new ones.

B Kubernetes creates new pods first, then deletes old pods after they are ready.

C Kubernetes updates pods one by one without downtime.

D Kubernetes scales up new pods and keeps old pods running indefinitely.

💡 Hint

Think about whether old pods and new pods run at the same time or not.

The Recreate strategy deletes all existing pods before starting new pods, causing downtime but ensuring no two versions run simultaneously.

💻 Command Output

intermediate

Output of Deployment with Recreate strategy during update

Given this Deployment YAML snippet using Recreate strategy, what will be the status of pods during an update?

Kubernetes

strategy:
  type: Recreate

A Old pods and new pods run simultaneously during update.

B Pods are updated one at a time with zero downtime.

C Old pods are terminated before new pods start; no pods run simultaneously.

D New pods start first, then old pods terminate after readiness.

💡 Hint

Recreate means 'remove then create'.

With Recreate, Kubernetes deletes old pods before creating new ones, so no overlap occurs.

❓ Configuration

advanced

Correct YAML for Recreate update strategy

Which YAML snippet correctly configures a Deployment to use the Recreate update strategy?

A

strategy:
  rollingUpdate:
    maxUnavailable: 1

B

strategy:
  type: RollingUpdate

C

updateStrategy:
  type: Recreate

D

strategy:
  type: Recreate

💡 Hint

Look for the correct field name and value for Recreate.

The correct field is strategy.type with value Recreate. Other options are either wrong field names or different strategies.

❓ Troubleshoot

advanced

Why does a Deployment with Recreate strategy cause downtime?

You notice your application becomes unavailable during Deployment updates using the Recreate strategy. Why does this happen?

A Because all old pods are deleted before new pods start, causing downtime.

B Because new pods fail to start due to resource limits.

C Because pods are updated one by one, causing slow rollout.

D Because the Deployment uses RollingUpdate strategy instead.

💡 Hint

Think about pod availability during the update process.

Recreate deletes all old pods before creating new ones, so there is a period with no pods running, causing downtime.

✅ Best Practice

expert

When to prefer Recreate update strategy over RollingUpdate?

In which scenario is using the Recreate update strategy recommended instead of RollingUpdate?

A When zero downtime is critical for the application.

B When the application cannot handle multiple versions running simultaneously.

C When you want to update pods gradually without downtime.

D When you want to scale pods automatically based on load.

💡 Hint

Consider application compatibility with multiple versions running at once.

Recreate is best when running multiple versions simultaneously causes issues, such as with certain databases or stateful apps.