Google Professional Cloud DevOps Engineer Question 116
Single answerGoogle Cloud PlatformYour team has deployed a new version of a microservice on Google Kubernetes Engine (GKE). Shortly after deployment, users report significant performance degradation. You want to minimize downtime while restoring the previous stable version of the service. Which rollback strategy should you implement to address this issue?
- A
Perform a rolling update with the previous stable version of the container image.
- B
Delete the new deployment and create a fresh deployment using the previous stable version.
- C
Use the GKE rollback command to automatically revert to the previous version.
- D
Manually edit the deployment YAML file and apply changes to use the previous stable version.
Show answer and explanation
Correct answer: A
Explanation
In Google Kubernetes Engine (GKE), a rolling update using the previous stable version of the container image ensures a controlled rollback with minimal downtime and disruption. This approach gradually replaces the new version with the stable version while continuously monitoring the health of pods. Other options either introduce downtime, do not exist as features, or increase the risk of configuration errors.
- A. Correct.
Performing a rolling update with the previous stable version is the most reliable and recommended approach in GKE. It ensures minimal downtime by gradually replacing the problematic version with the stable one while monitoring the health of the pods.
- B. Incorrect.
Deleting the deployment and creating a fresh deployment can lead to downtime because the pods running the new version will be removed before the previous version is brought back online. This is not an optimal rollback strategy in production environments.
- C. Incorrect.
There is no GKE-specific rollback command to automatically revert to a previous version. Rollbacks in GKE require manual configuration or use of deployment strategies.
- D. Incorrect.
Manually editing the deployment YAML file and applying changes is prone to errors and may result in misconfigurations. It is not a best practice for efficient and reliable rollbacks.