[Solved] Given this Cloud Run service configuration snippet, what happens when traffic increases? apiVersion:... Given this Cloud Run service configuration snippet, what happens when traffic increases? | GCP

GCP - Cloud Run

Given this Cloud Run service configuration snippet, what happens when traffic increases?

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: hello-service
spec:
  template:
    spec:
      containers:
      - image: gcr.io/my-project/hello-image
        resources:
          limits:
            cpu: 1
            memory: 512Mi

ACloud Run automatically creates more instances to handle the traffic.

BThe service crashes because CPU is limited to 1.

CYou must manually add more instances in the config.

DTraffic is rejected when CPU limit is reached.

Step-by-Step Solution

Solution:

Step 1: Understand Cloud Run scaling behavior
Cloud Run automatically scales container instances based on incoming traffic.
Step 2: Analyze resource limits
CPU and memory limits set max per instance but do not prevent scaling.
Final Answer:
Cloud Run automatically creates more instances to handle the traffic. -> Option A
Quick Check:
Auto scaling = more instances on traffic rise [OK]

Quick Trick: Cloud Run scales instances automatically with traffic [OK]

Common Mistakes:

Thinking CPU limit stops scaling
Believing manual scaling is required
Assuming traffic is rejected on resource limits

Master "Cloud Run" in GCP

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More GCP Quizzes

Given this Cloud Run service configuration snippet, what happens when traffic increases?

Step 1: Understand Cloud Run scaling behavior

Step 2: Analyze resource limits

Final Answer:

Quick Check:

Want More Practice?