Question

A retail company runs a customer-facing API on Cloud Run. During an unplanned marketing campaign, traffic spiked 20x and Cloud Run scaled out aggressively, causing a downstream Cloud SQL instance to hit its connection limit and a surprise spike in the monthly bill. The team wants to protect the database and cap runaway costs during future spikes while keeping the service available at a predictable capacity. Which action best meets these goals?

Accepted Answer

Set a maximum number of instances on the Cloud Run service to bound concurrent scaling and use a connection pooler in front of Cloud SQL.

Answer

Increase the Cloud Run per-instance concurrency to a very high value so fewer instances are needed at any traffic level.

Answer

Set a higher minimum number of instances to keep warm capacity ready for spikes.

Answer

Create a billing budget alert on the project so the team is notified when spending exceeds a threshold.