Cloud Build for CI/CD in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Cloud Build trigger creation output

What is the output when you run this command to create a Cloud Build trigger for a GitHub repo?

GCP

gcloud beta builds triggers create github --repo-name=my-repo --repo-owner=my-user --branch-pattern=main --build-config=cloudbuild.yaml

A Created trigger [my-repo-trigger] for repository [my-user/my-repo] on branch [main].

B ERROR: (gcloud.beta.builds.triggers.create.github) argument --repo-name: Must be specified.

C Trigger creation failed: branch pattern 'main' is invalid.

D Permission denied: User does not have roles/cloudbuild.builds.editor.

💡 Hint

Check the command syntax and required flags for creating a GitHub trigger.

The command correctly creates a trigger for the GitHub repo on the main branch using the specified build config file.

❓ Configuration

intermediate

Cloud Build YAML step syntax

Which Cloud Build YAML snippet correctly defines a build step that runs a Docker build command?

A

steps:
- executor: 'gcr.io/cloud-builders/docker'
  params: ['build', '-t', 'gcr.io/my-project/my-image', '.']

B

]'.' ,'egami-ym/tcejorp-ym/oi.rcg' ,'t-' ,'dliub'[ :sgra  
'rekcod/sredliub-duolc/oi.rcg' :eman -
:spets

C

steps:
- container: 'gcr.io/cloud-builders/docker'
  run: ['build', '-t', 'gcr.io/my-project/my-image', '.']

D

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '-t', 'gcr.io/my-project/my-image', '.']

💡 Hint

Look for the correct keys for specifying the container and arguments in Cloud Build steps.

The 'name' key specifies the container image, and 'args' lists the command arguments. Other keys like 'image' or 'container' are invalid in Cloud Build YAML.

🔀 Workflow

advanced

Cloud Build multi-step workflow behavior

Given this Cloud Build YAML with two steps, what happens if the first step fails?

GCP

steps:
- name: 'gcr.io/cloud-builders/gcloud'
  args: ['app', 'deploy']
- name: 'gcr.io/cloud-builders/kubectl'
  args: ['apply', '-f', 'deployment.yaml']

A The build retries the first step twice before running the second step.

B Both steps run regardless of the first step's success or failure.

C The build stops immediately after the first step fails; the second step does not run.

D The second step runs only if the first step succeeds, but the build does not stop on failure.

💡 Hint

Consider the default behavior of Cloud Build when a step fails.

Cloud Build stops the build immediately if any step fails, so subsequent steps do not run.

❓ Troubleshoot

advanced

Diagnosing Cloud Build permission errors

You get this error when running a Cloud Build: "Permission denied: User does not have roles/cloudbuild.builds.editor." What is the most likely cause?

A The Dockerfile has syntax errors causing build failure.

B The user lacks the required IAM role to execute builds.

C The build config file is missing or malformed.

D The Cloud Build trigger is not linked to the correct GitHub repository.

💡 Hint

Focus on the permission error message and what controls build execution rights.

The error indicates the user running the build lacks the necessary IAM role to perform build operations.

✅ Best Practice

expert

Optimizing Cloud Build caching strategy

Which Cloud Build configuration best enables caching to speed up Docker image builds?

A

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '--cache-from', 'gcr.io/my-project/my-image:latest', '-t', 'gcr.io/my-project/my-image', '.']
options:
  machineType: 'E2_HIGHCPU_8'

B

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
options:
  logging: 'DEBUG'

C

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '--no-cache', '-t', 'gcr.io/my-project/my-image', '.']

D

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
substitutions:
  _CACHE: 'true'

💡 Hint

Look for Docker build options that enable cache reuse.

Using '--cache-from' with a previously built image allows Docker to reuse layers, speeding up builds. Other options do not enable caching or disable it.