You are developing a public web application on Cloud Run. You expose the Cloud Run service directly with its public IP address. You are now running a load test to ensure that your application is resil

Question

Options

• ACheck the network traffic to Cloud Run in Cloud Monitoring to validate whether a traffic spike
• BCheck the min-instances value for your Cloud Run service. If necessary, increase the min-
• CCheck whether Cloud Armor is detecting distributed denial of service (DDoS) attacks and is
• DCheck whether the Cloud Run service has scaled to a number of instances that equals the max-

• A
  15% (5)
• B
  9% (3)
• C
  6% (2)
• D
  71% (24)

Explanation

When Cloud Run reaches its configured max-instances limit, it cannot scale out further to handle additional requests. Incoming requests then queue or are rejected, causing slow responses and errors - exactly the symptoms described. Option D directs you to check whether the service has reached max-instances, which is the root cause to verify first. If the service is capped, increasing max-instances (or setting it to 0 for unlimited) resolves the issue. Option A (checking network traffic in Cloud Monitoring) is too generic and would not pinpoint this specific bottleneck. Option B (checking min-instances) addresses cold start latency, not capacity under load. Option C (Cloud Armor DDoS detection) is irrelevant here - the traffic is your own load test, not an attack, and Cloud Armor is not configured in this scenario.

No community discussion yet for this question.