What is CI/CD?
Automatically building, testing and delivering code every time it changes.
In plain English
Continuous integration means developers merge small changes often and each merge triggers an automatic build and tests. Continuous delivery keeps the code always ready to release, with a person pressing the button. Continuous deployment goes one step further and releases automatically when the checks pass. The aim is smaller, safer, more frequent releases.
Example
A pull request triggers a workflow that builds the app and runs tests. Merging to the main branch deploys it to a test environment.
Easy to confuse with
- GitOps: CI/CD pushes changes out through a pipeline. GitOps has a controller inside the cluster pull the desired state from Git.
Where you will meet it
This idea belongs to the subject area of these practice tests. We do not publish or predict real exam questions.
Related terms
- GitOps: Using a Git repository as the single source of truth for what should be running, with software that keeps the live system matching it.
- Kubernetes Deployment: An object that keeps a chosen number of identical pods running and updates them safely.
Test yourself
Practice tests with an explanation for every answer option, so each mistake teaches you something.
Browse practice testsAll glossary termsWritten and checked by the Be Ready Education team, last reviewed 2 November 2026. General study information, not professional advice. Providers change names and rules, so confirm details on the official documentation. Not affiliated with, endorsed by or sponsored by any certification vendor or exam body. Certification names, exam codes and product names are trademarks of their respective owners and are used only to identify the exam a practice product prepares for. Our questions are original and are not actual exam questions.