- A
Set waitFor: ['-'] on the unit tests and linting steps, and waitFor: ['unit-tests', 'linting'] on the package step.
This correctly runs unit tests and linting in parallel, then package after both complete.
- B
Do not set waitFor on any step.
Why wrong: Without waitFor, steps run sequentially by default, not in parallel.
- C
Set waitFor: ['-'] on the package step.
Why wrong: This would make the package step run immediately, not after the parallel steps.
- D
Set waitFor: ['unit-tests', 'linting'] on all three steps.
Why wrong: This would make unit tests and linting wait for each other, running them sequentially.
Question 311 of 1,000
PCDE Practice Question: Building and Implementing CI/CD Pipelines for a Service
This PCDE practice question tests your understanding of building and implementing ci/cd pipelines for a service. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
An engineer is configuring a cloudbuild.yaml file. They want two build steps (unit tests and linting) to run simultaneously, and after both complete, a third step (package) should run. How should they configure waitFor in the package step?
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
✓
Set waitFor: ['-'] on the unit tests and linting steps, and waitFor: ['unit-tests', 'linting'] on the package step.
Option A is correct because in Cloud Build, steps run sequentially by default. To run unit tests and linting in parallel, you set `waitFor: ['-']` on each of those steps, which tells Cloud Build they have no dependencies and can start immediately. Then, setting `waitFor: ['unit-tests', 'linting']` on the package step ensures it only runs after both parallel steps have completed successfully.
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.
- ✓
Set waitFor: ['-'] on the unit tests and linting steps, and waitFor: ['unit-tests', 'linting'] on the package step.
Why this is correct
This correctly runs unit tests and linting in parallel, then package after both complete.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Do not set waitFor on any step.
Why it's wrong here
Without waitFor, steps run sequentially by default, not in parallel.
- ✗
Set waitFor: ['-'] on the package step.
Why it's wrong here
This would make the package step run immediately, not after the parallel steps.
- ✗
Set waitFor: ['unit-tests', 'linting'] on all three steps.
Why it's wrong here
This would make unit tests and linting wait for each other, running them sequentially.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that `waitFor: ['-']` is used to make a step wait for nothing, but candidates confuse it with making a step wait for all previous steps, or they think omitting `waitFor` enables parallelism.
Detailed technical explanation
How to think about this question
Cloud Build uses the `waitFor` field to define explicit dependencies between build steps. The special identifier `'-'` means the step has no dependencies and can start immediately. Under the hood, Cloud Build schedules steps based on their `waitFor` lists, and steps that are not dependent on each other can run concurrently. A real-world scenario where this matters is in a monorepo with multiple services, where you might want to run linting and unit tests in parallel for different services before packaging them together.
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 Implementing CI/CD Pipelines for a Service — study guide chapter
Learn the concepts, then practise the questions
- →
Building and Implementing CI/CD Pipelines for a Service practice questions
Targeted practice on this topic area only
- →
All PCDE questions
1,000 questions across all exam domains
- →
Google Professional Cloud Database Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Building and Implementing CI/CD Pipelines for a Service practice questions
Practise PCDE questions linked to Building and Implementing CI/CD Pipelines for a Service.
Bootstrapping a Google Cloud Organisation for DevOps practice questions
Practise PCDE questions linked to Bootstrapping a Google Cloud Organisation for DevOps.
Applying Site Reliability Engineering Practices to a Service practice questions
Practise PCDE questions linked to Applying Site Reliability Engineering Practices to a Service.
Implementing Service Monitoring Strategies practice questions
Practise PCDE questions linked to Implementing Service Monitoring Strategies.
Optimising Service Performance practice questions
Practise PCDE questions linked to Optimising Service Performance.
Plan and manage database infrastructure practice questions
Practise PCDE questions linked to Plan and manage database infrastructure.
Define data structures and implement SQL for Business Intelligence practice questions
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Design and implement database schemas practice questions
Practise PCDE questions linked to Design and implement database schemas.
Monitor and optimize database performance practice questions
Practise PCDE questions linked to Monitor and optimize database performance.
PCDE fundamentals practice questions
Practise PCDE questions linked to PCDE fundamentals.
PCDE scenario practice questions
Practise PCDE questions linked to PCDE scenario.
PCDE troubleshooting practice questions
Practise PCDE questions linked to PCDE troubleshooting.
Practice this exam
Start a free PCDE 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 PCDE question test?
Building and Implementing CI/CD Pipelines for a Service — This question tests Building and Implementing CI/CD Pipelines for a Service — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set waitFor: ['-'] on the unit tests and linting steps, and waitFor: ['unit-tests', 'linting'] on the package step. — Option A is correct because in Cloud Build, steps run sequentially by default. To run unit tests and linting in parallel, you set `waitFor: ['-']` on each of those steps, which tells Cloud Build they have no dependencies and can start immediately. Then, setting `waitFor: ['unit-tests', 'linting']` on the package step ensures it only runs after both parallel steps have completed successfully.
What should I do if I get this PCDE 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 →
Last reviewed: Jul 4, 2026
This PCDE 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 PCDE 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.