DevOps CI/CD Pipelines

Question 1

What does CI stand for in the context of DevOps?

Accepted Answer

Continuous Integration

Answer

Continuous Inspection

Answer

Continuous Infrastructure

Answer

Continuous Implementation

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

Automatically deploy every commit to production

Answer

Run unit tests on every commit

Answer

Monitor production environments continuously

Question 3

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

Accepted Answer

Jenkinsfile

Answer

pipeline.yaml

Answer

build.xml

Answer

ci-config.json

Question 4

What is a 'blue-green deployment' strategy?

Accepted Answer

Running two identical production environments and switching traffic between them

Answer

Deploying to a subset of servers first then rolling out gradually

Answer

Using blue containers for staging and green containers for production

Answer

Deploying canary builds to test new features

Question 5

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

Accepted Answer

Trunk-based development

Answer

Git Flow

Answer

Feature branching

Answer

Forking workflow

Question 6

What is the purpose of a 'pipeline artifact' in CI/CD?

Accepted Answer

A built output (binary, JAR, Docker image) produced by one stage and consumed by another

Answer

A log file generated during pipeline execution

Answer

A configuration file that defines pipeline variables

Answer

A test report generated after running unit tests