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: Eliminate cold-start latency for initial incoming morning requests Proactively scale out new instances based on concurrent connections before current instances reach full capacity Retain automatic scaling capabilities during high-traffic periods Which configuration should you specify in the application's automatic scaling configuration?

Configure `min-instances` to a value greater than zero and define `target-throughput-utilization` alongside `max-concurrent-requests`.: What this configuration is 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. How it meets the requirements Eliminating cold starts: Setting 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. Proactive scaling on concurrency: The 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. Retaining automatic scaling: The application continues to utilize dynamic horizontal autoscaling to handle higher daytime traffic volumes as load increases beyond the minimum baseline. Key advantages and capabilities Pre-warmed capacity: Maintains an active execution environment to bypass JVM/runtime initialization overhead. Smooth scaling transitions: Prevents request queueing and throttling by scaling up before instances reach 100% concurrency capacity. Granular resource optimization: Allows balancing cost and performance by fine-tuning minimum reserve capacity and target thresholds. Why this is optimal 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.

App Engine Autoscaling Concurrency Coldstarts | Professional Cloud Architect

StudyCerts

Explanations

What this configuration is

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.

How it meets the requirements

Eliminating cold starts: Setting 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.
Proactive scaling on concurrency: The 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.
Retaining automatic scaling: The application continues to utilize dynamic horizontal autoscaling to handle higher daytime traffic volumes as load increases beyond the minimum baseline.

Key advantages and capabilities

Pre-warmed capacity: Maintains an active execution environment to bypass JVM/runtime initialization overhead.
Smooth scaling transitions: Prevents request queueing and throttling by scaling up before instances reach 100% concurrency capacity.
Granular resource optimization: Allows balancing cost and performance by fine-tuning minimum reserve capacity and target thresholds.

Why this is optimal

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.

View source documentation

Professional Cloud Architect

App Engine Autoscaling Concurrency Coldstarts