Bird
0
0

In GCP request-based auto scaling, what happens if the average requests per instance exceed the target concurrency?

easy📝 Conceptual Q2 of 15
GCP - Cloud Run
In GCP request-based auto scaling, what happens if the average requests per instance exceed the target concurrency?
AInstances are shut down to save cost
BMore instances are added to handle the load
CCPU throttling is applied to existing instances
DRequests are queued indefinitely
Step-by-Step Solution
Solution:
  1. Step 1: Understand scaling trigger

    If the average requests per instance exceed the target concurrency, the system needs to add capacity.
  2. Step 2: Identify scaling action

    The system adds more instances to distribute the load and maintain performance.
  3. Final Answer:

    More instances are added to handle the load -> Option B
  4. Quick Check:

    High requests per instance = Add instances [OK]
Quick Trick: High request load triggers adding instances, not shutting down [OK]
Common Mistakes:
  • Thinking instances are removed when load increases
  • Assuming CPU throttling manages request spikes
  • Believing requests queue without scaling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes