Question 1
Application DeliveryHow does GitOps facilitate collaboration between development and operations teams?
Correct answer: C
Explanation
GitOps centers on a shared Git repository as the single source of truth, so both development and operations work from the same versioned configuration. Pull requests provide a standard way to "propos[e] and review" infrastructure and application changes, creating an auditable collaboration workflow before changes are applied.
Why each option is right or wrong
A. By requiring operations teams to manually approve every developer commit.
B. By providing separate Git repositories for developers and operators with no overlap.
C. By using a shared Git repository and pull requests as a common mechanism for proposing and reviewing infrastructure and application changes.
GitOps is built around Git as the authoritative record of desired state, so both application and infrastructure changes are made through the same version-controlled workflow rather than ad hoc direct edits. Pull requests are the standard review gate in Git-based workflows, giving teams a documented, auditable mechanism to propose changes, review diffs, and approve them before deployment.
D. By eliminating the need for an operations team entirely.
E. By forcing developers to manage the underlying Kubernetes infrastructure.