Google Professional Cloud DevOps Engineer Question 149
Select 3Google Cloud PlatformYour team is running a containerized application on Google Kubernetes Engine (GKE). Recently, users have reported intermittent high latency and timeouts when accessing the application. As a DevOps engineer, you want to troubleshoot the issue. Which of the following actions should you take to identify the root cause?
- A
Check the GKE pod logs for errors or warnings.
- B
Inspect the horizontal pod autoscaler (HPA) configuration and metrics.
- C
Increase the CPU and memory resource limits of all pods in the cluster.
- D
Use Cloud Monitoring to analyze network latency and application performance metrics.
- E
Manually restart all pods in the cluster to ensure they are running fresh instances.
Show answer and explanation
Correct answers: A, B, D
Explanation
Troubleshooting high latency and timeouts in GKE involves examining logs for application-level issues, verifying the scaling behavior of the application through HPA, and analyzing network and performance metrics using Cloud Monitoring. These steps allow you to systematically identify the root cause of the issue. Arbitrarily increasing resource limits or restarting pods may temporarily alleviate symptoms but do not address the underlying problem.
- A. Correct.
Checking the pod logs can help identify application-level errors or warnings that might be causing high latency or timeouts.
- B. Correct.
Inspecting the HPA configuration and metrics allows you to verify if the application is scaling correctly in response to load. Misconfigured scaling policies could lead to performance issues.
- C. Incorrect.
While increasing CPU and memory resource limits might seem like a solution, it is not a troubleshooting step. Resource limits should only be adjusted after identifying the root cause.
- D. Correct.
Cloud Monitoring provides insights into network latency and application performance, which are critical for identifying the source of intermittent latency.
- E. Incorrect.
Restarting all pods is not an effective troubleshooting step as it only temporarily resolves symptoms without identifying the root cause.