Topic 1 Question 142
You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source of the issue is a recently updated container image, although the exact change in code was not identified. The deployment is currently pointing to the latest tag. You need to update your cluster to run a version of the container that functions as intended. What should you do?
Create a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.
Alter the deployment to point to the sha256 digest of the previously working container.
Build a new container from a previous Git tag, and do a rolling update on the deployment to the new container.
Apply the latest tag to the previous container image, and do a rolling update on the deployment.
ユーザの投票
コメント(5)
- 正解だと思う選択肢: B👍 3koo_kai2023/10/28
- 正解だと思う選択肢: B
This question looks to tease out the knowledge of tag vs digest while deploying containers. The best approach is to figure out the previously functional digest and apply to deployment. Tag is mutable, using a tag like latest in deployment is confusing and prone to cause deployment inconsistency. https://cloud.google.com/kubernetes-engine/docs/concepts/about-container-images
👍 3lelele20232023/11/01 Answer D seems correct. https://cloud.google.com/kubernetes-engine/docs/how-to/updating-apps
👍 1activist2023/10/22
シャッフルモード