CompTIA Cloud+ (CV0-004)DevOps FundamentalsEasy
A software team commits code to a shared repository multiple times per day. Each commit automatically triggers a build and a suite of automated tests to catch integration errors as early as possible. Which practice does this describe?
- AContinuous integration
- BContinuous delivery
- CContinuous deployment
- DContinuous monitoring
Show answer & explanationAnswer & explanation
Correct answer: A. Continuous integration
Continuous integration (CI) focuses on frequently merging code changes and automatically building and testing them to detect issues early. Continuous deployment and delivery extend the pipeline further to automate release into production.
Why the other options are wrong
- B. Continuous delivery ensures code is always release-ready but still requires a deployment step, not the focus here.
- C. Continuous deployment automatically pushes every passing build to production, which isn't described here.
- D. Continuous monitoring tracks running systems in production, not the build/test cycle.
Continuous Integration (CI)
CI is the practice of frequently merging code into a shared repository, with each merge automatically built and tested to catch integration issues early.
- Encourages small, frequent commits
- Automated build and test pipeline runs on each commit
- Reduces integration conflicts and catches bugs early
Memory trick: Commit, Build, Test, Deploy — CI catches problems before they snowball.