Topic 1 Question 185
Your company has an application running as a Deployment in a Google Kubernetes Engine (GKE) cluster. When releasing new versions of the application via a rolling deployment, the team has been causing outages. The root cause of the outages is misconfigurations with parameters that are only used in production. You want to put preventive measures for this in the platform to prevent outages. What should you do?
Configure liveness and readiness probes in the Pod specification.
Configure health checks on the managed instance group.
Create a Scheduled Task to check whether the application is available.
Configure an uptime alert in Cloud Monitoring.
ユーザの投票
コメント(10)
- 正解だと思う選択肢: A
A: Configuring the right liveness and readiness probes prevents outages when rolling out a new ReplicaSet of a Deployment, because Pods are only getting traffic when they are considered ready. B: With GKE, you do not deal with MIGs. C: Does not use GKE tools and is therefore not the best option. D: Does alert you but does not prevent the outage.
👍 11jabrrJ68w02ond12022/09/04 - 正解だと思う選択肢: A
A. There are no MIGs in GKE. Only thing that makes sense is to have good readiness probes
👍 4aut0pil0t2022/09/02 Option A is correct. Since it is regarding GKE and the application deployed in GKE cluster. Therefore, managed instance group does not have anything to do. So, right answer is: A. Configure liveness and readiness probes in the Pod specification.
👍 2spET_10242022/09/03
シャッフルモード