Courseiva

Cloud Digital Leader Why cloud technology is transforming business Practice Question

Match each Google Cloud DevOps tool to its purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Continuous integration/continuous delivery (CI/CD)

Managed continuous delivery for applications

Store and manage container images and packages

Private Git repositories hosted on GCP

Monitoring, logging, and diagnostics suite

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

Cloud Build: Continuous integration/continuous delivery platform that executes builds in the cloud.

Key Google Cloud DevOps tools include Cloud Build for CI/CD, Container Registry for container image storage, Cloud Deployment Manager for infrastructure as code, and Cloud Source Repositories for version control. Common confusions often arise between Container Registry and Cloud Build, or between Cloud Source Repositories and Deployment Manager.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cloud Build: Continuous integration/continuous delivery platform that executes builds in the cloud.

    Why this is correct

    Cloud Build is Google Cloud's serverless CI/CD platform that compiles source code, runs tests, and produces artifacts in a fully managed execution environment. It supports build triggers from Cloud Source Repositories, GitHub, and Bitbucket, and can deploy to various Google Cloud services like Compute Engine and GKE. Its purpose is to automate the software delivery pipeline, not to store images or define infrastructure.

  • Container Registry: Private container image registry for storing and managing Docker images.

    Why this is correct

    Container Registry (now Artifact Registry) is a private, fully managed repository for storing, managing, and scanning Docker container images. It provides fine-grained IAM access control and integrates seamlessly with Cloud Build, Google Kubernetes Engine, and other Google Cloud services. Its role is securing and distributing container artifacts, which is fundamentally different from building code or provisioning infrastructure.

  • Cloud Deployment Manager: Infrastructure management service that allows you to define and deploy Google Cloud resources using declarative templates.

    Why this is correct

    Cloud Deployment Manager is an infrastructure management service that lets you define your Google Cloud resources in declarative templates (YAML or Python). It handles the creation, updating, and deletion of related resources as a unit, enabling repeatable and consistent infrastructure-as-code deployments. This is distinct from CI/CD, container storage, or version control; it's about orchestrating resource lifecycle.

  • Cloud Source Repositories: Private Git repositories hosted on Google Cloud.

    Why this is correct

    Cloud Source Repositories are fully managed, private Git repositories hosted on Google Cloud, providing version control for code. They integrate with IAM for access control and can trigger Cloud Build builds on pushes, connecting source management to CI/CD. This service focuses exclusively on hosting and securing code history, not on building, storing artifacts, or deploying infrastructure.

  • Cloud Build: Private container image registry for storing and managing Docker images.

    Why it's wrong here

    This definition incorrectly assigns the purpose of Container Registry to Cloud Build. Cloud Build is not a registry; it performs compilation, testing, and packaging as part of a CI/CD pipeline, and often outputs images to a registry like Container Registry. The storage and management of Docker images—including versioning, access control, and vulnerability scanning—is the job of Container Registry, not Cloud Build.

  • Cloud Deployment Manager: Private Git repositories hosted on Google Cloud.

    Why it's wrong here

    This statement confuses Cloud Deployment Manager with Cloud Source Repositories. Cloud Deployment Manager is not a Git hosting service; it is an infrastructure-as-code tool that uses declarative templates to define and deploy Google Cloud resources. Git repository hosting, with version control and collaboration features, is provided by Cloud Source Repositories, making this definition entirely mismatched.

About these practice questions

One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This GCDL 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 GCDL exam.