QuizzesKubernetes: Mastering Rolling Updates and Rollbacks
intermediate
kubernetes

Kubernetes: Mastering Rolling Updates and Rollbacks

Assess your understanding of Kubernetes rolling updates and rollbacks.

18 minutes 12 questions Pass at 70%
Time Limit
18 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

12 questions on Kubernetes: Mastering Rolling Updates and Rollbacks. Work through them here, then start the quiz to answer them and see your score.

  1. 1.What command is used to perform a rolling update in Kubernetes?

    • Akubectl update deployment
    • Bkubectl rollout update
    • Ckubectl apply update
    • Dkubectl set image
  2. 2.Which of the following is NOT a benefit of rolling updates in Kubernetes?

    • AInstantaneous deployment
    • BEasy rollback
    • CZero downtime
    • DGradual traffic shift
  3. 3.In a rolling update, what happens if a new pod fails to become ready?

    • AThe update continues
    • BThe update stops permanently
    • CThe update rolls back
    • DThe update pauses
  4. 4.How can you check the status of a rolling update in Kubernetes?

    • Akubectl get pods
    • Bkubectl rollout status
    • Ckubectl describe deployment
    • Dkubectl check update
  5. 5.What is the default strategy for rolling updates in Kubernetes?

    • ARecreate
    • BBlue/Green
    • CRollingUpdate
    • DCanary
  6. 6.Which command initiates a rollback to a previous deployment version?

    • Akubectl rollout undo
    • Bkubectl revert deployment
    • Ckubectl undo update
    • Dkubectl rollback
  7. 7.What is the purpose of the 'maxUnavailable' parameter in a rolling update?

    • ATo specify the maximum number of pods that can be unavailable during the update
    • BTo set the maximum number of new pods that can be created
    • CTo define the maximum time an update can take
    • DTo limit the number of updates per hour
  8. 8.What does the 'maxSurge' parameter control in a rolling update?

    • AMaximum time for the update
    • BMaximum number of rollbacks allowed
    • CMaximum number of pods that can be unavailable
    • DMaximum number of additional pods that can be scheduled
  9. 9.If a deployment is rolled back, what happens to the replica set of the failed update?

    • AIt is deleted
    • BIt is merged with the new replica set
    • CIt is retained
    • DIt is scaled down to zero
  10. 10.Which Kubernetes object keeps track of deployment history for rollbacks?

    • ADeployment
    • BReplicaSet
    • CPod
    • DConfigMap
  11. 11.How can you limit the number of old replica sets retained for a deployment?

    • AConfigure 'maxHistory' in the deployment
    • BUse 'kubectl set limit'
    • CAdjust 'historyLimit' in the ReplicaSet
    • DSet 'revisionHistoryLimit' in the deployment spec
  12. 12.What is a potential risk of setting 'maxUnavailable' to 100% during a rolling update?

    • AInconsistent state
    • BIncreased deployment time
    • CExcessive resource usage
    • DComplete service downtime