Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An online retail company hosts its core ordering service on Google Kubernetes Engine (GKE). The application experiences predictable, massive traffic spikes every morning at the start of business hours, followed by minimal activity overnight.
To ensure responsiveness during the morning rush, the team currently maintains a high static minReplicas value in the Horizontal Pod Autoscaler (HPA) configuration. However, management noticed that this setting prevents the cluster from scaling down during off-peak night hours, resulting in substantial unnecessary infrastructure costs.
You need to design a scaling architecture that handles the predictable morning surges without overpaying for idle capacity overnight.
Which scaling strategy should you implement?
minReplicas configuration and set the GKE cluster node pool autoscaler minimum node limit to zero.This configuration attempts to rely on the GKE Cluster Autoscaler minimum node setting (min-nodes=0) while leaving the Horizontal Pod Autoscaler (HPA) minReplicas set to a permanently high value.
minReplicas enforces a high minimum number of running Pods at all times, the Pods will continually request CPU and memory, preventing the cluster autoscaler from scaling down nodes overnight.minReplicas creates an inflexible lower bound on cluster capacity.The workload experienced unpredictable 24/7 traffic at steady rates that required immediate capacity without any tolerance for node spin-up times.
Auto mode to increase Pod CPU and memory requests overnight while disabling the Horizontal Pod Autoscaler.The Vertical Pod Autoscaler (VPA) adjusts the CPU and memory resource requests and limits of individual containers within Pods rather than changing the total number of Pod replicas.
Auto mode, VPA evicts and restarts Pods to apply updated resource boundaries, which can cause service disruptions during traffic transitions.The goal was to determine optimal baseline resource requests and limits for single-instance, long-running batch applications that run during off-peak hours.
minReplicas to 1 and rely strictly on reactive target CPU utilization thresholds to scale up instances when the morning traffic arrives.This approach configures the Horizontal Pod Autoscaler (HPA) with a low minimum replica count (minReplicas: 1) and depends entirely on reactive resource consumption triggers (like reaching 80% target CPU utilization) to scale out the application.
Traffic increases were gradual and continuous throughout the day rather than sudden, massive surges at a known start time.
Scheduled autoscaling on Google Kubernetes Engine combines standard Kubernetes autoscaling mechanisms with time-based triggers. Because standard Horizontal Pod Autoscaling (HPA) reacts dynamically to resource metrics like CPU or memory utilization, it can suffer from a slight lag during sudden, sharp traffic surges. By utilizing Cloud Monitoring custom metrics alongside scheduled jobs (such as CronJobs), you can programmatically publish metric values at specific times to scale application replicas up ahead of business hours and down during low-traffic windows.

This solution directly balances performance and cost. Rather than keeping expensive infrastructure running all night, scheduled custom metrics anticipate regular traffic spikes while letting standard dynamic scaling handle unexpected daytime fluctuations.
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