Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An administrator is deploying an in-memory data processing workload to a Google Kubernetes Engine (GKE) Autopilot cluster. During performance testing, the Pod encounters frequent Out-Of-Memory (OOMKilled) termination errors because memory allocation is insufficient for the working set, while CPU utilization remains near zero despite having several vCPUs requested.
The administrator wants to ensure workload stability while optimizing operational costs in GKE Autopilot.
What should the administrator do?
Pod resource request optimization in Google Kubernetes Engine (GKE) Autopilot is the practice of tailoring container CPU, memory, and storage requests to reflect the true runtime resource profile of the workload.
OOMKilled crashes: Increasing the memory request provides sufficient memory to accommodate the application's active working set, preventing the Linux kernel out-of-memory killer from terminating the container.GKE Autopilot operates on a per-Pod billing model where users pay specifically for the resources requested by running workloads. Adjusting requests to supply sufficient RAM for the working set while trimming idle vCPUs achieves both high reliability and minimal cost.

This approach sets CPU and memory requests to excessively high values under the assumption that GKE Autopilot charges solely for real-time CPU cycles and RAM consumed by running processes.
Google Cloud offered an execution mode where GKE Autopilot billed exclusively on telemetry-measured process consumption rather than declared Pod request reservations.
This approach attempts to remove the resources.requests specification entirely from the container manifest, assuming Kubernetes will provide elastic, unbounded compute resources.
OOMKilled crashes.This option would be appropriate only for quick proof-of-concept testing of basic, generic workloads that naturally fit within standard default Kubernetes resource parameters.
This configuration increases the container's compute request while keeping memory low, assuming the underlying operating system can swap active container memory to disk.
OOMKilled termination regardless of available CPU.The workload was CPU-bound and experiencing computational throttling during intensive calculations rather than memory exhaustion.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated