DevNet Associate (DEVASC) v1.0Application Deployment and SecurityEasy
A DevOps team is implementing a new CI/CD pipeline for a critical microservice. They need to ensure that every code change undergoes automated testing and static code analysis before being deployed to a staging environment. Which CI/CD practice directly addresses this requirement?
- AContinuous Monitoring
- BContinuous Delivery
- CContinuous Integration
- DContinuous Deployment
Show answer & explanationAnswer & explanation
Correct answer: C. Continuous Integration
Continuous Integration (CI) is the practice of frequently merging code changes into a central repository, followed by automated builds and tests. This ensures early detection of integration issues and adheres to the described requirement for automated testing and static code analysis.
Why the other options are wrong
- A. Continuous Monitoring is about observing system performance and health in production, not part of the build/test phase.
- B. Continuous Delivery ensures that code is always in a deployable state, often including manual approval for production, which is a broader scope than just the integration phase.
- D. Continuous Deployment automatically releases every validated change to production, which goes beyond just testing and analysis.
Continuous Integration (CI)
Continuous Integration is a development practice where developers frequently merge their code changes into a central repository, after which automated builds and tests are run.
- Frequent code merges.
- Automated builds.
- Automated tests (unit, integration, static analysis).
- Early detection of defects.
Memory trick: CI integrates and tests, CD delivers, CDep deploys.