- A
Increase the number of Dataflow workers to process messages faster.
Why wrong: The problem states there are enough workers. Adding more workers doesn't fix a bottleneck in pipeline logic (slow stage, hot partitions, external API latency).
- B
Inspect Dataflow job graph metrics to identify the slow stage, then optimize that stage's logic or address data skew.
The Dataflow job monitoring graph shows per-stage throughput and latency. Identifying the slow stage reveals the root cause (slow transform, external call, skew), enabling targeted optimization.
- C
Increase the Pub/Sub subscription's ack deadline to 600 seconds.
Why wrong: Increasing ack deadline prevents message redelivery due to slow processing but doesn't fix the throughput issue — messages still accumulate.
- D
Switch from Dataflow to Pub/Sub Lite for lower cost and higher throughput.
Why wrong: Pub/Sub Lite is a message queue, not a processing engine. It cannot replace Dataflow's transformation logic.
Quick Answer
The answer is to inspect the Dataflow job graph metrics to identify the slow stage, then optimize that stage’s logic or address data skew. A growing `oldest_unacked_message_age` in Pub/Sub, despite sufficient workers, signals that messages are being pulled but not acknowledged quickly enough, meaning a specific processing stage—not worker count—is the bottleneck. This directly tests your ability to interpret Dataflow’s streaming pipeline metrics, a common scenario on the Google Associate Cloud Engineer exam where candidates mistakenly scale workers instead of diagnosing stage-level issues like hot keys or expensive transforms. The trap is assuming more workers always fix throughput drops; in reality, a slow stage creates a backlog regardless of parallelism. Remember the mnemonic: “Oldest unacked age? Check the stage, not the page”—meaning look at stage-level wall time and backlog in the job graph before adjusting autoscaling.
Google ACE Practice Question: Ensuring successful operation of a cloud solution
This ACE practice question tests your understanding of ensuring successful operation of a cloud solution. 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.
Your Dataflow streaming pipeline is consuming messages from Pub/Sub but the pipeline's throughput has dropped significantly. Cloud Monitoring shows the `pubsub/subscription/oldest_unacked_message_age` metric is growing. The pipeline has enough workers. What is the most likely bottleneck, and how should you address it?
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
Inspect Dataflow job graph metrics to identify the slow stage, then optimize that stage's logic or address data skew.
The growing `oldest_unacked_message_age` metric indicates that messages are not being processed and acknowledged quickly enough, even though the pipeline has enough workers. This points to a bottleneck within a specific stage of the Dataflow pipeline, such as a transformation or grouping operation that is slow or suffering from data skew. Option B is correct because inspecting the job graph metrics (e.g., wall time, backlog, and throughput per stage) allows you to identify the slow stage and then optimize its logic or address data skew, which directly resolves the processing delay.
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.
- ✗
Increase the number of Dataflow workers to process messages faster.
Why it's wrong here
The problem states there are enough workers. Adding more workers doesn't fix a bottleneck in pipeline logic (slow stage, hot partitions, external API latency).
- ✓
Inspect Dataflow job graph metrics to identify the slow stage, then optimize that stage's logic or address data skew.
Why this is correct
The Dataflow job monitoring graph shows per-stage throughput and latency. Identifying the slow stage reveals the root cause (slow transform, external call, skew), enabling targeted optimization.
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.
- ✗
Increase the Pub/Sub subscription's ack deadline to 600 seconds.
Why it's wrong here
Increasing ack deadline prevents message redelivery due to slow processing but doesn't fix the throughput issue — messages still accumulate.
- ✗
Switch from Dataflow to Pub/Sub Lite for lower cost and higher throughput.
Why it's wrong here
Pub/Sub Lite is a message queue, not a processing engine. It cannot replace Dataflow's transformation logic.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that adding more workers or increasing timeouts always solves throughput issues, but the correct approach is to diagnose the specific bottleneck stage using Dataflow's built-in metrics.
Detailed technical explanation
How to think about this question
Under the hood, Dataflow uses a fused execution model where stages are separated by GroupByKey or other shuffle operations. A slow stage can be identified by high 'wall time' or 'backlog bytes' metrics in the job graph. Data skew often occurs when a hot key causes a single worker to process a disproportionate amount of data, leading to a long-tail effect that increases unacknowledged message age. Real-world scenarios include a windowed aggregation on a high-cardinality key where one key dominates, requiring techniques like key salting or reshuffling to distribute the 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
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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.
- →
Ensuring successful operation of a cloud solution — study guide chapter
Learn the concepts, then practise the questions
- →
Ensuring successful operation of a cloud solution practice questions
Targeted practice on this topic area only
- →
All ACE questions
500 questions across all exam domains
- →
Google Associate Cloud Engineer study guide
Full concept coverage aligned to exam objectives
- →
ACE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Setting up a cloud solution environment practice questions
Practise ACE questions linked to Setting up a cloud solution environment.
Planning and configuring a cloud solution practice questions
Practise ACE questions linked to Planning and configuring a cloud solution.
Deploying and implementing a cloud solution practice questions
Practise ACE questions linked to Deploying and implementing a cloud solution.
Ensuring successful operation of a cloud solution practice questions
Practise ACE questions linked to Ensuring successful operation of a cloud solution.
Configuring access and security practice questions
Practise ACE questions linked to Configuring access and security.
ACE fundamentals practice questions
Practise ACE questions linked to ACE fundamentals.
ACE scenario practice questions
Practise ACE questions linked to ACE scenario.
ACE troubleshooting practice questions
Practise ACE questions linked to ACE troubleshooting.
Practice this exam
Start a free ACE 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 ACE question test?
Ensuring successful operation of a cloud solution — This question tests Ensuring successful operation of a cloud solution — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Inspect Dataflow job graph metrics to identify the slow stage, then optimize that stage's logic or address data skew. — The growing `oldest_unacked_message_age` metric indicates that messages are not being processed and acknowledged quickly enough, even though the pipeline has enough workers. This points to a bottleneck within a specific stage of the Dataflow pipeline, such as a transformation or grouping operation that is slow or suffering from data skew. Option B is correct because inspecting the job graph metrics (e.g., wall time, backlog, and throughput per stage) allows you to identify the slow stage and then optimize its logic or address data skew, which directly resolves the processing delay.
What should I do if I get this ACE 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 →
Last reviewed: Jun 30, 2026
This ACE 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 ACE 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.