DOL CI/CD Pipeline 2

Question 1

A team notices that every merged PR triggers a full regression suite taking 45 minutes. Which strategy best reduces this feedback cycle without sacrificing coverage?

Accepted Answer

Implement test parallelization and selective test execution based on changed files

Answer

Run the full suite only on the main branch nightly

Answer

Skip unit tests and rely solely on integration tests

Answer

Reduce the number of test cases permanently

Question 2

In a trunk-based development model, how are long-running features typically managed in the CI/CD pipeline?

Accepted Answer

By using feature flags to hide incomplete functionality in production

Answer

By creating long-lived feature branches merged quarterly

Answer

By freezing the main branch until the feature is complete

Answer

By deploying features directly to production without testing

Question 3

What is the primary purpose of a 'canary deployment' in a CD pipeline?

Accepted Answer

To gradually roll out a release to a small subset of users before full deployment

Answer

To deploy only to a staging environment for final QA

Answer

To automatically roll back a failed deployment within seconds

Answer

To run smoke tests against the production environment post-deployment

Question 4

A DevOps leader wants to enforce that no secrets are ever committed to the source repository. Which pipeline control is MOST effective?

Accepted Answer

Adding a pre-commit hook and a CI stage that scans for secrets using tools like Gitleaks

Answer

Educating developers in quarterly security training

Answer

Storing secrets in environment variable files committed alongside code

Answer

Requiring manual code review approval for all changes

Question 5

Which CI/CD metric directly measures the average time from a code commit to a successfully running production deployment?

Accepted Answer

Lead time for changes

Answer

Change failure rate

Answer

Mean time to recovery (MTTR)

Answer

Deployment frequency

Question 6

A CI pipeline fails intermittently on the same test with no consistent reproduction steps. This is best described as:

Accepted Answer

A flaky test that introduces noise into the pipeline

Answer

A regression caused by a recent commit

Answer

A misconfigured build environment

Answer

An infrastructure capacity issue

Question 7

In a Jenkins pipeline, what is the role of a 'Jenkinsfile' stored in version control?

Accepted Answer

It defines the pipeline as code, enabling versioning and peer review of the CI/CD process itself

Answer

It stores build artifacts for later retrieval

Answer

It configures Jenkins server-level settings and plugins

Answer

It acts as a secrets vault for pipeline credentials