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…

Question

Options

• APublish the data factory.
• BCreate a pull request to merge the changes into the main branch.
• CCreate a pull request to merge the changes into the abc branch.
• DPush the code to a remote origin.

• A
  11% (7)
• B
  81% (51)
• C
  3% (2)
• D
  5% (3)

Explanation

In Azure Data Factory with Git integration, the collaboration branch (main) is the only branch that can be published to the live service - so changes in any feature branch must first be merged into main via a pull request before publishing is possible.

Why the distractors are wrong:

• A (Publish the data factory) fails because you cannot publish directly from a feature branch like xyz; ADF only publishes from the collaboration branch.
• C (Merge into abc) is wrong because abc is just another feature branch, not the collaboration branch - merging there still leaves you unable to publish.
• D (Push to remote origin) is irrelevant here; the branch is already in the Git repo, and pushing alone doesn't satisfy the requirement to get changes into the collaboration branch.

Memory tip: Think of the collaboration branch as the "launch pad" - no matter which feature branch you work in, your code must land on that launch pad (main) before it can take off to the live service.

No community discussion yet for this question.