Automation & CI/CD Toolchains
53 practice questions with explanations — 15 free to try
3 of these 53 questions are in the free 15-question taster · the full topic is part of Premium
PassNova has 53 DevOps Foundation practice questions on Automation & CI/CD Toolchains, each with a clear explanation. A 15-question taster is free with no sign-up; the full bank is part of PassNova Premium. Updated for 2026.
Automation & CI/CD Toolchains: example questions & answers
3 worked examples with answers and explanations below. Try 15 DevOps Foundation questions free in the browser; the full 53-question Automation & CI/CD Toolchains bank is part of PassNova Premium.
What is the main difference between Continuous Delivery and Continuous Deployment?
- AContinuous Delivery keeps code always releasable with a manual trigger to production; Continuous Deployment releases every passing change automatically✓
- BThey are identical terms with no practical difference
- CContinuous Deployment applies only to infrastructure, not application code
- DContinuous 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)?
- ATo keep each developer's work on a separate long-lived branch until the whole feature is finished
- BTo merge developers' code frequently and verify each change with an automated build and tests✓
- CTo have a senior engineer inspect each line of code by hand before a merge, in place of an automated build
- DTo deploy each developer's changes straight to customers without running automated tests first
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?
- AA method for encrypting server hard drives
- BManaging and provisioning infrastructure through machine-readable definition files rather than manual configuration✓
- CWriting application business logic in a low-level language
- DStoring hand-drawn infrastructure diagrams and network topology documents in a team wiki so engineers can configure servers by hand
Answer: Infrastructure as Code manages and provisions infrastructure using version-controlled, machine-readable definition files, enabling repeatable, consistent, and automated environment creation.