Module 3 - Graded Quiz: Continuous Delivery (CD) » Week 3 » Continuous Integration And Continuous Delivery (CI/CD)

Q: What is a benefit of Continuous Delivery (CD)?

Correct. A benefit of CD is that its automation reduces deployment time through nonstop testing and deployment cycles.

Q: According to the key principles of Continuous Delivery (CD), what should you do if a build breaks?

Correct. A principle of CD is that everyone is responsible for their part in the story. If a build breaks, you should investigate how the system failed the team, not who is at fault.

Q: What is a best practice for Continuous Delivery (CD)?

Correct. A best practice for CD is to make every change releasable. Doing so means always including user documentation, operations runbooks, and information about what your change does.

Q: Which scanning capability should you have within your Continuous Delivery (CD) pipeline?

Correct. To prevent accidental exposure of sensitive information, you should have a CD tool that scans for secrets like API keys and credentials.

Q: In Tekton, what does TaskRun do?

Correct. When a Tekton pipeline executes, the PipelineRun entity is responsible for managing the tasks. It does this by creating a TaskRun for each task. In turn, each TaskRun creates a Kubernetes pod for its task and all the task’s steps to run in.

Q: In a Tekton task manifest, what syntax must you use to pass a parameter into a step?

Correct. The syntax required to pass a parameter into a step is '$(<variable-name>)'.

Q: Which subfield must you include within the spec field of a Tekton EventListener definition?

Correct. You must include the serviceAccountName subfield within the spec field of a Tekton EventListener definition.

Q: Assume you want to use the git-clone task from the Tekton Catalog. You have a Tekton PersistentVolumeClaim named pipelinerun-vc and a PipelineRun defined as follows: apiVersion: tekton.dev/v1beta1kind: PipelineRun metadata: generateName: pipeline-mn- spec: pipelineRef: name: ab-pipeline workspaces: - name: pipeline-xy persistentVolumeClaim: claimName: pipelinerun-vc params: - name: repo-url value: "$(tt.params.repo)" In the pipeline’s spec section, what name must you give the workspace so that any tasks that need it can use it?

Correct. In the pipeline’s spec section, you must define the workspace as named in the spec--> workspaces --> name subfield of the PipelineRun manifest. In this example, the name is pipeline-xy.