Can Enabling Git Integration Allow Saving an Unpublished ADF Pipeline?

Azure Data Factory Authoring & Source Control

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure subscription that contains an Azure data factory named ADF1. From Azure Data Factory Studio, you build a complex data pipeline in ADF1. You discover that the Save button is unavailable, and there are validation errors that prevent the pipeline from being published. You need to ensure that you can save the logic of the pipeline. Solution: You enable Git integration for ADF1. Does this meet the goal?

Yes Source Reference Answer
No

Community Votes

62%

38%

62% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests the distinction between Live Mode and Git Mode, trapping candidates who confuse resolving validation errors with the ability to save incomplete drafts.

This question evaluates your understanding of Azure Data Factory modes and draft persistence. Community consensus confirms that enabling Git integration switches the workspace to Git mode, bypassing strict validation requirements and allowing incremental saves.

Many test-takers choose No because they assume validation errors must be fixed before any workflow step can proceed, failing to recognize that Git mode explicitly permits saving unvalidated JSON drafts.

Community Discussion (14 comments)

lola_mary5 👍 10 Selected: A

Partial saves: "Whether your pipelines are not finished or you simply don't want to lose changes if your computer crashes, git integration allows for incremental changes of data factory resources regardless of what state they are in." https://learn.microsoft.com/en-us/azure/data-factory/source-control

ddhoogduin 👍 6 Selected: B

Git configuration is already enabled otherwise the "Save" option would be a "Publish" option.

renan_ineu 👍 1 Selected: A

The answer is YES: "When authoring against the data factory service, you can't save changes as a draft and all publishes must pass data factory validation. Whether your pipelines are not finished or you simply don't want to lose changes if your computer crashes, git integration allows for incremental changes of data factory resources regardless of what state they are in. Configuring a git repository allows you to save changes, letting you only publish when you have tested your changes to your satisfaction." https://learn.microsoft.com/en-us/answers/questions/391324/save-option-not-enabled

Danweo 👍 1 Selected: A

Don't overthink it, you enable git so you can save it. This is not about fixing the problem just making sure we can save what we have so far.

Sr18 👍 4

Answer is A 100%. Reason: Save button is unavailable means git is not enabled or I say you are in live mode you will see only Publish icon. In that case there is no way you can Publish the code. So you need to enable the GIT to save the code, but switching to git mode from live mode with remove the changes in live mode, so go to json view and copy the code. Discard changes switch to git mode, create new pipeline and paste the copied json in the json view and you can save the code now

jpgsa11 👍 1

Enabling Git Integration is just the first step. Doesn't necessarily allow to have a backup. JSON file on the other hand its different

[Removed] 👍 3 Selected: B

B. No Enabling Git integration for ADF1 wouldn't directly address the immediate need to save the logic of the pipeline if the Save button is unavailable due to validation errors. Git integration allows for version control and collaboration but doesn't inherently resolve the issue of saving the pipeline's logic when there are validation errors preventing it from being published. You'd still need to address the validation errors before being able to successfully save the pipeline.

Alongi 👍 1 Selected: A

It's A

poesklap 👍 1 Selected: B

Enabling Git integration for Azure Data Factory (ADF) does not directly address the issue of validation errors preventing the pipeline from being published. Git integration allows you to manage your ADF resources using source control and enables collaboration among multiple developers. It doesn't inherently fix validation errors.

MBRSDG 👍 2 Selected: A

As stated, this question is a bit misleading. "You need to ensure that you can save the logic of the pipeline" means "you have to prevent the situation in which already working pipelines are damaged by buggy implementations". If you have the working, not buggy, code already inside the repository, you can create a new branch and do the updates there. If there's a error, it is contained inside the feature branch and not inside the main branch, which keeps working fine.

Delphin_8150 👍 1 Selected: A

Answer should be A

Alongi 👍 2 Selected: B

No, enabling Git integration alone does not directly address the immediate goal of saving the logic of the pipeline and resolving validation errors in Azure Data Factory Studio. You need to fix the validation errors and save the changes locally within the studio before enabling Git integration for long-term version control.

ELJORDAN23 👍 4 Selected: A

Although the validation might be wrong, enablng the git integration allows you to save your datasets, pipelines and everything else as json files in your git repo, so A) is correct.

jongert 👍 3

Safe to assume that enabling git integration also means setting up the repo and branches, then it would allow saving. Would answer yes.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Enabling Git integration transitions Azure Data Factory from Live Mode to Git Mode. In Live Mode, the platform enforces strict validation on every publish and does not support draft saving. Once Git is configured, ADF stores pipelines and datasets as JSON files in a connected repository, allowing developers to save incremental changes regardless of whether the code passes validation or is fully complete.

Why the Other Options Are Wrong

Selecting No reflects a misunderstanding of the scenario's primary objective, which is simply to save the pipeline logic, not to resolve validation failures. While Git integration does not automatically fix broken configurations or trigger successful validation, it directly satisfies the goal by providing a persistent, version-controlled storage mechanism for unvalidated work.

Community Comment Notes

Comment [1] and [9] accurately reference Microsoft documentation, emphasizing that Git integration enables incremental resource changes independent of their current state. Comment [3] provides crucial context regarding the user interface, noting that the absence of a Save button signals Live Mode, whereas enabling Git restores draft-saving functionality. Several users also highlight that copying JSON views or discarding live changes are preliminary steps when switching modes, but the core solution remains Git activation.

Official Reference

https://learn.microsoft.com/en-us/azure/data-factory/source-control

Exam Strategy

Always isolate the exact action requested in the scenario, such as 'save' versus 'fix' or 'publish'. When ADF validation blocks your workflow, prioritize Git integration as the architectural pattern designed to enable offline drafting and continuous version control.

Related Analysis

← Back to DP-203 Study Guide