Answer-first summary for fast verification
Answer: Check whether the Cloud Run service has scaled to a number of instances that equals the max-instances value. If necessary, increase the max-instances value.
The issue occurs under high load, suggesting the Cloud Run service might be hitting the `max-instances` limit. Cloud Run automatically scales instances based on traffic, but if the configured `max-instances` is too low, the service cannot scale beyond that limit. When traffic exceeds the capacity of the available instances, requests are queued or fail, leading to slow performance and errors. Increasing the `max-instances` value allows more instances to handle the load. Option D addresses this by checking if the service is scaling to the current `max-instances` and adjusting it if needed. Other options are less relevant: traffic splitting (A) is for gradual rollouts, increasing `min-instances` (B) reduces cold starts but doesn't resolve max scaling limits, and disabling Cloud Armor (C) is unnecessary unless misconfigured policies block legitimate traffic (not indicated here).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
How can you troubleshoot performance issues in a Cloud Run web application that functions correctly under light traffic but becomes slow and returns errors during high-load testing when exposed via its public IP address?
A
Check the network traffic to Cloud Run in Cloud Monitoring to validate whether a traffic spike occurred. If necessary, enable traffic splitting on the Cloud Run instance to route some of the traffic to a previous instance revision.
B
Check the min-instances value for your Cloud Run service. If necessary, increase the min-instances value to match the maximum number of virtual users in your load test.
C
Check whether Cloud Armor is detecting distributed denial of service (DDoS) attacks and is blocking traffic before the traffic is routed to your Cloud Run service. If necessary, disable any Cloud Armor policies in your project.
D
Check whether the Cloud Run service has scaled to a number of instances that equals the max-instances value. If necessary, increase the max-instances value.