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 deploying a stateless web API to Cloud Run to serve incoming HTTP traffic. During load testing, engineers observe that Cloud Run creates a new container instance for every individual simultaneous request, resulting in rapid horizontal scale-out and underutilized instance resources.
The API handles lightweight, non-blocking I/O operations. The team wants each container instance to process multiple simultaneous requests concurrently and ensure they are only billed for compute resources when requests are actively being processed.
Which configuration should the team apply to the Cloud Run service?
Cloud Run concurrency determines the maximum number of simultaneous requests that a single container instance can receive. By default, Cloud Run supports up to 1,000 concurrent requests per instance (with a default of 80). The "CPU is only allocated during request processing" model is Cloud Run's standard serverless billing model, where CPU is throttled and compute is not billed when the container instance is not actively handling requests.
This combination aligns directly with Google Cloud best practices for stateless, I/O-bound web applications. It prevents excessive instance creation while ensuring compute billing stops as soon as all active requests complete.
Setting concurrency to 1 forces Cloud Run into a strict single-concurrency model, where each container instance processes only one request at a time. Selecting "CPU is always allocated" allocates continuous CPU capacity throughout the entire lifecycle of the container instance, regardless of whether it is actively processing requests.
The workload consisted of heavy, single-threaded CPU computations or background worker processes that need to perform background processing tasks even when no HTTP requests are being actively handled.
This option configures the Cloud Run service to accept multiple concurrent requests per container instance while keeping the container's CPU continuously provisioned and running using the instance-based pricing model.
The application required background threads to continue running tasks (such as event polling or continuous log flushing) after the HTTP response has already been sent back to the client.
Setting the maximum instances limit to 1 places a hard cap on Cloud Run autoscaling, restricting the entire service to a maximum of one running container instance at any given time.
The goal was to protect a legacy, non-scalable downstream database that cannot handle more than one active database connection from Cloud Run.
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