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.
A DevOps engineering team operates a data ingestion service running on a Compute Engine regional Managed Instance Group (MIG). The worker instances process tasks pulled from a Cloud Pub/Sub subscription.
During high-volume periods, incoming message traffic fluctuates rapidly with intermittent 2-to-3-minute lulls between bursts. The team observes the following issues:
Which autoscaler configuration should the team implement to resolve these issues?
Scale-in controls in Compute Engine Managed Instance Groups (MIGs) allow administrators to regulate the pace at which the autoscaler removes VM instances. By defining a stabilization period (a lookback window up to several hours) and a max scaled-in replicas constraint (either a fixed number or percentage), the autoscaler prevents rapid, abrupt reductions in capacity during transient drops in load.
maxScaledInReplicas restricts the rate of instance deletions per time unit, providing a gradual scaling curve that gives running instances adequate time to finish inflight messages and drain workloads cleanly.Scale-in controls are purpose-built in Google Cloud to handle bursty workloads where short-term metric drops would otherwise trigger premature scale-in events, directly eliminating VM thrashing while protecting in-progress tasks.
The Only scale out autoscaling mode allows the MIG autoscaler to automatically add instances when demand surges, but completely disables automated scale-in actions by the control plane.
Management mandated an absolute freeze on downscaling during a major promotional retail event, preferring idle compute costs over any potential risk of capacity loss.
Predictive autoscaling leverages machine learning algorithms to analyze historical metric patterns (such as CPU usage) over several weeks and proactively scales out capacity ahead of forecasted daily or weekly cycles.
The workload followed a strictly predictable diurnal pattern (e.g., traffic surging every morning at 09:00 AM) and instances required significant warm-up time before accepting user web traffic.
The cool-down period (also called the initialization period) specifies how long the autoscaler should wait after a new instance is created before collecting and factoring that VM's metrics into autoscaling decisions.
New VM instances required 30 minutes to download heavy container images, initialize local caches, and become healthy before they could handle incoming traffic.
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