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.
During a Cloud Build execution, a step fails due to timeout. What is the first thing to check?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Check network connectivity
Why wrong: Network issues can cause timeouts, but logs will reveal that.
Check the build logs for errors
Logs provide details on what caused the step to hang or fail.
Increase machine type for the build
Why wrong: This might help but not until the cause is understood.
Increase the timeout in cloudbuild.yaml
Why wrong: Increasing timeout may mask the underlying issue.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Check the build logs for errors
When a Cloud Build step fails due to a timeout, the build logs are the first and most authoritative source of diagnostic information. They contain the exact error messages, exit codes, and step output that reveal why the step exceeded its timeout — for example, a hanging command, a missing dependency, or a resource contention issue. Checking logs before making any configuration changes ensures you address the root cause rather than treating symptoms.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Check network connectivity
Why it's wrong here
Network issues can cause timeouts, but logs will reveal that.
Check the build logs for errors
Why this is correct
Logs provide details on what caused the step to hang or fail.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Increase machine type for the build
Why it's wrong here
This might help but not until the cause is understood.
Increase the timeout in cloudbuild.yaml
Why it's wrong here
Increasing timeout may mask the underlying issue.
Common exam traps
Google Cloud often tests the misconception that a timeout is always a performance or configuration issue, leading candidates to jump to increasing resources or timeout values, when the correct first step is always to inspect the build logs for the actual error.
Detailed technical explanation
Cloud Build steps run in Docker containers, and the timeout is enforced by the Cloud Build service at the step level (default 10 minutes, configurable up to 24h). When a step times out, the container is killed with SIGTERM and the build status is set to TIMEOUT; the logs capture the last output before termination, which often includes the exact command that was running. In real-world scenarios, a common cause is a `gcloud` command waiting for a long-running operation (e.g., a deployment) without a `--async` flag, or a script that enters an infinite loop due to a missing exit condition — both are immediately visible in the logs.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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 — study guide chapter
Learn the concepts, then practise the questions
Building and implementing CI/CD pipelines 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Practise PCDOE questions linked to Managing service incidents.
Practise PCDOE questions linked to Managing Google Cloud costs.
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Practise PCDOE questions linked to Implementing service monitoring strategies.
Practise PCDOE questions linked to Optimizing service performance.
Practise PCDOE questions linked to PCDOE fundamentals.
Practise PCDOE questions linked to PCDOE scenario.
Practise PCDOE questions linked to PCDOE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Building and implementing CI/CD pipelines — This question tests Building and implementing CI/CD pipelines — Read the scenario before looking for a memorised answer..
The correct answer is: Check the build logs for errors — When a Cloud Build step fails due to a timeout, the build logs are the first and most authoritative source of diagnostic information. They contain the exact error messages, exit codes, and step output that reveal why the step exceeded its timeout — for example, a hanging command, a missing dependency, or a resource contention issue. Checking logs before making any configuration changes ensures you address the root cause rather than treating symptoms.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 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.