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. Flux CD synchronizes Kubernetes clusters using which model?

    Answer: Pull-based, with controllers running inside the cluster watching Git

    Flux CD uses a pull-based model where controllers (source-controller, kustomize-controller, etc.) run inside the cluster and continuously watch Git repositories for changes to apply.

  2. What is the 'app of apps' pattern in ArgoCD?

    Answer: A pattern where one ArgoCD Application manages other ArgoCD Application resources

    The 'app of apps' pattern uses a root ArgoCD Application pointing to a Git directory that contains manifests for additional ArgoCD Applications, enabling hierarchical management of many applications.

  3. What role does Kustomize play in a GitOps workflow?

    Answer: It allows customization of Kubernetes YAML manifests through overlays without modifying original base files

    Kustomize lets users apply environment-specific patches and overlays on top of base Kubernetes manifests without editing the originals, enabling DRY, environment-aware GitOps configurations.

  4. In a GitOps workflow, what event typically triggers a deployment to production?

    Answer: A merge into the target branch (e.g., main) in the Git repository

    In GitOps, merging a pull request into the target branch signals 'this change is approved,' causing the GitOps operator to detect the new desired state and synchronize the cluster.

  5. How does ArgoCD represent the synchronization status of a managed application?

    Answer: It displays a Synced or OutOfSync status and supports both auto-sync and manual sync modes

    ArgoCD displays each application's health and sync status (Synced/OutOfSync) and can be configured for automatic synchronization or to require manual approval before applying changes.

  6. What does a GitOps operator's self-healing capability accomplish?

    Answer: It automatically restores the cluster to the Git-defined desired state whenever drift is detected

    Self-healing means the GitOps operator detects any drift (e.g., a manually deleted resource) and automatically re-applies the desired state from Git without human intervention.

  7. Which Git branching strategy is commonly paired with GitOps for environment promotion?

    Answer: Environment-specific branches or directories within the repository to separate dev, staging, and production

    GitOps environments are commonly separated by branches (e.g., dev, staging, main) or by directories within a single branch, enabling controlled promotion of changes through each environment.