Certified GitOps Associate Exam Questions and Answers
Question 17
In GitOps, what is a pull-based approach?
Options:
A.
A pull-based approach is when developers manually push changes to the GitOps system, which then applies them automatically.
B.
A pull-based approach is when the GitOps system sends notifications to developers to apply changes from the Git repository manually.
C.
A pull-based approach is when the Git repository automatically pushes changes to the GitOps system, which then applies them.
D.
A pull-based approach is when the GitOps system continuously polls the Git repository for changes and applies them automatically.
Answer:
D
Explanation:
In GitOps,pull-based deploymentis fundamental. Instead of pushing changes into a cluster, GitOps agents running inside the cluster continuouslypull from Gitto reconcile desired state.
“GitOps uses a pull-based model: agents inside the cluster continuously poll the Git repository for desired state changes. If changes are found, they reconcile the live system automatically to match the declared state.”
This ensures secure, automated, and consistent deployments.
Thus,Dis correct.
[References:GitOps Principles (CNCF GitOps Working Group), Pull-based Reconciliation Model.]
Question 18
In the context of GitOps, what happens to a GitOps-managed Kubernetes cluster if there is drift divergence?
Options:
A.
The GitOps-managed Kubernetes cluster ignores the drift divergence and continues to operate as it is.
B.
The GitOps-managed Kubernetes cluster automatically reconciles the drift divergence to return the cluster to the Desired State.
C.
The GitOps-managed Kubernetes cluster notifies the administrator about the drift divergence and waits for manual intervention.
D.
The GitOps-managed Kubernetes cluster rolls back to the previous known state before the drift divergence occurred.
Answer:
B
Explanation:
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.
[References: GitOps Principles (CNCF GitOps Working Group), GitOps Principles Document —Principle 4: Software agents automatically pull the desired state declarations from the source and continuously observe actual system state, reconciling differences., ]
