KCNA GitOps and Continuous Delivery 2

Question 1

Flux CD synchronizes Kubernetes clusters using which model?

Accepted Answer

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

Answer

Push-based, triggered by external CI webhook calls

Answer

Manual, requiring operator approval for each synchronization

Answer

Event-driven, triggered exclusively by container registry update notifications

Question 2

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

Accepted Answer

A pattern where one ArgoCD Application manages other ArgoCD Application resources

Answer

A pattern for co-locating multiple containers within a single Kubernetes pod

Answer

A pattern for sharing configuration between cooperating microservices

Answer

A pattern for routing traffic between multiple application versions

Question 3

What role does Kustomize play in a GitOps workflow?

Accepted Answer

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

Answer

It is a secret encryption tool for storing credentials in Git

Answer

It is a package manager equivalent to Helm for templating manifests

Answer

It builds container images as part of the GitOps pipeline

Question 4

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

Accepted Answer

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

Answer

A manual kubectl apply run by an operator

Answer

A scheduled cron job running in the CI system every night

Answer

A direct API call sent to the Kubernetes API server

Question 5

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

Accepted Answer

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

Answer

It sends email alerts whenever an application is out of sync

Answer

It automatically rolls back the application to the last known good state on any sync failure

Answer

It blocks new Git commits to the repository when the cluster is out of sync

Question 6

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

Accepted Answer

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

Answer

It repairs corrupted or force-pushed Git repositories

Answer

It corrects syntax errors found in Kubernetes YAML manifests

Answer

It restarts failed CI/CD pipeline jobs when they time out

Question 7

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

Accepted Answer

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

Answer

A single shared branch used for all environments simultaneously

Answer

Feature branches that deploy changes directly to production on push

Answer

A merge-free workflow using cherry-picking across all environments