Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
An SRE team manages a latency-critical e-commerce checkout API deployed on Google Cloud Run. The API experiences unpredictable, spiky traffic patterns throughout the day.
During traffic surges, the service frequently breaches its 99th percentile (P99) latency Service Level Objective (SLO) due to cold-start overhead when new container instances spin up. Performance profiling shows that each container instance is thread-safe and can handle up to 40 concurrent requests without performance degradation.
You need to optimize the Cloud Run autoscaling configuration to eliminate cold-start latency for baseline traffic and handle rapid bursts efficiently, while minimizing infrastructure costs.
Which configuration should you apply to the Cloud Run service?
This configuration combines Cloud Run minimum instances (--min-instances), optimized container concurrency (--concurrency), and request-based CPU allocation (CPU throttling enabled) to create an elastic, cost-optimized, and low-latency serverless architecture.
StudyCerts
StudyCerts--min-instances maintains a pre-warmed pool of ready container instances. Incoming baseline requests are routed directly to these initialized instances without waiting for container startup, runtime bootstrapping, or health checks.--concurrency=40 configures each instance to multiplex up to 40 simultaneous requests. During a sudden traffic surge, existing warm instances absorb the initial influx of concurrent requests immediately before Cloud Run needs to scale out additional instances.--cpu-throttling), CPU is allocated and billed at full rate only during request execution. Idle minimum instances that are not actively processing requests are billed at a substantially discounted idle rate, avoiding the full compute costs of continuously running dedicated infrastructure.--max-instances threshold when incoming demand exceeds aggregate concurrency capacity.This approach directly targets the root causes of P99 SLO breaches—cold starts and aggressive single-request instance thrashing—while leveraging Cloud Run's discounted idle tier to protect the organization's cloud budget.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.