← CGOA hub

CGOA — GitOps Patterns

20% of the CGOA exam. Sample questions below; the full library has 28 questions tagged to this domain.

Sample questions on GitOps Patterns

GitOps Patterns

Q1. In the 'in-cluster reconciler' pattern, what is the advantage of deploying the GitOps controller in the same cluster it manages?

Reveal answer and explanations
  1. A In-cluster reconcilers always deploy faster

    Incorrect. Speed depends on implementation and load, not location.

  2. B In-cluster controllers can modify cluster security policies

    Incorrect. Controllers manage application state, not cluster security policies.

  3. C In-cluster patterns eliminate the need for version control

    Incorrect. The controller still pulls from Git; location doesn't eliminate the state store requirement.

  4. D Cluster-local identities without external cluster credentials

    Correct. An in-cluster controller uses native Kubernetes authentication, reducing credential exposure and attack surface.

GitOps Patterns

Q2. What is the purpose of ApplicationSet generators in Flux/ArgoCD?

Reveal answer and explanations
  1. A To manage Helm chart versions

    Incorrect. They work with charts but don't manage versions.

  2. B To create multiple Applications dynamically based on templates and data sources (cluster lists, Git branches, matrices)

    Correct. ApplicationSet generators template multiple Applications from data sources, enabling multi-cluster and multi-tenant deployments without manual repetition.

  3. C To automatically generate Git commits

    Incorrect. They don't generate commits.

  4. D To replace manual Application creation in the UI

    Incorrect. They do replace manual UI creation, but that's not the primary purpose.

  5. E To generate container images from source code

    Incorrect. Generators don't build images.

GitOps Patterns

Q3. What is the primary architectural difference between a 'pull-based' GitOps pattern and an 'event-driven' GitOps pattern?

Reveal answer and explanations
  1. A Pull-based is faster because it eliminates event latency

    Incorrect. Event-driven can be faster, but pull provides consistent, predictable update intervals.

  2. B Pull-based requires more infrastructure than event-driven

    Incorrect. Event-driven (webhooks) often requires additional infrastructure like event brokers.

  3. C Event-driven uses Git while pull-based uses databases

    Incorrect. Both use Git; the difference is in the trigger mechanism, not the state store.

  4. D Polling controllers versus webhook-triggered reconciliation

    Correct. Pull polls periodically; event-driven reacts to webhooks, enabling faster but potentially less consistent updates.

GitOps Patterns

Q4. In the ArgoCD App-of-Apps pattern, what is the primary advantage of this approach?

Reveal answer and explanations
  1. A It simplifies RBAC configuration

    Incorrect. RBAC is independent of this pattern.

  2. B It reduces the number of ArgoCD instances needed

    Incorrect. It doesn't reduce ArgoCD instances.

  3. C It eliminates the need for Helm or Kustomize

    Incorrect. Templating tools still apply.

  4. D It is required for multi-cluster management

    Incorrect. Multi-cluster is possible without App-of-Apps.

  5. E A root Application orchestrates child Applications

    Correct. The root app acts as a management layer, enabling scalable, organized deployments where the Git repo structure mirrors the application hierarchy.

GitOps Patterns

Q5. What is the 'monorepo' pattern in GitOps, and what is a key tradeoff it presents?

Reveal answer and explanations
  1. A A monorepo uses a single Git branch for all environments

    Incorrect. A monorepo can use multiple branches; the distinction is about the number of repositories, not branches.

  2. B Monorepos are always faster than polyrepos

    Incorrect. Performance depends on implementation and access patterns, not repository structure.

  3. C A single Git repository holds configuration for all applications and environments; advantage is centralization, but a disadvantage is that unrelated changes can cause merge conflicts or require careful access control

    Correct. Monorepos provide unified visibility and change tracking but require strong CI/CD practices and careful role-based access to prevent conflicts.

  4. D A monorepo ensures that only one person can commit at a time to optimize resource utilization and cost and encompasses related operational processes across environments

    Incorrect. Git allows concurrent commits; a monorepo doesn't serialize contributors.

Drill GitOps Patterns with the full bankDomain Drill mode targets your weak areas — paid feature

How this domain is tested

GitOps Patterns accounts for 20% of the CGOA exam. Expect questions that test recall of terminology and the ability to read short scenarios — not deep configuration. Use the sample questions above as difficulty calibration; if any feel hard, the rest of our 28-question domain bank will close those gaps.