- A
The concurrency setting is too low, causing many instances to be created.
Low concurrency increases instance count, each handling few requests, causing underutilization.
- B
The max instances limit is set too low, causing requests to queue.
Why wrong: If max instances were too low, the instance count would be capped, not spiked.
- C
The service uses too much memory, causing cold starts.
Why wrong: Memory issues would show in memory metrics, not CPU utilization.
- D
The CPU utilization target for autoscaling is set too high, causing slow scaling.
Why wrong: A high CPU target would delay scaling, leading to high latency but not high instance count.
PCDOE Optimizing service performance Practice Question
This PCDOE practice question tests your understanding of optimizing service performance. 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.
A DevOps team uses Cloud Run for a containerized application that processes real-time financial data. The service has a concurrency setting of 80, and instances are scaled based on CPU usage. During market volatility, the service experiences high latency and some requests timeout. Cloud Monitoring shows that the average CPU utilization is 40%, but the instance count spikes to the maximum allowed. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The concurrency setting is too low, causing many instances to be created.
With a concurrency setting of 80, each instance can handle up to 80 simultaneous requests. However, if the actual request rate exceeds 80 per instance, Cloud Run will spin up new instances. During market volatility, the request volume spikes, causing the instance count to hit the maximum even though average CPU utilization is only 40%. This indicates that the concurrency limit is too low for the burst traffic, forcing excessive instance creation and leading to high latency and timeouts due to instance startup overhead.
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 concurrency setting is too low, causing many instances to be created.
Why this is correct
Low concurrency increases instance count, each handling few requests, causing underutilization.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The max instances limit is set too low, causing requests to queue.
Why it's wrong here
If max instances were too low, the instance count would be capped, not spiked.
- ✗
The service uses too much memory, causing cold starts.
Why it's wrong here
Memory issues would show in memory metrics, not CPU utilization.
- ✗
The CPU utilization target for autoscaling is set too high, causing slow scaling.
Why it's wrong here
A high CPU target would delay scaling, leading to high latency but not high instance count.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that CPU utilization is the primary driver of Cloud Run scaling, when in fact concurrency settings and request queuing are the dominant factors in burst scenarios.
Trap categories for this question
Command / output trap
Memory issues would show in memory metrics, not CPU utilization.
Detailed technical explanation
How to think about this question
Cloud Run's autoscaler uses the concurrency setting as a key input: it aims to keep the number of concurrent requests per instance at or below the configured value. When traffic bursts exceed this threshold, the scaler creates new instances, but each new instance incurs a cold start penalty (container startup, health checks). In real-time financial data processing, even a few seconds of cold start can cause timeouts, especially if the burst is short-lived and the scaler over-provisions. The 40% average CPU utilization indicates that instances are underutilized on CPU but are being created due to concurrency pressure, not CPU load.
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.
- →
Optimizing service performance — study guide chapter
Learn the concepts, then practise the questions
- →
Optimizing service performance practice questions
Targeted practice on this topic area only
- →
All PCDOE questions
500 questions across all exam domains
- →
Google Professional Cloud DevOps Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDOE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDOE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Bootstrapping a Google Cloud organization for DevOps practice questions
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Managing service incidents practice questions
Practise PCDOE questions linked to Managing service incidents.
Managing Google Cloud costs practice questions
Practise PCDOE questions linked to Managing Google Cloud costs.
Building and implementing CI/CD pipelines practice questions
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Implementing service monitoring strategies practice questions
Practise PCDOE questions linked to Implementing service monitoring strategies.
Optimizing service performance practice questions
Practise PCDOE questions linked to Optimizing service performance.
PCDOE fundamentals practice questions
Practise PCDOE questions linked to PCDOE fundamentals.
PCDOE scenario practice questions
Practise PCDOE questions linked to PCDOE scenario.
PCDOE troubleshooting practice questions
Practise PCDOE questions linked to PCDOE troubleshooting.
Practice this exam
Start a free PCDOE 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 PCDOE question test?
Optimizing service performance — This question tests Optimizing service performance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The concurrency setting is too low, causing many instances to be created. — With a concurrency setting of 80, each instance can handle up to 80 simultaneous requests. However, if the actual request rate exceeds 80 per instance, Cloud Run will spin up new instances. During market volatility, the request volume spikes, causing the instance count to hit the maximum even though average CPU utilization is only 40%. This indicates that the concurrency limit is too low for the burst traffic, forcing excessive instance creation and leading to high latency and timeouts due to instance startup overhead.
What should I do if I get this PCDOE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Keep practising
More PCDOE practice questions
- Order the steps to set up a CI/CD pipeline using Cloud Build and Cloud Deploy for a Cloud Run service.
- Order the steps to configure a VPC Network Peering between two projects.
- Order the steps to respond to a Google Cloud security incident involving a compromised service account key.
- Refer to the exhibit. The Cloud Build fails with a permission error. The Cloud Build service account has roles/cloudbuil…
- A company is setting up a new Google Cloud organization. They want to ensure that all projects inherit common IAM polici…
- A DevOps team is bootstrapping CI/CD pipelines that need access to API keys stored in Secret Manager. The pipelines run…
Last reviewed: Jun 30, 2026
This PCDOE 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 PCDOE 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.