Azure Data Factory Git Workflow: Publishing Changes
You have an Azure data factory connected to a Git repository that contains the following branches: • main: Collaboration branch • abc: Feature branch • xyz: Feature branch You save changes to a pipeline in the xyz branch. You need to publish the changes to the live service. What should you do first?
Publish the data factory.
Create a pull request to merge the changes into the main branch. Source Reference Answer
Create a pull request to merge the changes into the abc branch.
Push the code to a remote origin.
Community Votes
B
100%
100% of anonymous learners picked answer B.
Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests your understanding of the separation between development (feature branches) and production deployment (main branch), specifically identifying that PR creation precedes the publish action.
This question tests the correct Azure Data Factory Git integration workflow for deploying changes from a feature branch to the live service. Community consensus confirms that merging into the main collaboration branch via a pull request is the mandatory first step before publishing.
Candidates often select 'Publish the data factory' immediately, failing to realize that publishing only deploys the current state of the main branch, not the unmerged feature branch content.
Community Discussion (9 comments)
NAWRESS96👍 1
Correct . C'est la première étape appropriée. Vous devez créer une pull request pour fusionner vos modifications de la branche xyz dans la branche main. Une fois que cette PR est approuvée et fusionnée, vous pourrez publier les changements dans le service en direct.
606a82e👍 1Selected: B
correct
Danweo👍 1Selected: B
B is correct
princepark👍 1Selected: B
Save changes to a pipeline in the xyz branch means that the changes are Published in the data factory
Alongi👍 1Selected: A
Why not A? You should Publish the save changes before every pull requests
DiLsH👍 1Selected: B
Correct
jsav1👍 3Selected: B
Correct, always merge the feature into to the main branch and then publish the main branch
moize👍 1
Bonne réponse : B.
jongert👍 4
Correct, simply best practices for version control. Each feature branch develops changes, then should create pull requests to merge with main branch before publishing.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Log in to comment, report an error, or add a note about this question.
Expert Analysis
Why the Answer Is Correct
In Azure Data Factory's Git integration, the 'main' branch serves as the collaboration and production baseline. When you develop in a feature branch (like 'xyz'), those changes are isolated. To deploy them to the live service, you must first merge them into the main branch via a Pull Request (PR). This ensures code review and stability before the 'Publish' action syncs the main branch to the live ARM resources.
Why the Other Options Are Wrong
Option A is incorrect because clicking 'Publish' only pushes the contents of the currently selected branch (usually main) to the live service; it does not automatically include unmerged changes from 'xyz'. Option C suggests merging into another feature branch ('abc'), which violates standard branching strategies where all features converge on main. Option D refers to local Git operations, but Azure Data Factory manages the remote synchronization internally through its UI-based Publish button, making manual git push irrelevant in this context.
Community Comment Notes
Comments [1], [2], [3], and [9] strongly support option B, emphasizing that best practices require merging feature branches into main before publishing. Comment [4] correctly notes that saving changes in the UI publishes them to the repo, but not necessarily to the live service if they aren't in main. Comment [5] highlights the common confusion between saving/publishing to the repo versus deploying to the live environment.