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.
Your company runs a microservices application on a Google Kubernetes Engine (GKE) Standard cluster. During peak traffic periods, new Pods are created to handle the load, but they remain in a Pending state because the existing worker nodes lack sufficient CPU and memory capacity to satisfy their resource requests.
You need to ensure that the cluster automatically provisions additional Compute Engine instances when Pods are unschedulable and removes nodes when they are underutilized.
What should you do?
Node auto-repair is a GKE management feature that continuously monitors node health status. If a node fails health checks (reporting a NotReady status for an extended period), GKE automatically drains and recreates the unhealthy virtual machine instance.
Pending Pod queues or evaluate workload resource requests.Worker nodes were becoming unresponsive or failing Kubernetes health checks due to underlying operating system or hardware issues and needed automated recreation.
Cluster Autoscaler is a GKE management feature that automatically adjusts the number of worker nodes in a given node pool based on the resource demands of your scheduled and pending workloads.
Pending state), Cluster Autoscaler detects the unschedulable Pods and adds new nodes up to the configured maximum limit.Enabling Cluster Autoscaler directly addresses the root cause of Pending unschedulable Pods by provisioning the necessary physical VM infrastructure on-demand while optimizing operational costs when demand subsides.
Resource limits define the maximum amount of CPU and memory a container is allowed to consume before being throttled (for CPU) or terminated with an Out-Of-Memory (OOM) error (for memory).
Pending Pods unscheduled.Containers were experiencing CPU throttling or OOMKilled crashes during high load while running on nodes that had plenty of allocatable headroom.
The Horizontal Pod Autoscaler (HPA) is a Kubernetes workload controller that adjusts the number of Pod replicas in a Deployment, ReplicaSet, or StatefulSet based on observed CPU/memory utilization or custom metrics.
Pending queue without providing the infrastructure needed to run them.The scenario asked how to automatically scale the number of application Pod replicas in response to increasing end-user traffic or CPU consumption on existing containers.
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