Answer-first summary for fast verification
Answer: Use GKE autoscaling to increase the number of replicas for the affected service to distribute the load evenly and improve application availability., Create a postmortem report to analyze the root cause of the incident and implement corrective actions to prevent similar incidents in the future.
**Correct Answers:** - **Use GKE autoscaling to increase the number of replicas for the affected service to distribute the load evenly and improve application availability.** This strategy helps mitigate the incident's impact by ensuring the service remains responsive. - **Create a postmortem report to analyze the root cause of the incident and implement corrective actions to prevent similar incidents in the future.** This is a critical step in the incident management process for continuous improvement. **Incorrect Options:** - Deploying a canary release is not effective for identifying the root cause of an incident. - Google Cloud Pub/Sub is not suitable for notifying the on-call team about incidents; Google Cloud Operations Suite is recommended instead. - Introducing untested changes in production can lead to further instability and is not a best practice.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a DevOps Engineer managing service incidents for an application on Google Kubernetes Engine (GKE), your organization faces an incident affecting application availability. Which two actions are crucial for mitigating the incident's impact and ensuring efficient incident management?
A
Deploy a canary release of the application with the same configuration as the current production environment to identify the root cause of the incident.
B
Configure Google Cloud Pub/Sub to notify the on-call team when an incident is detected to reduce the mean time to resolution (MTTR).
C
Use GKE autoscaling to increase the number of replicas for the affected service to distribute the load evenly and improve application availability.
D
Create a postmortem report to analyze the root cause of the incident and implement corrective actions to prevent similar incidents in the future.
E
Perform a rolling update in the production environment to introduce a new, untested version of the application to resolve the incident.
No comments yet.