What is the role of Git in the CI/CD process in Fabric?

• A. Git is used to deploy code changes to different environments.
• B. Git is used for automated testing of code changes.
• C. Git automatically consolidates pipelines across projects.
• D. Git lets your team collaborate using branches, and provides version control. It helps manage incremental code changes, and see code history.

Answer: (D)

Git in a Fabric CI/CD setup is about version control and collaboration. It serves as the single source of truth for code, allowing teams to work in parallel through branches, commits, and a complete history of changes. Each change is captured as a commit, branches let you isolate features or fixes, and pull requests enable code review and traceability. In the Fabric CI/CD workflow, pipelines respond to commits or PRs, build and test the code, and deploy, but the versioning and collaboration core comes from Git. This is why the described role fits best: it emphasizes collaboration using branches, robust version control, the management of incremental changes, and the ability to see code history. Deployment, automated testing performed within pipelines, or cross-project pipeline consolidation are handled by the CI/CD tooling rather than Git itself.