Rolling Updates — Certified Kubernetes App Developer (CKAD) Practice Questions
Rolling updates are the default update strategy for Kubernetes Deployments, replacing old pods with new ones incrementally rather than all at once to maintain application availability during a release. The Deployment controller creates new pods from the updated template in controlled waves while terminating old pods, respecting the maxSurge and maxUnavailable constraints throughout the process. CKAD candidates must be able to trigger, monitor, pause, resume, and roll back rolling updates using kubectl, as these operations represent real-world deployment workflows the exam simulates.
Free questions on rolling updates
A Deployment's rolling update strategy allows updating Pods gradually. What two fields control this behavior?
Free question · medium · full answer + explanation
More rolling updates questions in the full bank
- What is the purpose of spec.minReadySeconds in a Deployment? Unlock answer & explanation →
- How does Kubernetes handle rolling updates by default? Unlock answer & explanation →
- How does PDB coordinate with deployment strategies? Unlock answer & explanation →