Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
You are architecting an autoscaling strategy for a latency-critical event processing application deployed on Google Kubernetes Engine (GKE) Standard. The application experiences sudden spikes in message volume from a Google Cloud Pub/Sub subscription and variable memory usage during payload deserialization.
You need to scale the container replicas based on queue depth, optimize container resource sizing without metric contention, and ensure the underlying cluster infrastructure dynamically provisions compute capacity when Pods cannot be scheduled.
Which autoscaling configuration should you implement?
This configuration targets both horizontal and vertical autoscalers to the same resource metric (CPU) while enabling native Compute Engine Managed Instance Group (MIG) autoscaling on the cluster's worker nodes.
PodDisruptionBudgets.You were managing standalone Compute Engine VM fleets without Kubernetes orchestration and needed traditional instance-level horizontal scaling based strictly on average host CPU consumption.
This configuration relies strictly on container resource limits for scheduling, attaches HPA to an external Pub/Sub metric, and enables both GKE Cluster Autoscaler and native Compute Engine MIG autoscaling simultaneously.
Compute Engine MIG autoscaling were natively integrated into the Kubernetes control plane scheduling logic, which is not how GKE is architected.
This approach attempts to scale Pod replicas horizontally based on memory utilization percentages while omitting container resource requests and assuming Cluster Autoscaler responds to real-time node memory usage.
Unschedulable (Pending) due to total requested resources exceeding node allocatable capacity.Kubernetes supported utilization-based node autoscaling directly at the kubelet layer without requiring explicit pod scheduling requests, which contradicts the core design of the Kubernetes scheduling pipeline.
Multi-dimensional autoscaling on Google Kubernetes Engine (GKE) combines workload-level horizontal elasticity, workload-level vertical resource right-sizing, and cluster-level compute provisioning into a unified, non-conflicting scaling architecture.
Pending (unschedulable) Pods and adds Compute Engine VMs to the node pool when existing nodes lack allocatable capacity.This design establishes a clean separation of concerns: HPA handles concurrency based on external ingress volume, VPA right-sizes container memory footprints, and GKE Cluster Autoscaler ensures underlying compute infrastructure expands dynamically without conflicting with native Compute Engine autoscalers.
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 Validated