Answer-first summary for fast verification
Answer: Increase the memory limit in the application deployment.
The issue described indicates a memory leak in the application, as the heap usage grows constantly until the application restarts. Increasing the CPU limit (Option A) or adding high memory compute nodes (Option B) does not address the root cause of the memory leak. Adding Cloud Trace (Option D) might help in tracing requests but does not directly solve the memory leak issue. The most appropriate action is to increase the memory limit in the application deployment (Option C) to accommodate the growing heap usage until the memory leak can be identified and fixed in the application code.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a Site Reliability Engineer supporting a Go application running on Google Kubernetes Engine (GKE) in production, you observe that the application restarts after approximately 15 minutes of runtime following a new release. After enabling Cloud Profiler, you notice the heap usage grows continuously until the restart occurs. What steps should you take to address this issue?
A
Increase the CPU limit in the application deployment.
B
Add high memory compute nodes to the cluster.
C
Increase the memory limit in the application deployment.
D
Add Cloud Trace to the application, and redeploy.
No comments yet.