nerdexam
MicrosoftMicrosoft

DP-203 · Question #366

DP-203 Question #366: Real Exam Question with Answer & Explanation

The correct answer is B: No. Enabling Git integration changes the save mechanism going forward - it allows future changes to be committed to a branch even before validation passes - but it does not retroactively preserve unsaved in-memory pipeline work that already cannot be saved. When you configure Git int

Submitted by yasin.bd· Mar 30, 2026Develop data processing

Question

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?

Options

  • AYes
  • BNo

Explanation

Enabling Git integration changes the save mechanism going forward - it allows future changes to be committed to a branch even before validation passes - but it does not retroactively preserve unsaved in-memory pipeline work that already cannot be saved. When you configure Git integration on an existing ADF instance, the setup process syncs with the published state of the service; any unsaved, unvalidated work currently in Studio is not carried over, meaning the complex pipeline you just built would be lost.

Option A is wrong because Git integration is a source control configuration change, not a mechanism to rescue currently unsaved pipeline state; the validation errors remain and the unsaved work is discarded during the integration setup.

The correct approach in this scenario is to export the pipeline as an ARM template (via the "Export ARM Template" option), which serializes the current pipeline definition regardless of validation errors and lets you preserve the logic externally - this is what the "Yes" answer in the sibling question covers.

Memory tip: Think of it this way - Git integration helps you save drafts going forward, but it can't save what was never committed to begin with. "Export ARM Template = save now, fix later; Enable Git = save strategy for the future."

Topics

#Azure Data Factory#Pipeline development#Git integration#Validation

Community Discussion

No community discussion yet for this question.

Full DP-203 PracticeBrowse All DP-203 Questions