Question 1 of 18
A Cloud Run checkout service is I/O-bound and its instances have low CPU. What would you change first, and how would you validate the change?
Strong Interview Answer
I would test a higher maximum concurrency because requests spend most of their time waiting on external APIs. I would load-test the revision and compare latency, error rate, memory, and instance count before adopting the setting.
What to Listen For
- I/O-bound workload
- Cloud Run concurrency
- load test
- latency and instance metrics
Caution
Do not recommend concurrency one merely because the service is under load; that is the containment setting for unsafe or resource-heavy code, not the default answer to low CPU with I/O wait.