Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryMedium
A DevOps team is setting up a new CI/CD pipeline for a microservices application. They want to ensure that every code change triggers an automated build, test, and potentially a deployment process. What is the primary purpose of the 'Continuous Integration' (CI) part of a CI/CD pipeline?
- ATo perform manual security audits on code before release.
- BTo monitor application performance and user experience in real-time.
- CTo automatically deploy validated code to production environments.
- DTo continuously merge code changes from multiple developers into a shared repository and verify them.
Show answer & explanationAnswer & explanation
Correct answer: D. To continuously merge code changes from multiple developers into a shared repository and verify them.
Continuous Integration (CI) is the practice of frequently merging code changes into a central repository, followed by automated builds and tests. Its primary purpose is to detect integration errors early and ensure the codebase remains in a healthy, deployable state.
Why the other options are wrong
- A. Manual security audits are part of security practices, often integrated but not the core of CI.
- B. This describes monitoring tools, which are part of observability, not CI.
- C. This describes Continuous Delivery/Deployment (CD), not CI.
Continuous Integration (CI)
A development practice where developers frequently merge their code changes into a central repository, after which automated builds and tests are run. The primary goal of CI is to find and address integration bugs quicker.
- Frequent code merges (multiple times a day).
- Automated build and test processes.
- Early detection of integration issues.
- Maintains a consistently healthy and deployable codebase.
Memory trick: CI is the constant 'check-in' before the 'delivery' journey.