Pass the Linux Foundation DevOps and Site Reliability CGOA Questions and answers with ExamsMirror

Thefeedback loopis critical in GitOps reconciliation. It continuously monitors the system’s actual state and compares it to the desired state. This loop determines when reconciliation is required and whether a full or partial synchronization is necessary.

“The feedback loop in reconciliation continuously observes the actual state. It determines if reconciliation is required, and informs whether to perform a partial or full sync to align with the declared desired state.”

Thus, the correct answer isA.

Prometheus is commonly used in GitOps for monitoring.Alertmanageris the tool integrated with Prometheus to handle alert routing. It supports sending alerts to external systems such as Slack, PagerDuty, or email.

“Prometheus generates alerts, which are routed and managed by Alertmanager. Alertmanager can integrate with messaging tools like Slack to deliver alerts in real time.”

Thus, the correct answer isA: Alertmanager.

A GitOps-managed Kubernetes cluster uses reconciliation loops to continuously compare the actual state of the system with the desired state declared in Git. When drift (divergence between declared configuration and live cluster state) is detected, the GitOps operator automatically reconciles the difference to bring the system back into alignment.

“In GitOps, a reconciliation loop ensures that the desired state as declared in Git is continuously compared with the observed state of the system. If drift is detected, the system automatically takes corrective action to reconcile the difference and restore the declared configuration.”

This ensures consistency, reliability, and self-healing. Manual intervention is not required for drift correction, as the automated reconciliation is a core principle of GitOps.

In GitOps, deployments are driven bycommitting declarative configurationinto a Git repository (the State Store). From there, agents reconcile the actual environment to match the desired state, making deployments reproducible and auditable.

“To deploy in GitOps, commit the declarative configuration into version control. The reconciler ensures the runtime environment converges to the declared state.”

Thus, the correct answer isD.

ThePulled Automaticallyprinciple in GitOps means that agents inside the runtime environment (e.g., controllers/operators) continuously monitor Git (the source of truth) andautomatically pull changeswhen updates are detected.

“Software agents continuously pull changes from the version control system and reconcile them automatically. This pull-based approach ensures automation, security, and self-healing.”

Thus, the correct answer isB.

Progressive deliveryis a GitOps pattern that incrementally rolls out application updates, using methods like canary releases, feature flags, and blue-green deployments. GitOps enhances this by ensuring the rollout isautomated and declaratively managed through Git, removing the need for manual traffic switching.

“GitOps enables progressive delivery by declaratively managing rollout strategies such as canary or blue-green deployments. These strategies are applied automatically by controllers, without requiring manual traffic switching.”

Thus, the correct answer isB.

The reconciliation loop is a fundamental GitOps principle. It continuously compares thedesired state(stored in Git) with theactual state(running in the system). When a divergence (drift) is detected, the reconciler automatically corrects the system to match the desired state.

“The reconciliation loop ensures the system is continuously converging toward the declared desired state. Whenever the actual state deviates, the loop reconciles the system to match the desired state.”

Thus, the correct answer isC.

GitOps emphasizes immutability and auditability. If an error occurs in the configuration stored in Git, the system should be rolled back to the last known good state while the error is fixed. This preserves system reliability and aligns with the GitOps principle of rollback through version control.

“With Git as the source of truth, if an error is introduced, the system can be rolled back by reverting to a previous commit. This ensures stability while the faulty configuration is corrected.”

Thus, the recommended action isC: Roll back to the previous working version.

The first GitOps principle isDeclarative Descriptions. This means the desired system configuration (for infrastructure, services, and applications) is expressed declaratively and stored in version control. Git becomes the single source of truth.

“The desired system state must be expressed declaratively. This provides a clear, machine-readable blueprint for the system, and ensures that what is in Git is what should be running in the environment.”

Therefore,infrastructure and application configurations must be defined declaratively and stored in Git, not managed imperatively or manually.

In GitOps,Git is the single source of truth. If changes are made manually in the cluster (viakubectl), those changes will drift from the desired state in Git. To ensure consistency, the correct approach is toupdate the Git repository (Desired State store)so that the reconciler can continuously apply and maintain those changes.

“The desired state must always be declared in Git. Manual changes in the cluster will be overwritten by reconciliation unless they are committed to the Git repository.”

Thus, the correct answer isB.