- A
The maximum number of instances can be set to 'default' which is unlimited.
Why wrong: The default max instances is 100; you can set a higher value but there is no unlimited setting.
- B
You can set a minimum number of instances to ensure zero cold starts.
Why wrong: Min instances reduce cold starts but don't guarantee zero; traffic bursts beyond warm instances can still cause cold starts.
- C
You can define a target concurrency to control how many requests each container instance handles.
Container concurrency setting controls the maximum number of concurrent requests per instance.
- D
The number of container instances can be scaled to zero when there is no traffic.
Cloud Run automatically scales down to zero if min instances is 0 and no traffic.
- E
Autoscaling uses CPU and memory utilization to make decisions.
Why wrong: Cloud Run autoscaling is based on request concurrency, not CPU or memory utilization.
Cloud Digital Leader Scaling with Google Cloud operations Practice Question
This GCDL practice question tests your understanding of scaling with google cloud operations. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO statements correctly describe Cloud Run scaling behavior?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
You can define a target concurrency to control how many requests each container instance handles.
Option C is correct because Cloud Run allows you to set a target concurrency (the number of simultaneous requests a single container instance can handle). This is a key scaling parameter that controls how many requests are routed to each instance before Cloud Run spins up additional instances. By default, concurrency is set to 80, but you can adjust it up to 1000 or set it to 1 for sequential processing.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The maximum number of instances can be set to 'default' which is unlimited.
Why it's wrong here
The default max instances is 100; you can set a higher value but there is no unlimited setting.
- ✗
You can set a minimum number of instances to ensure zero cold starts.
Why it's wrong here
Min instances reduce cold starts but don't guarantee zero; traffic bursts beyond warm instances can still cause cold starts.
- ✓
You can define a target concurrency to control how many requests each container instance handles.
Why this is correct
Container concurrency setting controls the maximum number of concurrent requests per instance.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
The number of container instances can be scaled to zero when there is no traffic.
Why this is correct
Cloud Run automatically scales down to zero if min instances is 0 and no traffic.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Autoscaling uses CPU and memory utilization to make decisions.
Why it's wrong here
Cloud Run autoscaling is based on request concurrency, not CPU or memory utilization.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that Cloud Run uses CPU or memory utilization for autoscaling, when in fact it uses request concurrency as the primary metric, and candidates may incorrectly select Option E because they associate autoscaling with resource metrics from other services.
Detailed technical explanation
How to think about this question
Cloud Run's autoscaler uses a request-based scaling model: it monitors the number of concurrent requests and compares it to the target concurrency setting. If the average concurrency per instance exceeds the target, new instances are created; if it falls below, instances are removed. This is fundamentally different from CPU/memory-based autoscaling used in Google Kubernetes Engine or Compute Engine. A real-world scenario: if you set target concurrency to 10 and each instance can handle 10 requests simultaneously, the autoscaler will keep the number of instances such that the average concurrency per instance stays near 10, scaling up only when demand exceeds that threshold.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Scaling with Google Cloud operations — study guide chapter
Learn the concepts, then practise the questions
- →
Scaling with Google Cloud operations practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: You can define a target concurrency to control how many requests each container instance handles. — Option C is correct because Cloud Run allows you to set a target concurrency (the number of simultaneous requests a single container instance can handle). This is a key scaling parameter that controls how many requests are routed to each instance before Cloud Run spins up additional instances. By default, concurrency is set to 80, but you can adjust it up to 1000 or set it to 1 for sequential processing.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.