Google Professional-Cloud-DevOps-Engineer Exam With Confidence Using Practice Dumps

OOMKilled means the containers exceeded their allocated memory. Since the HPA isn't scaling up (stuck at min), this indicates the issue is not scale-related but container memory limits are too low.

"Pods terminated with OOMKilled have exceeded their memory limits. You should adjust the container's resource requests and limits."

— Kubernetes OOMKill Debug Guide

Scaling the number of replicas won't help if each replica crashes. You need to increase memory limits so pods can run reliably before autoscaling can even work.

Comprehensive and Detailed 150 to 200 words of Explanation From Google Cloud DevOps guides documents:

In incident management, the primary goal during the "Mitigation" phase is to restore service levels as quickly as possible, often referred to as "stopping the bleeding." Google Cloud’s SRE principles emphasize that during a high-priority incident, you should prioritize actions that have an immediate impact over long-term fixes or deep-dive forensics. While a rollback (Option C) is a standard procedure, the 15-minute CI/CD overhead is too slow when a critical payment service is failing. Using Cloud Profiler (Option A) is a diagnostic step that should be reserved for the post-mortem phase, not the heat of the outage.

Canceling the active Dataflow job (Option D) is the fastest way to alleviate the pressure on the shared Memorystore instance. Since the Dataflow pipeline is "non-critical" and "batch-based," stopping it has a low business impact compared to the payment service outage. Once the job is canceled, the write pressure on Redis drops instantly, reducing read latency and restoring the payment service to health. This aligns with the SRE practice of "shedding load" to protect critical system components. Once the immediate crisis is resolved, the team can then investigate the root cause and implement long-term fixes like rate limiting or resource isolation.