Bird
0
0

A developer sets targetConcurrency to 20 but the service keeps scaling too high. What is a likely misconfiguration?

medium📝 Debug Q6 of 15
GCP - Cloud Run
A developer sets targetConcurrency to 20 but the service keeps scaling too high. What is a likely misconfiguration?
AMinimum instances set too high, preventing scale down
BTarget concurrency set too low, causing scale up
CCPU utilization threshold is too high
DMaximum instances set to zero
Step-by-Step Solution
Solution:

  1. Step 1: Analyze scaling behavior

    Service scales too high despite target concurrency set to 20.

  2. Step 2: Identify misconfiguration

    If minimum instances is set too high, service cannot scale down, causing high instance count.

  3. Final Answer:

    Minimum instances set too high, preventing scale down -> Option A

  4. Quick Check:

    High minimum instances block scaling down [OK]
Quick Trick: Check minimum instances if scaling stays high unexpectedly [OK]
Common Mistakes:
  • Confusing target concurrency effect
  • Checking CPU instead of request concurrency
  • Setting maximum instances to zero (invalid)

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes
Cloud Firestore and Bigtable - Firestore document model - Quiz 9hard Cloud Functions - Function deployment and testing - Quiz 15hard Cloud Load Balancing - Why load balancing matters - Quiz 13medium Cloud Load Balancing - Load balancer types comparison - Quiz 13medium Cloud Load Balancing - HTTP(S) Load Balancer (Layer 7) - Quiz 9hard Cloud Load Balancing - Why load balancing matters - Quiz 11easy Cloud Monitoring and Logging - Metrics and dashboards - Quiz 2easy Cloud Monitoring and Logging - Alerting policies - Quiz 9hard Cloud Pub/Sub - Publishing messages - Quiz 14medium Cloud SQL and Databases - Why managed databases matter - Quiz 12easy