Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureHard
A software development team wants to automate the process of building, testing, and deploying their cloud-native application. They aim for frequent, small releases and want to ensure that every code change that passes automated tests is automatically released to a production-like environment. What practice are they implementing?
- AContinuous Integration (CI)
- BContinuous Delivery (CD)
- CContinuous Deployment (CD)
- DContinuous Monitoring (CM)
Show answer & explanationAnswer & explanation
Correct answer: B. Continuous Delivery (CD)
Continuous Delivery (CD) ensures that every code change is built, tested, and prepared for release to production. While it makes the application deployable at any time, a manual step is still required to push to production. This aligns with 'automatically released to a production-like environment' but retains the option for a final manual gate.
Why the other options are wrong
- A. Continuous Integration (CI) focuses on merging code changes frequently and running automated tests, not on preparing for release or deploying to environments.
- C. Continuous Deployment (CD) is an extension of Continuous Delivery where every change that passes automated tests is automatically deployed to production without human intervention.
- D. Continuous Monitoring (CM) involves observing the application and infrastructure in production to detect issues, not a release practice.
Continuous Delivery (CD)
A software engineering approach where teams produce software in short cycles, ensuring that the software can be reliably released at any time. It automates the entire software release process up to the point of production deployment.
- Automates building, testing, and preparing for release.
- Ensures software is always in a deployable state.
- Includes a manual step for production deployment.
- Builds upon Continuous Integration.
Memory trick: CI builds, CD delivers, CD deploys.