CI/CD Pipeline Fundamentals Quiz

What is the primary difference between Continuous Delivery and Continuous Deployment?

• Delivery requires no tests; deployment does

• Delivery is fully automated; deployment is manual

• Delivery is manual trigger after automation; deployment is fully automated

• Delivery is used in Dev, deployment in Prod

What is the main goal of implementing CI/CD?

• Reduce the number of developers needed

• Deliver software faster, safer, and more reliably

• Automate everything including customer support

• Build larger monolithic systems

What does CI stand for?

• Continuous Inspection

• Continuous Integration

• Code Injection

• Commit Inventory

Which of the following is a characteristic of a *good* pipeline?

• Tightly coupled logic

• Manual error-prone steps

• Fast feedback

• One person owns the script

What does 'Fail-Fast' mean in pipeline design?

• Intentionally crashing the first test

• Prioritizing speed over accuracy

• Detecting failures early in the pipeline

• Skipping failed jobs

Which of the following is NOT a good practice in a pipeline?

• Modular scripts

• Secure and observable flows

• Black box operations

• Auto rollback support

What is a key benefit of running automated tests on every commit?

• It prevents merge conflicts

• It ensures everyone’s changes are deployed immediately

• It helps catch bugs earlier

• It increases code complexity

What is the meaning of 'Shift Left' in the context of CI?

• Run more steps after deployment

• Avoid test automation

• Perform validations as early as possible

• Delay production builds

Which of the following is NOT part of typical CI steps?

• Static code analysis

• Manual deployment

• Pull request validation

• Build artifact creation

In Continuous Delivery, what is typically manual?

• Testing

• Deployment to production

• Code commit

• Linting