Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium
A team is implementing a CI/CD pipeline for their cloud-native application. They want to ensure that every code change undergoes automated testing, code quality checks, and then is automatically deployed to a staging environment for further validation. Only after successful staging tests and manual approval should it proceed to production. Which principle of CI/CD does the 'automated deployment to staging' and 'manual approval for production' part primarily represent?
- AContinuous Delivery
- BContinuous Integration
- CContinuous Monitoring
- DContinuous Deployment
Show answer & explanationAnswer & explanation
Correct answer: A. Continuous Delivery
Continuous Delivery ensures that code changes are automatically built, tested, and prepared for release to production, including automated deployment to staging, but requires a manual step for the final production deployment. Continuous Deployment would automate the final step as well.
Why the other options are wrong
- B. Continuous Integration focuses on merging code frequently and running automated tests.
- C. Continuous Monitoring is about observing the application in production, not the deployment process itself.
- D. Continuous Deployment automates the entire process, including deployment to production without manual approval.
Continuous Delivery (CD)
A software development practice where code changes are automatically built, tested, and prepared for release to production, allowing for frequent, reliable releases at any time, typically with a manual approval gate for production deployment.
- Automates pipeline up to production readiness.
- Requires manual approval for production deployment.
- Enables frequent, reliable releases.
- Superset of Continuous Integration.
Memory trick: CI is building, CD is delivering to the door, and CDep is pushing it inside.