Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryMedium

A company is implementing a CI/CD pipeline for its cloud-native applications. They want to ensure that all changes to application code and infrastructure configurations are version-controlled, traceable, and subject to review before deployment. Which foundational practice, central to modern CI/CD, best supports these requirements?

  1. ACanary Releases
  2. BBlue/Green Deployments
  3. CGit-based Workflow
  4. DFeature Flagging
Show answer & explanation

Correct answer: C. Git-based Workflow

A Git-based workflow ensures that all code and configuration changes are stored in a Git repository, providing version control, a complete history, and mechanisms for pull requests and code reviews, which are essential for traceability and quality in CI/CD.

Why the other options are wrong

  • A. Canary Releases are a deployment strategy for risk reduction.
  • B. Blue/Green Deployments are a deployment strategy for zero-downtime updates.
  • D. Feature Flagging is a release strategy, not a version control practice.

Git-based Workflow

A development practice where all code, configuration, and artifacts are managed and version-controlled within a Git repository, enabling collaboration, traceability, and automated processes.

  • Serves as the single source of truth for all project assets.
  • Facilitates collaboration through branching and merging.
  • Provides a complete history of changes for auditing and rollback.

Memory trick: Git is the master scroll of all CI/CD changes.

More Cloud Native Delivery questions