DevOps CI/CD Pipelines 3

Question 1

What does the DORA metric 'Lead Time for Changes' measure?

Accepted Answer

Time from code commit to running in production

Answer

Time to recover from a production failure

Answer

Percentage of deployments causing failures

Answer

Number of deployments per time period

Question 2

In GitLab CI/CD, what file defines the pipeline configuration?

Accepted Answer

.gitlab-ci.yml

Answer

Gitlabfile

Answer

pipeline.yml

Answer

ci-config.yml

Question 3

What is a 'rolling deployment'?

Accepted Answer

Gradually replacing old instances with new ones in batches

Answer

Deploying to two environments simultaneously and comparing results

Answer

Routing a percentage of traffic to the new version

Answer

Deploying and immediately rolling back if errors are detected

Question 4

Which practice ensures that every code change passes automated tests before being merged?

Accepted Answer

Continuous Integration

Answer

Continuous Deployment

Answer

Continuous Monitoring

Answer

Continuous Feedback

Question 5

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

Accepted Answer

To provide a production-like environment for final testing before release

Answer

To store build artifacts before deployment

Answer

To run unit tests in isolation

Answer

To monitor production traffic patterns

Question 6

What does 'fail fast' mean in a CI/CD pipeline?

Accepted Answer

Running the quickest and most critical checks first to detect failures early

Answer

Automatically rolling back all failed deployments immediately

Answer

Terminating the pipeline as soon as any single test fails

Answer

Deploying rapidly even if some non-critical tests fail