Automation & CI/CD Toolchains

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

• A Continuous Delivery keeps code always releasable with a manual trigger to production; Continuous Deployment releases every passing change automatically ✓
• B They are identical terms with no practical difference
• C Continuous Deployment applies only to infrastructure, not application code
• D Continuous Delivery deploys every change automatically to production; Continuous Deployment requires manual approval

Answer: In Continuous Delivery, code is always in a releasable state but a human decides when to deploy; in Continuous Deployment, every change that passes the pipeline is automatically released to production.

What is the primary purpose of Continuous Integration (CI)?

• A To replace version control entirely
• B To merge developers' code frequently and verify each change with an automated build and tests ✓
• C To manually review every line of code before merging
• D To deploy software directly to customers without testing

Answer: Continuous Integration is the practice of frequently merging code changes into a shared repository, where each merge triggers an automated build and test to detect integration problems early.

Infrastructure as Code (IaC) is best described as which of the following?

• A A method for encrypting server hard drives
• B Managing and provisioning infrastructure through machine-readable definition files rather than manual configuration ✓
• C Writing application business logic in a low-level language
• D Storing infrastructure diagrams in a wiki

Answer: Infrastructure as Code manages and provisions infrastructure using version-controlled, machine-readable definition files, enabling repeatable, consistent, and automated environment creation.

Which of the following is a key benefit of using a version control system as the single source of truth in a DevOps toolchain?

• A It guarantees zero defects in production
• B It eliminates the need for collaboration
• C It removes the need for automated testing
• D It provides traceability, history, and the ability to reproduce any version of code or configuration ✓

Answer: Version control provides a complete, auditable history of changes and allows any version of code or configuration to be reproduced, forming the foundation of reliable, automated pipelines.

A deployment pipeline typically progresses through which logical sequence of stages?

• A Manual approval only, with no automated stages
• B Commit/build, automated tests, then release to staging and production ✓
• C Monitoring first, then coding
• D Production, then build, then commit

Answer: A deployment pipeline generally moves from commit and build, through progressively more thorough automated tests, to deployment in staging and finally production, giving fast feedback at each stage.

What distinguishes a 'declarative' approach to Infrastructure as Code from an 'imperative' one?

• A Imperative can only be used for cloud, declarative only for on-premises
• B There is no difference between the two approaches
• C Declarative specifies the desired end state; imperative specifies the exact steps to reach it ✓
• D Declarative requires more manual scripting than imperative

Answer: A declarative approach describes the desired end state and lets the tool determine how to achieve it, whereas an imperative approach defines the explicit sequence of commands to reach that state.