Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A development team is implementing a CI/CD pipeline for their cloud-native application. They want to ensure that every code change that passes automated tests is automatically deployed to a staging environment, but requires a manual approval step before deployment to production. Which CI/CD practice does this scenario best describe?
- AContinuous Integration
- BContinuous Delivery
- CContinuous Deployment
- DGitOps
Show answer & explanationAnswer & explanation
Correct answer: B. Continuous Delivery
Continuous Delivery ensures that all code changes are built, tested, and prepared for release to production, allowing for manual approval before the final deployment. This aligns with the scenario's requirement for automated deployment to staging and manual approval for production.
Why the other options are wrong
- A. Continuous Integration focuses on frequently merging code changes into a central repository and running automated tests.
- C. Continuous Deployment automates the entire release process, including deployment to production, without manual intervention.
- D. GitOps is an operational framework that uses Git as the single source of truth for declarative infrastructure and applications.
Continuous Delivery (CD)
A software engineering approach where teams produce software in short cycles and ensure that the software can be reliably released at any time. It automates testing and deployment to non-production environments, with a manual step for production.
- Automates build, test, and staging deployment.
- Requires manual approval for production deployment.
- Ensures code is always release-ready.
Memory trick: Integrate, Deliver, Deploy: The software journey.