CGOA Gitops Principles Practice Question
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?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configuring the GitOps controller to ignore specific dynamic fields updated by in-cluster controllers, such as 'spec.replicas' managed by a HorizontalPodAutoscaler (HPA).
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.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Granting full cluster-admin permissions to all application developers so they can manually disable drift correction during deployments.
Why it's wrong here
Broad administrator access undermines security and bypasses the governed GitOps pipeline.
- ✗
Disabling Git versioning so that drift detection compares live state against an unversioned NFS network share.
Why it's wrong here
Removing Git versioning violates core GitOps principles.
- ✓
Configuring the GitOps controller to ignore specific dynamic fields updated by in-cluster controllers, such as 'spec.replicas' managed by a HorizontalPodAutoscaler (HPA).
Why this is correct
Ignoring fields modified by cluster operators prevents continuous reconciliation loops between the GitOps engine and live cluster controllers.
- ✗
Setting the reconciliation loop interval to run once every 30 seconds while forcing a full cluster node reboot on every iteration.
Why it's wrong here
Rebooting nodes during reconciliation cycles causes massive service disruption and is not part of GitOps operations.
- ✓
Utilizing dry-run or diff-matching alerts to notify teams of unexpected drift before automated self-healing applies destructive changes to critical resources.
Why this is correct
Alerting on drift or staging automated corrections for sensitive resources prevents catastrophic data loss from unintentional manual cluster edits being wiped out.
About these practice questions
Courseiva writes every CGOA question from scratch — 325 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official CNCF / Linux Foundation exam blueprint
This CGOA practice question is part of Courseiva's free CNCF / Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CGOA exam.