GCP - Cloud RunIn GCP request-based auto scaling, what happens if the average requests per instance exceed the target concurrency?AInstances are shut down to save costBMore instances are added to handle the loadCCPU throttling is applied to existing instancesDRequests are queued indefinitelyCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand scaling triggerIf the average requests per instance exceed the target concurrency, the system needs to add capacity.Step 2: Identify scaling actionThe system adds more instances to distribute the load and maintain performance.Final Answer:More instances are added to handle the load -> Option BQuick 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 increasesAssuming CPU throttling manages request spikesBelieving requests queue without scaling
Master "Cloud Run" in GCP9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
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