DevOps CI/CD Pipelines

Question 1

What does CI stand for in the context of DevOps?

Accepted Answer

Continuous Integration

Answer

CI stands for Continuous Integration, the practice of frequently merging code changes into a shared repository with automated builds and tests.

Question 2

Which of the following is the primary goal of Continuous Delivery (CD)?

Accepted Answer

Ensure software can be released to production at any time

Answer

Continuous Delivery ensures the software is always in a deployable state so it can be released to production at any time with a manual approval step.

Question 3

In a Jenkins pipeline, what file defines the pipeline-as-code configuration?

Accepted Answer

Jenkinsfile

Answer

A Jenkinsfile is a text file stored in the repository that defines the Jenkins pipeline using either Declarative or Scripted pipeline syntax.

Question 4

What is a 'blue-green deployment' strategy?

Accepted Answer

Running two identical production environments and switching traffic between them

Answer

Blue-green deployment maintains two identical production environments where one is live (blue) and the other receives the new deployment (green), then traffic is switched.

Question 5

Which Git branching strategy is most commonly associated with CI/CD pipelines?

Accepted Answer

Trunk-based development

Answer

Trunk-based development, where all developers commit to a single main branch frequently, best supports CI/CD by reducing merge conflicts and enabling rapid integration.

DevOps Practice Test

DevOps Practice Test

DevOps CI/CD Pipelines