Free CGOA Sample Questions

Incorrect. Deployment registry typically refers to container registries, not configuration repositories.

Incorrect. While technically accurate (it does contain manifests), the precise GitOps term is state store.

Incorrect. While Git could cache configuration, 'cache' implies it's not authoritative, but the state store is the authority.

Correct. The Git repository acting as the authoritative source of truth for desired state is the state store.

Incorrect. The Application manages deployed resources, not the image itself.

Incorrect. While it may contain workloads, an Application is the declarative management wrapper.

Correct. An ArgoCD Application declaratively specifies the Git source, destination cluster, and sync policy for resources.

Incorrect. An Application is a management construct, not a workload.

Incorrect. CI/CD pipelines are separate from GitOps Applications.

Incorrect. Database rollback is a separate operational concern from GitOps rollback.

Incorrect. CI pipeline reversion is not a rollback mechanism; it doesn't affect what's already deployed.

Correct. In GitOps, rollback is achieved declaratively by reverting the commit that defined the undesired state, allowing the system to reconcile to a known good state.

Incorrect. While automatic remediation exists, true GitOps rollback is accomplished through version control, not automatic reversion.

Incorrect. Multiple controllers can coexist in GitOps; convergence is a state property.

Incorrect. That's organizational transformation, not the technical concept.

Incorrect. Convergence is about state alignment, not branch merging.

Correct. Convergence is the core GitOps mechanism: continuous reconciliation drives live state toward desired state.

Incorrect. Convergence is about state, not environment timing.

Incorrect. CI pipelines are separate from the reconciliation loop, which continuously operates in GitOps systems.

Correct. 'Continuous' means the reconciliation loop is always running and never stops, continuously observing and adjusting the system.

Incorrect. Polling frequency and continuous operation are different concepts; a system can poll infrequently but still be continuous.

Incorrect. While reconciliation may happen frequently, 'continuous' refers to the never-stopping nature of the loop, not just the frequency.

Incorrect. While drift detection is part of feedback, this doesn't capture the full scope of what feedback includes.

Incorrect. These terms have distinct meanings in GitOps architecture.

Incorrect. Operator-initiation doesn't define the distinction between these concepts.

Correct. The feedback loop encompasses drift detection (measuring state divergence), remediation (triggering reconciliation), and alerting (notifying operators of changes), making it the broader concept.

Incorrect. Both can be automatic in modern GitOps systems.

Incorrect. Performance degradation is unrelated to state drift, which is a configuration/deployment concept.

Incorrect. Deployment latency is separate from state drift; a system can have low latency and high drift if manual changes are made.

Correct. State drift occurs when the actual running state diverges from the desired state defined in the Git repository.

Incorrect. Unapproved Git changes are a process issue, not the definition of state drift itself.

Correct. These address fundamentally different stages: CI tests code changes, while continuous reconciliation ensures deployed state matches declared state persistently.

Incorrect. Continuous reconciliation is inherently ongoing, not one-time.

Incorrect. Both reconciliation loops and CI jobs can be automated; they operate on different targets.

Incorrect. These solve different problems in the deployment pipeline.

Incorrect. While common in Kubernetes, reconciliation applies to any declarative system.

Incorrect. Verbal declarations have nothing to do with declarative infrastructure; the focus is on data representation.

Incorrect. Building images is part of CI, not a characteristic of declarative systems.

Incorrect. While a changelog is useful documentation, it's not what makes a system declarative.

Correct. Declarative systems define the desired state as data structures that can be version controlled and automatically enforced, not through procedural commands.

Correct. While high availability is desirable, geographic distribution across multiple clouds is not a requirement for a valid state store.

Incorrect. Being the single source of truth is a defining characteristic.

Incorrect. Version control is fundamental to GitOps state stores.

Incorrect. Immutability is essential to prevent undocumented changes.

Incorrect. Auditability through history is critical to GitOps principles.