GitOps enhancesDevSecOpsby ensuring security-related configurations and changes are stored in version control, where acomplete audit historyis available. This provides traceability, accountability, and compliance enforcement.
“With GitOps, the entire version history of desired state changes is stored immutably in Git. This audit trail supports security and compliance goals in DevSecOps practices.”
Thus, the correct answer isB.
[References:GitOps Related Practices (CNCF GitOps Working Group), DevSecOps Integration., ===========]
Question 2
When using Kustomize, how are resources, configurations, and customizations commonly organized?
Options:
A.
By specifying all resources inline in the customization file.
B.
In separate configuration files for each resource.
C.
In a single configuration file.
D.
Using a combination of folder directories and referenced folder/file paths.
Answer:
D
Explanation:
Kustomize is a GitOps tool for managing Kubernetes configurations declaratively. It uses afolder structure with configuration filesand akustomization.yamlfile that references resources and overlays. This enables customization without modifying the base manifests.
“Kustomize allows customization of Kubernetes manifests by organizing resources in directories and referencing them through file paths in a kustomization file. This directory-based approach supports overlays, reusability, and modular configuration.”
Thus, the correct answer isD.
[References:GitOps Tooling (CNCF GitOps Working Group), Kustomize practices., ===========]
Question 3
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., ]