Answer: the ability to save without publishing, the ability to save pipelines that have validation issues

When integrating Azure Data Factory with GitHub for source control, two key advantages emerge: **C. The ability to save without publishing** - This is a fundamental benefit of GitHub integration. Without source control, Data Factory requires publishing changes to the service for them to be saved. With GitHub integration, developers can save their work-in-progress pipelines directly to the repository without affecting the published pipelines in the Data Factory service. This enables iterative development, experimentation, and collaboration without disrupting production environments. **D. The ability to save pipelines that have validation issues** - In the standard Data Factory workflow without source control, pipelines with validation errors cannot be saved. However, when integrated with GitHub, developers can commit pipelines to the repository even when they contain validation issues. This allows teams to save incomplete work, collaborate on fixing issues, and maintain a complete development history without being blocked by temporary validation problems. **Why other options are less suitable:** - **A. Additional triggers** - GitHub integration does not provide additional pipeline triggers. Triggers in Data Factory are configured separately and are not enhanced by source control integration. - **B. Lower pipeline execution times** - Source control integration does not impact pipeline execution performance. Execution times are determined by data volume, transformation complexity, and resource configuration, not by version control capabilities. The GitHub integration primarily enhances development workflows, collaboration, and change management rather than operational performance or trigger functionality.

Author: LeetQuiz Editorial Team