A cloud architect needs to change the network configuration at a company that uses GitOps...

Comprehensive and Detailed Explanation From Exact Extract:

With GitOps, all infrastructure changes are tracked as code and committed to version-controlled repositories. When the main branch is protected, changes should not be committed directly. Instead, best practices require that a new feature or change branch be created, followed by a pull request (PR) for peer review and approval before merging into the protected branch.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Infrastructure as Code and GitOps”:

“In GitOps workflows, changes are made in feature branches, reviewed via pull requests, and merged into protected branches only after validation, ensuring auditability and control over infrastructure deployments.”

Other options:

A. Direct commits to protected branches are restricted and violate GitOps practices.

C. The development branch may exist, but the question specifies main is the default, and the correct process requires a PR.

D. Rebase is for integrating histories, not submitting approved changes.