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 e-commerce organization hosts a latency-sensitive public web service on Google Cloud using App Engine standard environment with automatic scaling. The service currently scales down to zero instances during inactive overnight periods to save costs. However, during sudden morning traffic spikes, users experience latency degradation caused by instance cold starts and request queuing before new instances can spin up.
You need to optimize the autoscaling behavior to satisfy the following requirements:
Which configuration should you specify in the application's automatic scaling configuration?
target-cpu-utilization to 0.95.This option attempts to switch the App Engine service to manual scaling mode with a static number of instances while attempting to apply an automatic scaling metric (target-cpu-utilization).
target-cpu-utilization and target-throughput-utilization belong exclusively to the automatic-scaling block and are invalid in manual scaling configurations.The workload had completely predictable, steady-state throughput requiring a constant instance fleet with no dynamic autoscaling requirements.
min-instances to 0, configure warmup-requests-enabled to false, and set max-instances to 2147483647.This configuration sets the minimum instance count to zero, disables App Engine warmup requests, and removes upper bounds on autoscaling by setting max-instances to its theoretical maximum integer limit.
min-instances to 0 forces the application to scale completely to zero during idle periods. When the first morning request arrives, a brand-new instance must be initialized from scratch, resulting in cold-start latency.warmup-requests-enabled to false actively worsens cold-start behavior because initialization code and servlet context listeners cannot execute before receiving live user traffic.target-throughput-utilization or concurrent connection thresholds, meaning scaling decisions will rely solely on default latency or CPU metrics rather than proactive concurrency scaling.max-instances setting leaves the workload vulnerable to runaway scaling costs during traffic surges or denial-of-service events.The goal were purely to minimize idle hosting costs for a non-latency-sensitive batch or internal tool where cold starts are acceptable.
min-instances to a value greater than zero and define target-throughput-utilization alongside max-concurrent-requests.This configuration adjusts the automatic-scaling parameters in Google Cloud App Engine standard environment by setting a non-zero min-instances baseline and defining target-throughput-utilization in conjunction with max-concurrent-requests.
min-instances to a number greater than 0 (e.g., 2 or more) guarantees that pre-warmed dynamic instances are always running and ready to immediately serve incoming requests when morning traffic starts, preventing cold-start delays.target-throughput-utilization parameter specifies a fractional threshold (between 0.5 and 0.95). When current concurrent connections reach max-concurrent-requests * target-throughput-utilization, App Engine starts provisioning new instances ahead of time, ensuring instances do not saturate their maximum concurrent request limit.This solution directly addresses both cold-start mitigation and concurrency-based autoscaling within App Engine standard's native serverless model without introducing unnecessary infrastructure management overhead.
minNumReplicas set to 0.This option shifts the deployment architecture away from serverless App Engine to an IaaS-based Compute Engine Managed Instance Group (MIG) using schedule-based autoscaling with a minimum replica count of zero.
The workload required custom OS kernel extensions, GPU hardware acceleration, or specialized networking protocols unsupported by serverless platforms.
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