KCNA GitOps and Continuous Delivery 3

Question 1

What is progressive delivery in the context of GitOps?

Accepted Answer

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

Answer

A strategy for migrating incrementally from a monolith to microservices

Answer

A method for progressively reducing cloud infrastructure costs over time

Answer

A Git branching model that enforces incremental, non-breaking feature additions

Question 2

What is a canary deployment?

Accepted Answer

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

Answer

Deploying a release to a dedicated canary Git branch before merging to production

Answer

Deploying all new releases to an isolated canary Kubernetes cluster

Answer

Using a pre-release 'canary' container image tag for integration testing

Question 3

What is Argo Rollouts?

Accepted Answer

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

Answer

A tool for rolling back ArgoCD server configurations to a previous version

Answer

A built-in ArgoCD feature for updating the ArgoCD control plane itself

Answer

A Helm plugin for orchestrating multi-chart release rollouts

Question 4

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

Accepted Answer

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

Answer

Docker container CPU and memory resource consumption in production

Answer

Kubernetes cluster availability and control plane health over time

Answer

GitOps operator sync speed and reconciliation latency

Question 5

What is the OpenGitOps project?

Accepted Answer

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

Answer

An open-source self-hosted alternative to GitHub designed for GitOps workflows

Answer

An open-source GitOps operator maintained directly by the Kubernetes project

Answer

A Git hosting platform optimized for storing Kubernetes manifests

Question 6

How should Kubernetes secrets be handled in a GitOps workflow?

Accepted Answer

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

Answer

Stored in plaintext YAML files in Git alongside other manifests

Answer

Embedded directly inside container images at build time

Answer

Hard-coded into application configuration files committed to the repository

Question 7

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

Accepted Answer

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

Answer

GitOps replaces IaC tools like Terraform, making them unnecessary in cloud native environments

Answer

GitOps and IaC are competing approaches that cannot coexist in the same organization

Answer

GitOps applies only to application manifests, while IaC is handled through a completely separate process