CKA Application Lifecycle 2

Question 1

A Deployment has 5 replicas and you run `kubectl rollout pause deployment/myapp`. What happens to an in-progress rolling update?

Accepted Answer

The update halts at its current state until resumed

Answer

Pausing a rollout freezes the update mid-progress; new pods already created remain, but no further pod replacements occur until `kubectl rollout resume` is run.

Question 2

Which field in a Deployment spec controls the maximum number of pods that can be unavailable during a rolling update?

Accepted Answer

maxUnavailable

Answer

`maxUnavailable` defines how many pods can be taken down simultaneously during a rolling update, expressed as an absolute number or percentage.

Question 3

You need to update a Deployment's image without triggering a rollout. Which approach achieves this?

Accepted Answer

Edit the Deployment spec and set spec.paused: true first

Answer

Pausing the Deployment before editing the image prevents Kubernetes from starting a rollout; the change is saved but not applied until the Deployment is resumed.

Question 4

A pod's init container exits with code 0. What does Kubernetes do next?

Accepted Answer

Starts the next init container or the main app container

Answer

An exit code of 0 signals success; Kubernetes then starts the next init container in order, or starts the main application containers if all init containers have completed.

Question 5

What is the effect of setting `spec.strategy.type: Recreate` in a Deployment?

Accepted Answer

All existing pods are terminated before new pods are created

Answer

The Recreate strategy terminates all existing pods first, causing downtime, then creates the new version pods — useful when running two versions simultaneously is not acceptable.

(CKA) Certified Kubernetes Administrator Practice Test

(CKA) Certified Kubernetes Administrator Practice Test

CKA Application Lifecycle 2