23 of 98 questions · Page 2/2 · Gitops Principles · Answers revealed
Which THREE mechanisms can be used to notify a GitOps controller of a change in Git?
Efficient, event-driven notification.
Why this answer
Controllers can detect changes via polling (continuous), webhooks (event-driven), or manual sync requests.
You are debugging a GitOps deployment. The controller shows 'OutOfSync' but the cluster seems to be running correctly. What is the most likely cause?
This is the classic definition of configuration drift in GitOps.
Why this answer
An 'OutOfSync' status indicates that the actual cluster configuration deviates from the declarative state defined in Git.
Which THREE are standard ways to implement GitOps with Helm?
Modern GitOps tools integrate this natively.
Why this answer
Helm can be used by packaging charts in Git, using a GitOps operator to render templates, or by storing values files in Git.
An administrator notices that an engineer manually modified a Service loadBalancerIP in the Kubernetes live cluster using 'kubectl edit'. The cluster is managed by an automated GitOps engine configured in a pull-based model. What will happen during the next reconciliation cycle?
Continuous drift correction enforces the state in Git over any out-of-band manual changes made to the cluster.
Why this answer
In a pull-based GitOps pattern, an agent running inside the cluster continuously monitors both the declared state in Git and the actual state in the cluster. When drift is detected, the controller overwrites the live state with the desired state defined in Git.
Which of the following is NOT a benefit of the GitOps model?
GitOps improves consistency and manageability, not raw compute performance.
Why this answer
GitOps does not necessarily increase the performance of the underlying application; it focuses on deployment and configuration consistency.
What is a 'GitOps Operator'?
The operator is the heart of the GitOps pull-based loop.
Why this answer
An operator is a Kubernetes controller that implements a control loop to continuously reconcile the cluster with the desired state in Git.
What is the relationship between the 'desired state' and the 'actual state' in GitOps?
Reconciliation bridges the gap between the two states.
Why this answer
The goal of GitOps is to make the actual state equal to the desired state.
Which TWO of the following are primary benefits of storing immutable state in Git?
Declarative files in Git replace manual, error-prone configurations.
Why this answer
Immutability and versioning provide a clear audit trail and reliable rollback mechanisms.
Which TWO are examples of 'Drift' in a GitOps environment?
This is classic configuration drift.
Why this answer
Drift is any change to the cluster state that is not reflected in the Git repository.
A senior cloud architect is designing a multi-tenant platform using GitOps. They want to ensure that continuous drift detection and correction operate reliably without causing system instability. Which TWO practices help mitigate risks associated with automated continuous drift correction?
Ignoring fields modified by cluster operators prevents continuous reconciliation loops between the GitOps engine and live cluster controllers.
Why this answer
Automated drift correction can cause feedback loops or resource exhaustion if external mutations (like auto-scalers modifying replica counts or controllers adding status annotations) conflict with Git. Ignoring dynamic runtime fields or using structured sync windows mitigates these risks.
You are implementing a GitOps pipeline for a complex microservices architecture. To satisfy the principle of 'versioned and immutable state', how should you handle environment-specific configurations while maintaining a single source of truth?
Kustomize allows for a declarative, versioned approach to managing variants while keeping a single source of truth.
Why this answer
Using Kustomize bases and overlays allows for a single declarative base while versioning environment-specific patches separately in Git, maintaining immutability.
In a GitOps environment, an engineer manually deletes a Deployment via 'kubectl'. What should happen next to maintain the desired state?
Drift detection and automated correction is a core GitOps principle.
Why this answer
The GitOps controller, such as Argo CD or Flux, performs continuous reconciliation to ensure the cluster state matches the Git repository.
You are troubleshooting a Flux controller that is not reconciling changes. The Git repository is updated, but the cluster remains unchanged. Which component should you inspect first to verify the 'automated pull-based reconciliation'?
These resources define the source and the reconciliation loop for the specific application.
Why this answer
The Kustomization or HelmRelease custom resource defines the link between the repository and the reconciliation loop.
Which of the following actions best aligns with the GitOps principle of 'Automated Pull-Based Reconciliation'?
This describes the pull-based model central to GitOps.
Why this answer
Pull-based reconciliation involves an agent running inside the cluster that actively fetches the desired state from Git, rather than a CI system pushing changes.
What is the primary advantage of storing Kubernetes manifests in a version-controlled repository?
The repository serves as a disaster recovery point for the cluster configuration.
Why this answer
Version control allows for tracking changes, reverting to previous states, and providing a historical audit log.
A company is choosing between a push-based CI/CD pipeline (e.g., executing 'kubectl apply' from GitHub Actions) and a pull-based GitOps controller (e.g., Argo CD or Flux). Which security advantage is uniquely provided by adopting the pull-based architecture?
Because the operator runs inside the target cluster, it pulls manifests internally without requiring external CI runners to hold cluster kubeconfig credentials.
Why this answer
Pull-based reconciliation uses an agent running inside the cluster that reaches out to Git. This eliminates the need to expose cluster API endpoints to external network callers or store cluster admin credentials in external CI systems.
What happens when you delete an application from the Argo CD dashboard without deleting the Git repository?
The controller's job is to enforce the Git state; as long as the Git state exists, the controller will recreate the app.
Why this answer
The application is removed from Argo CD, but if the controller is still configured to watch that repository, it may re-create the application unless the removal is also reflected in Git.
When utilizing Git as the 'Source of Truth' for a cluster, what happens if the cluster state diverges from Git?
Identifying 'Out-of-Sync' status is the first step in reconciliation.
Why this answer
Drift detection allows the GitOps controller to identify when the cluster state has deviated from the declared Git state.
Which THREE components are essential for a robust pull-based GitOps deployment?
The repository is the source of truth.
Why this answer
A robust system requires the controller (the brain), a Git source (the truth), and a cluster (the execution environment).
When defining a declarative desired state in Kubernetes, which attribute is essential to satisfy the 'declarative' principle?
Declarative systems focus on the target state, represented by static configuration.
Why this answer
The manifest should define the final state, not the steps taken to achieve it.
Which TWO benefits does GitOps provide for team collaboration?
This makes communication much easier.
Why this answer
GitOps fosters collaboration by leveraging pull requests for peer reviews and providing a single, transparent record of all changes.
Which THREE principles are foundational to the GitOps model as defined by the CNCF GitOps Working Group?
Automated reconciliation is required to maintain the desired state.
Why this answer
The principles include Declarative state, Versioned/Immutable storage, and Automated reconciliation.
Which TWO characteristics help ensure a GitOps repository is auditable?
This guarantees the integrity of the commit history.
Why this answer
Auditable GitOps relies on commit history (who made the change) and cryptographic signing of commits (verifying the origin of the change).
Ready to test yourself?
Try a timed practice session using only Gitops Principles questions.