CI/CD

Question 1

What is Cloud Build?

Answer 1

Cloud Build is a CI/CD pipeline service offered by GCP. It has stronger support for CI than CD.

Question 2

Summarize the steps in this YAML file.

Answer 2

Each step must contain a name field that
specifies a cloud builder, which is a container image that runs common tools. In this
sample, we have a build step with a docker builder, which is an image running
Docker. The args field of a step takes a list of arguments and passes them to the builder. The
values in the args list are used to access the builder’s entrypoint. If the builder does
not have an entrypoint, the first element in the args list is used as the entrypoint.

Question 3

What is the difference between Cloud Deploy and Cloud Deployment Manager?

Question 4

What is the difference between Cloud Deployment Manager and Terraform?

Question 5

What does the Cloud Foundation Toolkit provide?

Answer 5

The Cloud Foundation Toolkit provides templates for Cloud Deployment Manager and Terraform which reflect Google Cloud best practices. These templates can be used to quickly build repeatable enterprise-ready foundations in Google Cloud.

Question 6

When needing to push container images from Docker to Artifact Registry, what gcloud command must you execute for Docker to be able to authenticate itself to Artifact Registry?

Answer 6

gcloud auth configure-docker ${REGION}-docker.pkg.dev

Question 7

What are the different ways to build container images using Cloud Build?

Answer 7

1. Configuration file (YAML or JSON)
2. Dockerfile
3. Buildpacks

While all 3 can be use to build container images, only configuration files can be used to implement a CI/CD pipeline.

Question 8

When using Cloud Build, each step in your configuration file is a ….

Answer 8

Container image that is executed as a container. These container images are also called cloud builders.

For example:

steps:
    - name: 'gcr.io/cloud-builders/docker'

Question 9

Understanding that any data created in one step of your Cloud Build configuration file does not carry over to other steps by default, what can you do to pass from previous steps to future steps?

Answer 9

You can attach volumes to your build steps. By default, Cloud Build provides a volume to the /workspace directory. Therefore, if a build step writes data into that directory, that same data can be read by future build steps.

Question 10

What are the 2 ways to execute Cloud Build?

Answer 10

1. Automatically through triggers
2. Manually through gcloud

Question 11

What are the 3 general supported Cloud Build event triggers?

Answer 11

1. Repository triggers
2. Pub/Sub Topic triggers
3. Webhook triggers

Question 12

What field can you declare on a Cloud Build configuration file to push an image to Artifact Registry?

Answer 12

steps:
    ...
images: 
    - "region-docker.pkg.dev..."

Question 13

Is a Cloud Storage Bucket created when using the gcloud builds submit command for the first time?

Answer 13

Yes. When you run gcloud builds submit for the first time in a Google Cloud project, Cloud Build creates a Cloud Storage bucket named [YOUR_PROJECT_NAME]_cloudbuild in that project. Cloud Build uses this bucket to store any source code that you might use for your builds. Cloud Build does not automatically delete contents in this bucket. To delete objects you’re no longer using for builds, you can either set up lifecycle configuration on the bucket or manually delete the objects.

Question 14

What is the format for tagging images so that they can be stored in Artifact Registry?

Answer 14

<regional-repository>-docker.pkg.dev/my-project/my-repo/my-image

Question 15

What are the 2 different continuous delivery target environments that Cloud Deploy supports?

Answer 15

1. Cloud Run
2. GKE

Cloud Deploy automates delivery of your applications to a series of target environments in a defined sequence.

Question 16

What is the command to perform on-demand container image analysis?

Answer 16

gcloud artifacts docker images scan <image>