Bird
0
0

A Cloud Run service YAML sets containerConcurrency: "ten" instead of 10. What is the likely result?

medium📝 Debug Q6 of 15
GCP - Cloud Functions
A Cloud Run service YAML sets containerConcurrency: "ten" instead of 10. What is the likely result?
AService runs with default concurrency
BDeployment fails due to invalid type
CService runs with concurrency set to 0
DService ignores concurrency setting
Step-by-Step Solution
Solution:

  1. Step 1: Check data type for containerConcurrency

    containerConcurrency expects an integer value, not a string.

  2. Step 2: Understand deployment validation

    Invalid type causes deployment to fail with error.

  3. Final Answer:

    Deployment fails due to invalid type -> Option B

  4. Quick Check:

    containerConcurrency must be integer, else deployment error [OK]
Quick Trick: Use integer values for containerConcurrency in YAML [OK]
Common Mistakes:
  • Using strings instead of numbers
  • Assuming default values apply silently
  • Ignoring deployment errors

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes
Cloud Firestore and Bigtable - Why NoSQL on GCP matters - Quiz 9hard Cloud IAM Advanced - IAM deny policies - Quiz 9hard Cloud Monitoring and Logging - Alerting policies - Quiz 12easy Cloud Pub/Sub - Pub/Sub with Cloud Functions integration - Quiz 5medium Cloud Pub/Sub - Pub/Sub vs Cloud Tasks - Quiz 5medium Cloud Run - Why Cloud Run matters for containers - Quiz 8hard Cloud Run - Cloud Run vs Cloud Functions decision - Quiz 13medium Cloud Run - Deploying container images - Quiz 13medium Cloud SQL and Databases - High availability configuration - Quiz 7medium Cloud SQL and Databases - Backup and restore - Quiz 11easy