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?
A. Configure liveness and readiness probes in the Pod specification.
B. Configure health checks on the managed instance group.
C. Create a Scheduled Task to check whether the application is available.
D. Configure an uptime alert in Cloud Monitoring.
Disclaimer
This is a practice question. There is no guarantee of coming this question in the certification exam.
Answer
A
Explanation
A. Configure liveness and readiness probes in the Pod specification.
(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. Configure health checks on the managed instance group.
(With GKE, you do not deal with MIGs.)
C. Create a Scheduled Task to check whether the application is available.
(Does not use GKE tools and is therefore not the best option.)
D. Configure an uptime alert in Cloud Monitoring.
(Does alert you but does not prevent the outage.)