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:
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
The answer provided is correct
The provided sequence is correct per below link: https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery
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
@NaiCob I believe the given answer is correct. What changes are published before creating a PR?
Before Pull Request you have to publish you local changes
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.
Nope. given answers are correct.
I agree. This was my order too. My understanding is: Publish changes = Push the changes to the remote repository
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
I think answer is correct. Pls refer to https://docs.microsoft.com/en-us/azure/data-factory/source-control#version-control
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.
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
The answers are correct. https://www.youtube.com/watch?v=cLf3nAiGG3Q
I think it's correct. Publish step is the last one, because there is no auto-publish on the master branch by default
given answer is correct
Given answer and sequence is absolutely correct !!
The given answer is correct. Please note that publish change is not same as commiting.
https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow
correct
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.