Exam Professional Cloud DevOps Engineer topic 1 question 154 discussion

insufficient memory

D. Cloud Trace can help identify inefficient memory usage and pinpoint the root cause of the memory leak. Since Cloud Profiler already showed that heap usage is constantly increasing, the next step is to analyze memory allocations in detail. Cloud Trace provides visibility into request execution and can highlight which functions are consuming excessive memory or not releasing it properly. This helps in debugging and fixing the leak instead of just mitigating its effects. C. Increasing the memory limit in the deployment would provide a temporary workaround by delaying the OOM kill. However, this does not fix the root cause—excessive memory allocation and retention. Eventually, the application will still exhaust the available memory and restart.

D) I would add Cloud Trace to find the root cause of the heap usage growth. Adding more memory will only solve the issue temporarily, and you might now see a restart in 30 minutes.

Given the scenario where the heap usage of the application grows constantly until it restarts, the issue is likely related to memory consumption. Therefore, the appropriate action to take is to address the memory-related problem. In this context, option C is the recommended. By increasing the memory limit in the application deployment configuration, you provide more memory resources to the application, potentially preventing it from exhausting its memory and triggering restarts. Options A and B may not directly address the underlying memory problem. Option D, adding Cloud Trace, is more focused on request tracing and may not directly resolve the memory growth issue. Therefore, increasing the memory limit is the most relevant step to take based on the symptoms described.

Vote C

That's what I do at work :-)