Medium1 markMultiple Choice
Subtask 2.3: Compute SystemsCloud RunScalabilityCloud SQLServerless

GCP PCA · Question 39 · Compute Systems

You are deploying a containerized web application to Cloud Run. The application is expected to receive sudden, massive spikes in traffic. You want to ensure the application scales quickly to handle the load, but you also need to prevent the backend database (Cloud SQL) from being overwhelmed by too many concurrent connections. Which TWO settings should you configure on the Cloud Run service? (Select TWO)

Answer options:

A.

Set the minimum instances to 0.

B.

Increase the maximum concurrent requests per instance (concurrency).

C.

Enable the Cloud SQL Auth Proxy sidecar.

D.

Set the CPU allocation to 'CPU only allocated during request processing'.

E.

Set a maximum number of instances (max instances).

How to approach this question

Look for the setting that optimizes container throughput (concurrency) and the setting that acts as a circuit breaker for downstream systems (max instances).

Full Answer

B,E
Cloud Run can scale from 0 to thousands of instances in seconds. To handle spikes efficiently, increasing 'concurrency' allows a single container to process multiple requests (up to 1000), reducing cold starts. However, if traffic is massive, Cloud Run might still spin up too many instances, each opening a connection to Cloud SQL, causing connection exhaustion. Setting 'max instances' limits the scale-out, protecting the downstream database.

Common mistakes

Forgetting that serverless scale-out can act as a DDoS attack on your own relational database if not capped with max instances.

Practice the full GCP Professional Cloud Architect Practice Exam 7

50 questions · hints · full answers · grading

More questions from this exam