Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is hosting a latency-sensitive API on Cloud Run. During periods of zero incoming traffic, the service currently scales down to zero instances. As a result, the first incoming requests experience noticeable delay due to cold start initialization. At the same time, the finance team requires strict guardrails to prevent runaway compute costs during unexpected traffic surges.
Which autoscaling configuration should you implement to meet these requirements?
Concurrency in Cloud Run defines the maximum number of simultaneous requests a single container instance can handle before the platform scales out additional instances.
min-instances at zero allows the service to scale down completely during idle periods. The first request after an idle period must still spin up a new container from scratch, incurring full cold start latency.max-instances limit, large traffic surges can still scale out many instances and lead to uncontrolled billing.The primary objective were to maximize throughput per container instance under sustained high concurrency while optimizing active compute utilization, without concern for idle cold start delays.
This option attempts to disable scaling by setting maximum instances to zero while enabling continuous CPU allocation.
max-instances=0 disables request serving for the revision.This configuration would only make sense if the goal were to temporarily disable all incoming traffic and shut down an active service deployment without deleting the underlying configuration.
Setting minimum instances (min-instances) and maximum instances (max-instances) on a Cloud Run service allows administrators to control both the lower and upper bounds of container autoscaling. By configuring min-instances to a non-zero value, Cloud Run keeps a baseline number of container instances initialized and warm at all times. Setting max-instances restricts the upper scaling limit to cap compute resource consumption.
min-instances is configured, designated instances remain running and ready to process traffic immediately. New requests avoid the startup penalty of container provisioning, language runtime boot, and global variable initialization.max-instances guarantees that the service will not scale beyond a predetermined limit, establishing a strict ceiling on compute expenditure during traffic surges.This approach directly targets the fundamental trade-off in serverless computing: balancing rapid response times with cost governance. It avoids complete cold starts by maintaining warm capacity while simultaneously enforcing budget guardrails.
Lazy initialization is a software design pattern where objects and dependencies are created only when needed rather than during application startup. The request timeout defines how long an instance will wait for a request to complete before returning an error.
You were optimizing application startup code to reduce container boot overhead on services where scaling down to zero is explicitly preferred to avoid idle instance charges.
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