You are working on a GitOps project and have made some changes to the cluster using kubectl. What is the recommended approach to ensure that your changes are continuously reconciled?
Answer(s): B
In GitOps, Git is the single source of truth. If changes are made manually in the cluster (via kubectl), those changes will drift from the desired state in Git. To ensure consistency, the correct approach is to update 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 is B.
GitOps Principles (CNCF GitOps Working Group), Drift and Reconciliation Practices.
In the context of GitOps, what source of truth guides the continuous deployment process?
Answer(s): A
The Desired State, stored in Git, is the ultimate source of truth in GitOps. It defines how the system should look and behave. Continuous deployment processes reconcile the actual cluster state against this Desired State."In GitOps, the desired state kept in Git is the single source of truth. The reconciler ensures the actual state matches the desired state, guiding the continuous deployment process."Thus, the correct answer is A.
GitOps Terminology (CNCF GitOps Working Group).
Why is the feedback loop important for reconciliation?
The feedback loop is 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 is A.
GitOps Related Practices (CNCF GitOps Working Group), Reconciliation Feedback Loops.
Which of these Git commands will enact a rollback of the configuration to a previous commit?
In GitOps, rollback is performed by reverting the system's Desired State stored in Git. This is done with the git revert command, which creates a new commit that undoes the changes introduced by a previous commit."Because Git provides an immutable history of changes, rollbacks are straightforward. Reverting to a previous configuration is accomplished by reverting the commit in Git, which then allows the reconciler to apply the earlier desired state."Thus, the correct answer is B: git revert.
GitOps Tooling (CNCF GitOps Working Group).
You are implementing GitOps in your organization and have configured the Desired State of your applications in a Git repository. However, during the deployment process, you encounter an error in the configuration. What is the recommended action in this scenario?
Answer(s): C
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 is C: Roll back to the previous working version.
GitOps Principles (CNCF GitOps Working Group).
Post your Comments and Discuss Linux Foundation CGOA exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CGOA content, but please register or login to continue.