DP-600 Deployment Pipelines and CI/CD 2

Question 1

Which Git providers are natively supported for Microsoft Fabric workspace Git integration?

Accepted Answer

Azure DevOps and GitHub

Answer

Azure DevOps, GitHub, and GitLab

Answer

GitHub and Bitbucket

Answer

Azure DevOps only

Question 2

What is the purpose of the .platform file found in each item folder of a Fabric Git repository?

Accepted Answer

It stores item metadata such as item type, display name, and logical ID

Answer

It contains the Fabric workspace connection settings for the repository

Answer

It defines deployment pipeline rules for the item

Answer

It stores role-based access control settings for the item

Question 3

When a Fabric workspace is connected to a Git branch for the first time, what happens to existing workspace items?

Accepted Answer

Fabric exports existing workspace items to the Git repository branch

Answer

Fabric imports all items from the repository, replacing existing workspace content

Answer

Fabric creates empty placeholder folders in the repository

Answer

Fabric performs a three-way merge between workspace and repository content

Question 4

What does the 'Update from Git' operation do in Fabric workspace Git integration?

Accepted Answer

Pulls the latest changes from the connected Git branch and applies them to the workspace

Answer

Pushes workspace changes to the Git repository as a new commit

Answer

Creates a pull request from uncommitted workspace changes

Answer

Merges two branches in the connected Git repository

Question 5

What file format does Fabric use to store semantic model definitions in a Git repository?

Accepted Answer

TMDL (Tabular Model Definition Language)

Answer

PBIX binary format

Answer

JSON with embedded DAX expressions

Answer

XML using the XMLA standard

Question 6

When both the workspace and the connected Git branch have conflicting changes to the same item, how does Fabric resolve the conflict?

Accepted Answer

The user must manually choose to keep either workspace changes or Git changes

Answer

Git branch changes always take priority over workspace changes automatically

Answer

Workspace changes always take priority over Git changes automatically

Answer

Fabric automatically performs a three-way merge of the item definitions

Question 7

Which of the following is NOT a capability of Fabric workspace Git integration?

Accepted Answer

Scheduling automatic workspace-to-Git syncs on a time-based interval

Answer

Undoing uncommitted workspace changes by reverting to the Git state

Answer

Viewing which workspace items have uncommitted pending changes

Answer

Connecting a workspace to a specific feature branch in the repository