Practice Test Geeks(KCNA) Kubernetes and Cloud Native Associate Practice Test
← All KCNA Flashcard Decks

GitOps and Continuous Delivery Flashcards

7 cards from real KCNA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 GitOps and Continuous Delivery flashcards as text

  1. What is progressive delivery in the context of GitOps?

    Answer: A technique for gradually rolling out changes to subsets of users with automated analysis and rollback

    Progressive delivery extends continuous delivery by gradually exposing new versions to increasing subsets of users while using automated metric analysis to decide whether to proceed or roll back.

  2. What is a canary deployment?

    Answer: Routing a small percentage of live traffic to a new version to validate it before full rollout

    A canary deployment sends a small slice of production traffic to the new version, allowing teams to validate behavior under real conditions before expanding the rollout to all users.

  3. What is Argo Rollouts?

    Answer: A Kubernetes controller that provides advanced deployment strategies such as canary and blue-green

    Argo Rollouts is a Kubernetes controller and set of CRDs that extend the standard Deployment with advanced strategies including canary, blue-green, and automated metric-based analysis for progressive delivery.

  4. What do DORA (DevOps Research and Assessment) metrics measure?

    Answer: Software delivery performance via deployment frequency, lead time, change failure rate, and time to restore

    DORA metrics quantify software delivery performance across four dimensions: deployment frequency, lead time for changes, change failure rate, and mean time to recovery (MTTR).

  5. What is the OpenGitOps project?

    Answer: A CNCF project that defines vendor-neutral GitOps principles and a shared specification

    OpenGitOps is a CNCF Sandbox project and working group that establishes vendor-neutral GitOps principles and a shared specification to ensure interoperability across GitOps tooling.

  6. How should Kubernetes secrets be handled in a GitOps workflow?

    Answer: Managed with tools like Sealed Secrets or External Secrets Operator so only encrypted or referenced data lives in Git

    Secrets must never be stored in plaintext in Git; tools like Sealed Secrets encrypt secrets before committing, or External Secrets Operator fetches secrets from an external vault at runtime.

  7. What is the relationship between GitOps and Infrastructure as Code (IaC)?

    Answer: GitOps builds on IaC by using Git as the system of record for IaC definitions and automating their reconciliation

    GitOps extends IaC by storing all declarative infrastructure definitions in Git and using operators to continuously reconcile the actual infrastructure to match that desired state automatically.