DP-500 · Question #56
You need to configure a source control solution for Azure Synapse Analytics. The solution must meet the following requirements: Code must always be merged to the main branch before being published…
This question tests knowledge of Azure Synapse Analytics Git integration, specifically how to configure collaboration branches, publish branches, and feature branches to enforce a proper CI/CD workflow.
Question
- Code must always be merged to the main branch before being published, and the main branch must be used for publishing resource
- The workspace templates must be stored in the publish branch.
- A branch named dev123 will be created to support the development of a new feature. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.
Explanation
This question tests knowledge of Azure Synapse Analytics Git integration, specifically how to configure collaboration branches, publish branches, and feature branches to enforce a proper CI/CD workflow.
Approach. The correct configuration sets 'main' as the Collaboration Branch - this is the branch Synapse publishes from, satisfying the requirement that code must be merged to main before publishing. The Publish Branch should be set to 'workspace_publish' (Synapse's default), which is where Synapse automatically stores generated ARM/workspace templates upon publishing, satisfying the workspace template storage requirement. Finally, the feature branch 'dev123' should be created from 'main' (the collaboration branch), so developers work in isolation and merge back via pull request before any publish action can occur. This enforces the merge-before-publish governance model Synapse Git integration is designed around.
Concept tested. Azure Synapse Analytics source control configuration: the distinction between the Collaboration Branch (where merged code lives and publishing is triggered from) and the Publish Branch (where Synapse stores generated workspace ARM templates), plus the proper Git branching strategy for feature development (create feature branches from the collaboration branch).
Reference. https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/source-control
Topics
Community Discussion
No community discussion yet for this question.