Which statement best describes the role of Git in Fabric’s CI/CD?

• A. Automated testing
• B. Deployment to environments
• C. Version control and branches for collaboration
• D. Data lineage

Answer: (C)

Git is the version control backbone of Fabric’s CI/CD workflow. It stores the complete history of pipeline definitions, notebooks, and configuration, so teams can track what changed, when, and by whom. This history enables reproducible builds, audits, and safe rollbacks. Branches let collaborators work in isolation on features or fixes without disrupting the main pipeline, using commits to capture changes and pull requests to review and merge into the main line. When changes reach the main branch, the surrounding CI/CD tooling can automatically run tests and trigger deployments. This setup emphasizes collaboration and traceability, rather than performing tests or deployments itself, which are handled by the CI/CD processes. Data lineage, meanwhile, relates to where data originates and how it moves, which isn’t something Git tracks—the focus here is on code and configuration changes and how they are coordinated across the team.