Question 271 of 500
Building and implementing CI/CD pipelinesmediumMultiple SelectObjective-mapped

Quick Answer

The answer is to use Cloud Build substitutions to parameterize build configurations for different environments and to use a Dockerfile to define the build process for containerized applications. These two practices are recommended for implementing CI/CD pipelines on Google Cloud because they enforce consistency and reusability across your deployment lifecycle. Cloud Build substitutions allow you to inject environment-specific variables—like project IDs or service endpoints—into a single pipeline template, eliminating the need for separate pipeline definitions per environment. Meanwhile, using a Dockerfile ensures that every build produces an identical container image, leveraging Cloud Build’s native support to store the artifact in Artifact Registry. On the Google Professional Cloud DevOps Engineer exam, this tests your understanding of pipeline parameterization and immutable infrastructure; a common trap is choosing manual environment overrides or hardcoded configurations. Remember the memory tip: “Substitute for flexibility, Dockerfile for consistency.”

PCDOE Building and implementing CI/CD pipelines Practice Question

This PCDOE practice question tests your understanding of building and implementing ci/cd pipelines. 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.

Which TWO practices are recommended for implementing CI/CD pipelines on Google Cloud?

Question 1mediummulti select
Full question →

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 a Dockerfile to define the build process for containerized applications.

Option D is correct because using a Dockerfile to define the build process for containerized applications is a recommended practice in CI/CD pipelines on Google Cloud. It ensures that the application is built consistently across all environments, leveraging Cloud Build's native support for Dockerfiles to produce container images that can be stored in Container Registry or Artifact Registry.

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.

  • Store service account keys in the build configuration file for authentication.

    Why it's wrong here

    Hardcoding keys is insecure; use Secret Manager or workload identity.

  • Deploy to production directly after a successful build without any approval gate.

    Why it's wrong here

    CI/CD best practice includes approval gates for production.

  • Create a single build pipeline that handles all microservices to reduce complexity.

    Why it's wrong here

    Monolithic pipelines reduce independence and slow down deployment.

  • Use a Dockerfile to define the build process for containerized applications.

    Why this is correct

    Dockerfile is the standard way to define container builds.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use Cloud Build substitutions to parameterize build configurations for different environments.

    Why this is correct

    Substitutions make pipelines reusable across environments.

    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 misconception that a single monolithic pipeline is simpler and thus better, but the correct approach is to decouple microservices into separate pipelines for isolation and independent release cycles.

Detailed technical explanation

How to think about this question

Cloud Build uses Dockerfiles to automatically detect the build context and execute steps like `docker build` and `docker push`; you can also use `cloudbuild.yaml` for multi-step builds. Substitutions (Option E) allow parameterization of environment-specific values (e.g., `_REGION`, `_TAG`) at build time, enabling a single pipeline to deploy to dev, staging, and prod without hardcoding. In practice, teams often combine Dockerfiles with Cloud Build triggers and Artifact Registry for immutable, versioned artifacts.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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.

Related practice questions

Related PCDOE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCDOE 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 PCDOE question test?

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: Use a Dockerfile to define the build process for containerized applications. — Option D is correct because using a Dockerfile to define the build process for containerized applications is a recommended practice in CI/CD pipelines on Google Cloud. It ensures that the application is built consistently across all environments, leveraging Cloud Build's native support for Dockerfiles to produce container images that can be stored in Container Registry or Artifact Registry.

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.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

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.