Exam DP-203 All Questions

View all questions & answers for the DP-203 exam

Exam DP-203 topic 2 question 95 discussion

Actual exam question from Microsoft's DP-203

Question #: 95
Topic #: 2

DRAG DROP
-

You have a project in Azure DevOps that contains a repository named Repo1. Repo1 contains a branch named main.

You create a new Azure Synapse workspace named Workspace1.

You need to create data processing pipelines in Workspace1. The solution must meet the following requirements:

• Pipeline artifacts must be stored in Repo1
• Source control must be provided for pipeline artifacts.
• All development must be performed in a feature branch.

Which four actions should you perform in sequence in Synapse Studio? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Show Suggested Answer

Suggested Answer:

by FRANCIS_A_M at April 3, 2023, 5:51 p.m.

Comments

Submit Cancel

SinSS

Highly Voted 2 years ago

Configure a code repo and select Repo1 Set the main branch as the collaboration branch Create a new brach Create pipeline artifacts and save them in the new branch

upvoted 31 times

Fusejonny1

1 year, 3 months ago

In the context of Azure Synapse Studio, it's recommended not to use the 'main' branch as a collaboration branch. Here's why: - Deployment Branch: The 'main' branch serves as the source of truth for your production-ready pipelines. Changes made directly in 'main' could potentially introduce instability or untested features into the production environment. -Code Stability: Isolating development work in separate collaboration branches protects your 'main' branch from unintended changes or broken code during development. -Review Process: Collaboration branches allow for code reviews, testing, and approval processes before merging changes into the 'main' branch, ensuring higher code quality.

upvoted 2 times

...

j4g092t

1 year, 8 months ago

Isn't the main branch by default the collaboration branch?

upvoted 1 times

[Removed]

1 year, 3 months ago

Your Azure Repos collaboration branch that is used for publishing. By default, it's main. https://learn.microsoft.com/en-us/azure/data-factory/source-control

upvoted 1 times

...

macinpune9

1 year, 5 months ago

This is wrong, given answer by exam topics is right

upvoted 3 times

...

mhi

Highly Voted 2 years ago

Shouldn't you merge the new branch into the main branch?

upvoted 16 times

Pian12345

6 months, 3 weeks ago

totally agree with this, I was looking for that option in the possible Actions and couldn't find any.

upvoted 1 times

...

peches

1 year, 11 months ago

Agree, you create a feature branch from the collaboration branch, work on it, and after you finished you merge back to the collaboration branch (by default is main). Source: https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/source-control#version-control

upvoted 5 times

...

evangelist

Most Recent 10 months, 3 weeks ago

Configure a code repository and select Repo1. Set the main branch as the collaboration branch. Create a new branch. Create pipeline artifacts and save them in the new branch.

upvoted 1 times

...

Sleuth

12 months ago

Read question first line again don't know why you all missed it, the top line says code repository Repo1 exists and has main branch therefore: 1. Set the main branch as collaboration branch. 2. Create a new branch. 3. Create a pull request to merge the contents of main branch to new branch. (You do this step to make new branch up-to-date to main branch) 4. Create pipeline artifacts in the new branch

upvoted 2 times

Sleuth

12 months ago

Ignore you might have to configure repo in local before doing any operation

upvoted 1 times

...

Mausar

1 year, 2 months ago

I think we could exclude two options, one is wrong and the other doesn´t make sense: - You do not create a PR to merge the contents of the "main" branch to "feature" branch, it´s from the "feature" into the "main" branch. - We don´t create the artifacts for the first time directly on the main branch and then fork to a new branch, you create directly on the new feature branch. This leaves four available options: - Configure a code repository and select Repo1 - Set the main branch as the collaboration branch (remember that repo was already created inside DevOps, a generic git project) - Create a new branch - Create pipelines artifacts and save in the new branch

upvoted 5 times

...