exam questions

Exam DP-203 All Questions

View all questions & answers for the DP-203 exam

Exam DP-203 topic 7 question 1 discussion

Actual exam question from Microsoft's DP-203
Question #: 1
Topic #: 7
[All DP-203 Questions]

DRAG DROP -
You need to implement versioned changes to the integration pipelines. The solution must meet the data integration requirements.
In which order should you perform the actions? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:

Show Suggested Answer Hide Answer
Suggested Answer:
Scenario: Identify a process to ensure that changes to the ingestion and transformation activities can be version-controlled and developed independently by multiple data engineers.
Step 1: Create a repository and a main branch
You need a Git repository in Azure Pipelines, TFS, or GitHub with your app.

Step 2: Create a feature branch -

Step 3: Create a pull request -

Step 4: Merge changes -
Merge feature branches into the main branch using pull requests.

Step 5: Publish changes -
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
ItHYMeRIsh
Highly Voted 3 years, 3 months ago
The answer provided is correct
upvoted 42 times
SameerL
2 years, 9 months ago
The provided sequence is correct per below link: https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery
upvoted 10 times
...
...
NaiCob
Highly Voted 3 years, 3 months ago
Before creating a pull request, it is required to save our changes on a feature branch (publish our local changes). So the correct order is: 1. Create a repository and a main branch 2. Create a feature branch 3. Publish changes 4. Create a pull request 5. Merge changes
upvoted 23 times
wwdba
3 years, 1 month ago
I agree. This was my order too. My understanding is: Publish changes = Push the changes to the remote repository
upvoted 1 times
...
corebit
3 years, 3 months ago
@NaiCob I believe the given answer is correct. What changes are published before creating a PR?
upvoted 3 times
NaiCob
3 years, 3 months ago
Before Pull Request you have to publish you local changes
upvoted 1 times
xeti
3 years, 1 month ago
No, the given answer is correct. Publish is done after the merge to collaboration (main) branch and is essentially a CI trigger to update the adf_publish branch.
upvoted 6 times
...
...
...
dev2dev
3 years, 2 months ago
Nope. given answers are correct.
upvoted 2 times
...
Lotusss
2 years, 11 months ago
I agree! Reference: https://www.google.com/search?q=Create+branch+create+feature+branch+create+ull+request&ei=7uFoYr7tO4-VkgWOt6jYAQ&ved=0ahUKEwi-nOOLzrP3AhWPiqQKHY4bChsQ4dUDCA8&uact=5&oq=Create+branch+create+feature+branch+create+ull+request&gs_lcp=Cgdnd3Mtd2l6EAMyBwghEAoQoAE6BwgAEEcQsAM6BQghEKABOggIIRAWEB0QHjoECCEQFUoECEEYAEoECEYYAFCxA1i5KmDXLGgDcAF4AIABnAGIAZgPkgEEMTYuNZgBAKABAcgBCMABAQ&sclient=gws-wiz#kpvalbx=_DeJoYrujKovCkwWT-anIBg18
upvoted 1 times
...
...
seranvijay
Most Recent 5 months ago
Answer is correct https://learn.microsoft.com/en-us/azure/data-factory/source-control#version-control
upvoted 1 times
...
evangelist
9 months ago
Create a repository and a main branch: This is the foundational step where you set up the repository that will contain your project. Create a feature branch: This step allows developers to work on new features or fixes in isolation from the main branch. Publish changes: This step involves pushing local changes to the remote repository, making them available for review and collaboration. Create a pull request: After publishing changes, you create a pull request to propose merging the feature branch into the main branch. Merge changes: This is the final step where changes from the feature branch are merged into the main branch after approval.
upvoted 1 times
...
Adediwura
1 year, 5 months ago
The given answer is correct. Please note that publish change is not same as commiting.
upvoted 2 times
...
kkk5566
1 year, 7 months ago
correct
upvoted 1 times
...
Jerrie86
2 years, 2 months ago
This case study was in my exam word to word. Thanks guys. passed at 970. Just dont do dumps but try to understand the logic via some youtube dp-203 tutorials. There is series by databag.ai. So please study to excel in exam as well in prof life.
upvoted 4 times
...
anks84
2 years, 7 months ago
Given answer and sequence is absolutely correct !!
upvoted 2 times
...
Deeksha1234
2 years, 8 months ago
given answer is correct
upvoted 2 times
...
hbad
2 years, 11 months ago
Given answer is correct: 1. Create a repository and a main branch -You need a Git repository in Azure Pipelines, TFS, or GitHub with your app. 2. Create a feature branch - 3. Create a pull request - you propose that changes you've made on a head branch should be merged 4. Merge changes -merge feature branches into the main/collaboration branch using pull requests. 5. Publish changes -after you merged changes to the collaboration branch (main is default), click Publish to manually publish. https://docs.microsoft.com/en-us/azure/data-factory/source-control https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
upvoted 3 times
...
Send2
2 years, 11 months ago
https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow
upvoted 1 times
...
Kondzio
3 years, 1 month ago
I think it's correct. Publish step is the last one, because there is no auto-publish on the master branch by default
upvoted 2 times
...
edba
3 years, 3 months ago
I think answer is correct. Pls refer to https://docs.microsoft.com/en-us/azure/data-factory/source-control#version-control
upvoted 4 times
...
Canary_2021
3 years, 3 months ago
The answers are correct. https://www.youtube.com/watch?v=cLf3nAiGG3Q
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago