Answer-first summary for fast verification
Answer: Perform a rolling update with a PodDisruptionBudget of 80%.
The correct approach is to use a rolling update with a PodDisruptionBudget (PDB) of 80%. Rolling updates incrementally replace old pods with new ones, ensuring minimal disruption. A PDB of 80% ensures that at least 80% of pods remain available during the update, limiting the impact if the new revision is faulty. If the new pods fail readiness checks, the rollout pauses, preventing further replacements. This aligns with Google's best practices for safe rollouts. Options involving HorizontalPodAutoscaler (B, D) are less relevant here, as HPA manages scaling based on load, not deployment safety. Converting to a StatefulSet (C, D) is unnecessary unless the app requires stateful characteristics, which isn't mentioned in the scenario.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How can you deploy a new application revision to Google Kubernetes Engine (GKE) in production while minimizing risk if the container fails, following Google-recommended best practices?
A
Perform a rolling update with a PodDisruptionBudget of 80%.
B
Perform a rolling update with a HorizontalPodAutoscaler scale-down policy value of 0.
C
Convert the Deployment to a StatefulSet, and perform a rolling update with a PodDisruptionBudget of 80%.
D
Convert the Deployment to a StatefulSet, and perform a rolling update with a HorizontalPodAutoscaler scale-down policy value of 0.
No comments yet.