DP-600 Deployment Pipelines and CI/CD 2 — Questions and Answers
Question 1: Which Git providers are natively supported for Microsoft Fabric workspace Git integration?
- Azure DevOps and GitHub (Correct answer)
- Azure DevOps, GitHub, and GitLab
- GitHub and Bitbucket
- Azure DevOps only
Correct answer: Azure DevOps and GitHub
Fabric workspace Git integration natively supports Azure DevOps Repos and GitHub as source control providers.
Question 2: What is the purpose of the .platform file found in each item folder of a Fabric Git repository?
- It stores item metadata such as item type, display name, and logical ID (Correct answer)
- It contains the Fabric workspace connection settings for the repository
- It defines deployment pipeline rules for the item
- It stores role-based access control settings for the item
Correct answer: It stores item metadata such as item type, display name, and logical ID
The .platform file stores essential item metadata — including item type and logical ID — that Fabric uses to track and identify items during Git sync operations.
Question 3: When a Fabric workspace is connected to a Git branch for the first time, what happens to existing workspace items?
- Fabric exports existing workspace items to the Git repository branch (Correct answer)
- Fabric imports all items from the repository, replacing existing workspace content
- Fabric creates empty placeholder folders in the repository
- Fabric performs a three-way merge between workspace and repository content
Correct answer: Fabric exports existing workspace items to the Git repository branch
On initial connection, Fabric exports the current workspace items to the connected Git branch, establishing the initial baseline in source control.
Question 4: What does the 'Update from Git' operation do in Fabric workspace Git integration?
- Pulls the latest changes from the connected Git branch and applies them to the workspace (Correct answer)
- Pushes workspace changes to the Git repository as a new commit
- Creates a pull request from uncommitted workspace changes
- Merges two branches in the connected Git repository
Correct answer: Pulls the latest changes from the connected Git branch and applies them to the workspace
Update from Git pulls the latest committed changes from the connected branch and synchronizes them into the workspace, updating workspace items accordingly.
Question 5: What file format does Fabric use to store semantic model definitions in a Git repository?
- TMDL (Tabular Model Definition Language) (Correct answer)
- PBIX binary format
- JSON with embedded DAX expressions
- XML using the XMLA standard
Correct answer: TMDL (Tabular Model Definition Language)
Fabric stores semantic model definitions using TMDL (Tabular Model Definition Language), a human-readable text format well-suited for version control diffing.
Question 6: When both the workspace and the connected Git branch have conflicting changes to the same item, how does Fabric resolve the conflict?
- The user must manually choose to keep either workspace changes or Git changes (Correct answer)
- Git branch changes always take priority over workspace changes automatically
- Workspace changes always take priority over Git changes automatically
- Fabric automatically performs a three-way merge of the item definitions
Correct answer: The user must manually choose to keep either workspace changes or Git changes
Fabric presents conflicts to the user and requires a manual decision to keep either the workspace version or the Git version; there is no automatic merge for item definitions.
Question 7: Which of the following is NOT a capability of Fabric workspace Git integration?
- Scheduling automatic workspace-to-Git syncs on a time-based interval (Correct answer)
- Undoing uncommitted workspace changes by reverting to the Git state
- Viewing which workspace items have uncommitted pending changes
- Connecting a workspace to a specific feature branch in the repository
Correct answer: Scheduling automatic workspace-to-Git syncs on a time-based interval
Fabric Git sync must be triggered manually or via the REST API; there is no built-in scheduler for automatic periodic synchronization.
Which Git providers are natively supported for Microsoft Fabric workspace Git integration?