The answer is to increase the timeout value in the Cloud Build configuration. The "context deadline exceeded" error occurs because the custom vulnerability scan step exceeds the build's hard timeout of 600 seconds, causing Cloud Build to terminate the entire pipeline. This tests your understanding of Cloud Build's execution lifecycle and timeout enforcement, a common scenario on the Google Professional Cloud DevOps Engineer exam where builds fail due to resource-intensive custom steps. A frequent trap is misdiagnosing the error as a network or permission issue, but the error message directly points to a time constraint. Remember the memory tip: "Deadline exceeded equals time needed exceeded"—always check the build's timeout duration against the step's actual runtime before troubleshooting other factors.
PCDOE Building and implementing CI/CD pipelines Practice Question
This PCDOE practice question tests your understanding of building and implementing ci/cd pipelines. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 is troubleshooting a Cloud Build pipeline that fails intermittently when building a container image. The build step uses a custom build step that runs a vulnerability scan. The error log shows: 'Step #1: Error: failed to scan image: context deadline exceeded'. The build configuration includes 'timeout: 600s'. Which is the most likely cause and solution?
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 the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The scan step is taking longer than the build timeout; increase the timeout value in the build configuration.
The error 'context deadline exceeded' indicates that the custom vulnerability scan step is taking longer than the build's configured timeout of 600 seconds. Cloud Build enforces a hard timeout for the entire build; if any step exceeds this duration, the build is terminated. Increasing the timeout value in the build configuration provides more time for the scan to complete, directly addressing the root cause.
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 scan tool requires a specific dependency; add an installation step before scanning.
Why it's wrong here
Missing dependency would cause command not found or similar errors.
✗
There is network latency between Cloud Build and the container registry; use VPC Service Controls.
Why it's wrong here
Network latency would cause connection errors, not a deadline exceeded within the build.
✗
The build step is running out of memory; increase the machine type to e2-highcpu-8.
Why it's wrong here
Memory issues would produce out-of-memory errors, not timeout.
✓
The scan step is taking longer than the build timeout; increase the timeout value in the build configuration.
Why this is correct
The error 'context deadline exceeded' indicates the step timed out.
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between resource exhaustion (memory/CPU) and timeout errors, leading candidates to mistakenly select machine type upgrades when the error message explicitly indicates a deadline exceeded.
Trap categories for this question
Similar concept trap
Missing dependency would cause command not found or similar errors.
Command / output trap
Missing dependency would cause command not found or similar errors.
Detailed technical explanation
How to think about this question
Cloud Build's timeout is enforced at the build level, not per step, and defaults to 10 minutes if not specified. The 'context deadline exceeded' error is a Go-style error from the scan tool's HTTP client or internal context, indicating the operation exceeded its own deadline, which is often tied to the parent build's timeout. In practice, vulnerability scans of large images (e.g., multi-GB base images) can easily exceed 600 seconds, especially when pulling layers or analyzing deep file systems.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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 implementing CI/CD pipelines — This question tests Building and implementing CI/CD pipelines — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The scan step is taking longer than the build timeout; increase the timeout value in the build configuration. — The error 'context deadline exceeded' indicates that the custom vulnerability scan step is taking longer than the build's configured timeout of 600 seconds. Cloud Build enforces a hard timeout for the entire build; if any step exceeds this duration, the build is terminated. Increasing the timeout value in the build configuration provides more time for the scan to complete, directly addressing the root cause.
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 →
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.
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.