- A
Use a Cloud Tasks queue to decouple the Pub/Sub push and process messages with retries.
Why wrong: Cloud Tasks has a 30-minute timeout by default (configurable up to 24 hours), but this adds latency and complexity; it's better to use Cloud Run jobs directly.
- B
Increase the Cloud Run request timeout to 120 minutes.
Why wrong: Cloud Run services have a maximum timeout of 60 minutes; you cannot set it higher.
- C
Use Cloud Run jobs instead of services to handle the processing asynchronously.
Cloud Run jobs can run for up to 24 hours, suitable for long processing, and they don't have a request timeout.
- D
Set up a second subscription to Pub/Sub with a different push endpoint to parallelize processing.
Why wrong: Parallelizing doesn't solve the timeout issue; each push endpoint still faces the 60-minute timeout.
Quick Answer
The answer is to use Cloud Run jobs instead of services to handle the processing asynchronously. This is correct because Cloud Run services enforce a hard 60-minute request timeout, which can cause message loss during spikes when long-running async processing exceeds that limit. Cloud Run jobs, by contrast, are designed for batch workloads that can run for up to 24 hours, allowing your container to pull messages from Pub/Sub, process them without interruption, and acknowledge them only after completion. On the Google Professional Cloud Developer exam, this scenario tests your understanding of the fundamental architectural difference between Cloud Run services (request-driven, short-lived) and Cloud Run jobs (task-driven, long-lived). A common trap is choosing to increase the timeout, but Cloud Run services cap at 60 minutes regardless of configuration. Another trap is overcomplicating with Cloud Tasks or additional subscriptions when the native job solution is simpler and more reliable. Memory tip: think “Jobs for long jobs, services for short requests”—if processing can outlast a lunch break, it belongs in a job.
PCD Building and testing applications Practice Question
This PCD practice question tests your understanding of building and testing applications. 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 team has developed a containerized application that processes streaming data from Pub/Sub. The application is deployed on Cloud Run. Under normal load, it processes messages within seconds. However, during spikes, processing time increases and some messages are not acknowledged before the Cloud Run request timeout of 60 minutes. You need to ensure that all messages are processed reliably without losing data. You have the following options: A) Increase the Cloud Run request timeout to 120 minutes. B) Use Cloud Run jobs instead of services to handle the processing asynchronously. C) Set up a second subscription to Pub/Sub with a different push endpoint to parallelize processing. D) Use a Cloud Tasks queue to decouple the Pub/Sub push and process messages with retries. Which option should you choose?
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
Use Cloud Run jobs instead of services to handle the processing asynchronously.
Option C is correct because Cloud Run jobs are designed for asynchronous, batch-style processing that can run longer than the 60-minute request timeout of Cloud Run services. By using a job, you can pull messages from Pub/Sub, process them without a hard timeout, and acknowledge them only after successful processing, ensuring reliable message handling during spikes.
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.
- ✗
Use a Cloud Tasks queue to decouple the Pub/Sub push and process messages with retries.
Why it's wrong here
Cloud Tasks has a 30-minute timeout by default (configurable up to 24 hours), but this adds latency and complexity; it's better to use Cloud Run jobs directly.
- ✗
Increase the Cloud Run request timeout to 120 minutes.
Why it's wrong here
Cloud Run services have a maximum timeout of 60 minutes; you cannot set it higher.
- ✓
Use Cloud Run jobs instead of services to handle the processing asynchronously.
Why this is correct
Cloud Run jobs can run for up to 24 hours, suitable for long processing, and they don't have a request timeout.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Set up a second subscription to Pub/Sub with a different push endpoint to parallelize processing.
Why it's wrong here
Parallelizing doesn't solve the timeout issue; each push endpoint still faces the 60-minute timeout.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Cloud Run services (which have a 60-minute timeout and are request-driven) with Cloud Run jobs (which are asynchronous and have no such timeout), leading them to incorrectly choose increasing the timeout or adding subscriptions instead of switching to the job execution model.
Detailed technical explanation
How to think about this question
Cloud Run jobs run as tasks that can execute for up to 24 hours, making them ideal for long-running or variable-duration workloads. Under the hood, Pub/Sub push subscriptions send messages to an HTTP endpoint, and if the endpoint does not return a 200/201/204 status within the acknowledgment deadline (default 10 seconds, extendable up to 600 seconds), the message is redelivered. Cloud Run jobs decouple this by pulling messages via the Pub/Sub client library, allowing manual acknowledgment only after processing completes, which prevents data loss during spikes.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
- →
Building and testing applications — study guide chapter
Learn the concepts, then practise the questions
- →
Building and testing applications practice questions
Targeted practice on this topic area only
- →
All PCD questions
500 questions across all exam domains
- →
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
- →
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Designing highly scalable, available, and reliable cloud-native applications practice questions
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Building and testing applications practice questions
Practise PCD questions linked to Building and testing applications.
Deploying applications practice questions
Practise PCD questions linked to Deploying applications.
Integrating Google Cloud services practice questions
Practise PCD questions linked to Integrating Google Cloud services.
Managing application performance monitoring practice questions
Practise PCD questions linked to Managing application performance monitoring.
PCD fundamentals practice questions
Practise PCD questions linked to PCD fundamentals.
PCD scenario practice questions
Practise PCD questions linked to PCD scenario.
PCD troubleshooting practice questions
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Start a free PCD 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 PCD question test?
Building and testing applications — This question tests Building and testing applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Cloud Run jobs instead of services to handle the processing asynchronously. — Option C is correct because Cloud Run jobs are designed for asynchronous, batch-style processing that can run longer than the 60-minute request timeout of Cloud Run services. By using a job, you can pull messages from Pub/Sub, process them without a hard timeout, and acknowledge them only after successful processing, ensuring reliable message handling during spikes.
What should I do if I get this PCD 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 →
Keep practising
More PCD practice questions
- A company is deploying a microservices architecture on GKE. They need to expose a set of related microservices under a s…
- You need to monitor the CPU usage of a Compute Engine instance and trigger an alert when it exceeds 80% for 5 minutes. W…
- Match each Firebase feature to its description.
- Drag and drop the steps to create a Cloud Run service in the correct order.
- Drag and drop the steps to deploy a containerized application to Google Kubernetes Engine (GKE) in the correct order.
- Drag and drop the steps to set up a Cloud SQL instance with a private IP in the correct order.
Last reviewed: Jun 11, 2026
This PCD 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 PCD 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.