- A
Increase the Cloud Run container instance request timeout
This extends the time a request can run, preventing premature termination.
- B
Increase the Pub/Sub subscription acknowledgment deadline
Why wrong: This affects message redelivery but not the Cloud Run request timeout.
- C
Enable CPU always allocation for the Cloud Run service
Why wrong: This prevents CPU throttling but does not change the request timeout.
- D
Add retry logic with exponential backoff for Firestore operations
Why wrong: Retry logic helps with transient failures but not with timeouts caused by long operations.
Question 460 of 999
Fixing DeadlineExceeded Errors from Firestore in Cloud Run by Adjusting Request Timeout
This PCD practice question tests your understanding of building and testing applications. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: cloud Run request timeout. 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 team is developing a microservice that processes messages from Pub/Sub. The service is deployed on Cloud Run and uses Cloud Firestore to store processed data. During load testing, the service frequently fails with 'DeadlineExceeded' errors from Firestore. What is the most likely cause and best practice to fix it?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.
Quick Answer
The answer is to increase the Cloud Run container instance request timeout. The DeadlineExceeded error from Firestore occurs because the Cloud Run instance is terminated before the Firestore write operation completes, as the default request timeout of five minutes is too short for the processing load. This is a common pitfall on the Google Professional Cloud Developer exam, where candidates often misdiagnose the error as a Firestore client-side timeout or a Pub/Sub acknowledgment issue, but the root cause is the Cloud Run runtime killing the container mid-operation. The exam tests your understanding that Cloud Run’s timeout governs the entire request lifecycle, and Firestore’s client timeout is separate but rarely the culprit in this scenario. To remember: think of Cloud Run as the bouncer—if it kicks the container out too early, Firestore never gets to finish its work.
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
✓
Increase the Cloud Run container instance request timeout
The 'DeadlineExceeded' error is raised by the Firestore client-side SDK when the operation exceeds its default timeout (e.g., 60 seconds). However, the underlying cause in this Cloud Run environment is that the default Cloud Run request timeout (5 minutes) is too short for the entire processing pipeline, causing the container to be terminated before the Firestore operation completes. When the container is terminated, the pending Firestore request fails with 'DeadlineExceeded'. Increasing the Cloud Run request timeout prevents premature termination, allowing the Firestore operation to finish within the container's lifetime. This is the most direct fix, as it addresses the infrastructure timeout that triggers the client-side error.
Key principle: Cloud Run request timeout
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 Cloud Run container instance request timeout
Why this is correct
This extends the time a request can run, preventing premature termination.
Clue confirmation
The clue words "best", "most likely" in the question point toward this answer.
Related concept
Cloud Run request timeout
- ✗
Increase the Pub/Sub subscription acknowledgment deadline
Why it's wrong here
This affects message redelivery but not the Cloud Run request timeout.
- ✗
Enable CPU always allocation for the Cloud Run service
Why it's wrong here
This prevents CPU throttling but does not change the request timeout.
- ✗
Add retry logic with exponential backoff for Firestore operations
Why it's wrong here
Retry logic helps with transient failures but not with timeouts caused by long operations.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates often confuse client-side timeouts (e.g., Firestore SDK timeout) with infrastructure-level timeouts (e.g., Cloud Run request timeout). While the error message comes from the Firestore client, the root cause is the Cloud Run timeout that kills the instance before the Firestore call completes. Simply increasing the Firestore client timeout or adding retries would not help because the container itself is being terminated.
Detailed technical explanation
How to think about this question
Cloud Run enforces a maximum request timeout of 60 minutes (configurable up to 3600 seconds), and if a request exceeds this timeout, the container is terminated, causing any in-flight Firestore operations to fail with 'DeadlineExceeded'. Firestore client libraries have their own default timeout (e.g., 60 seconds for gRPC), but the Cloud Run timeout is the outer bound; if the container is killed, the Firestore operation never completes. In practice, long-running Firestore transactions or batch writes that exceed the Cloud Run timeout are common culprits, especially under load when Firestore may throttle or take longer to commit.
KKey Concepts to Remember
- Cloud Run request timeout
- Firestore client-side DeadlineExceeded
- Timeout chaining
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
Cloud Run request timeout
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. Cloud Run request timeout 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.
Review cloud Run request timeout, then practise related PCD questions on the same topic to reinforce the concept.
- →
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
999 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.
Manage a Solution that Can Span Multiple Database Systems practice questions
Practise PCD questions linked to Manage a Solution that Can Span Multiple Database Systems.
Deploy Scalable and Highly Available Databases in Google Cloud practice questions
Practise PCD questions linked to Deploy Scalable and Highly Available Databases in Google Cloud.
Design Scalable and Highly Available Cloud Database Solutions practice questions
Practise PCD questions linked to Design Scalable and Highly Available Cloud Database Solutions.
Migrate Data Solutions practice questions
Practise PCD questions linked to Migrate Data Solutions.
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 — Cloud Run request timeout.
What is the correct answer to this question?
The correct answer is: Increase the Cloud Run container instance request timeout — The 'DeadlineExceeded' error is raised by the Firestore client-side SDK when the operation exceeds its default timeout (e.g., 60 seconds). However, the underlying cause in this Cloud Run environment is that the default Cloud Run request timeout (5 minutes) is too short for the entire processing pipeline, causing the container to be terminated before the Firestore operation completes. When the container is terminated, the pending Firestore request fails with 'DeadlineExceeded'. Increasing the Cloud Run request timeout prevents premature termination, allowing the Firestore operation to finish within the container's lifetime. This is the most direct fix, as it addresses the infrastructure timeout that triggers the client-side error.
What should I do if I get this PCD question wrong?
Review cloud Run request timeout, then practise related PCD questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "best", "most likely". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Cloud Run request timeout
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…
- A Cloud Bigtable instance has a single cluster. To improve availability and read throughput, the team decides to add a s…
- A developer wants to enable IAM database authentication for Cloud SQL for PostgreSQL. Which IAM role must be granted to…
- A company is using Cloud Bigtable for a time-series workload. They want to monitor performance and identify hot spots. W…
- A company wants to run hybrid transactional/analytical processing (HTAP) workloads on a PostgreSQL-compatible database w…
Last reviewed: Jun 30, 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.