325 questions total · 5pages · All types, answers revealed
Page 5 of 5
In a GitOps workflow, what is the best way to handle a configuration that must be different for production versus development clusters?
Overlays are the standard solution for environment-specific differences.
Why this answer
Using Kustomize overlays allows you to maintain a common base and modify specific values for each environment.
Which THREE of these practices are essential to successfully transition from traditional CI/CD to GitOps?
Declarative files are required for GitOps reconciliation.
Why this answer
Successful transition requires moving away from imperative commands, adopting declarative configuration, and centralizing the source of truth.
What is the purpose of 'App-of-Apps' pattern in Argo CD?
This allows for hierarchical management of multiple services.
Why this answer
The App-of-Apps pattern allows managing multiple applications using a single parent application, simplifying deployment for complex architectures.
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.
Why is 'Git' used as the source of truth rather than a standard database?
The Git workflow is specifically optimized for tracking changes over time.
Why this answer
Git provides built-in version control, audit trails, and collaborative workflows that databases lack.
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 THREE of the following are critical security considerations for a GitOps implementation?
Ensures the integrity and authenticity of configuration changes.
Why this answer
Access control, secure credential storage, and commit signing are essential for security.
Which TWO of the following are common GitOps challenges?
Manual changes often cause drift.
Why this answer
Managing secrets securely and handling drift are the most frequent challenges in GitOps environments.
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.
You are implementing a multi-environment strategy. Which Git branching strategy best supports GitOps?
This allows for environment-specific configuration while maintaining a single source of truth.
Why this answer
Environment-specific branches or directory-based separation (using Kustomize or Helm) allow for tracking changes across dev, staging, and prod independently.
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.
Which TWO of the following are valid reasons to maintain a clear separation between the CI pipeline and the GitOps controller?
Reconciliation is an ongoing process, whereas CI is a discrete, event-based process.
Why this answer
Separation of concerns ensures that the build pipeline focuses on artifacts and the GitOps controller focuses on state reconciliation, which also improves security by limiting cluster access.
You are designing a multi-cluster deployment with Argo CD. You want to avoid defining 50 individual Application manifests. Which feature should you use?
ApplicationSets automate the generation of Applications for multiple clusters.
Why this answer
ApplicationSets use generators (like the Cluster generator) to dynamically create Applications based on cluster list, significantly reducing configuration overhead.
Which of the following is a key advantage of using a 'pull' based GitOps model (like Flux or ArgoCD) over a 'push' based CI/CD pipeline?
The cluster pulls from Git, so the CI doesn't need write access.
Why this answer
Pull models don't require the GitOps tool to have cluster admin credentials stored in the CI system, enhancing security.
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.
When using an 'Image Updater' with a GitOps operator, what is the automated workflow?
This is the standard flow: watch registry -> update Git -> operator pulls change.
Why this answer
The updater monitors registries for new images and updates the Git repository automatically.
Which THREE of the following are best practices for managing GitOps secrets?
SealedSecrets allows keeping secrets in Git while preventing unauthorized access.
Why this answer
Secrets should be encrypted, managed outside Git, and rotated frequently.
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).
An administrator notices that the 'sync' status of an Argo CD application is 'Synced' but the health status is 'Degraded'. What does this indicate?
Sync status refers to configuration parity, while health status refers to runtime execution success.
Why this answer
The desired state in Git has been successfully applied to the cluster, but the workloads (e.g., Pods) are failing to run correctly.
Page 5 of 5
Practice CGOA by domain
Target a specific domain to shore up weak areas.
See all domains with question counts →