Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryEasy
A DevOps team is setting up a new CI/CD pipeline for a microservices application. They want to ensure that every code commit automatically triggers a process to build, test, and validate the code before it is integrated into the main branch. Which stage of the CI/CD pipeline does this describe?
- AContinuous Deployment
- BContinuous Integration
- CContinuous Monitoring
- DContinuous Delivery
Show answer & explanationAnswer & explanation
Correct answer: B. Continuous Integration
Continuous Integration (CI) is the practice where developers frequently merge their code changes into a central repository, after which automated builds and tests are run. This helps detect integration errors early.
Why the other options are wrong
- A. Continuous Deployment automatically releases validated code to production, going beyond just building and testing.
- C. Continuous Monitoring is about observing applications in production, not the build/test phase.
- D. Continuous Delivery implies code is always ready for release, but not necessarily automatically deployed.
Continuous Integration (CI)
Continuous Integration is a development practice where developers merge code changes frequently into a central repository, after which automated builds and tests are run.
- Automates build and test processes.
- Detects integration issues early.
- Requires frequent code commits.
Memory trick: CI is where the code first gets its check-up before the big journey.