DP-600 Deployment Pipelines and CI/CD 3

Question 1

Which Microsoft Fabric REST API operation is used to programmatically trigger a deployment between pipeline stages?

Accepted Answer

POST /v1/pipelines/{pipelineId}/deploy

Answer

POST /v1/workspaces/{workspaceId}/promote

Answer

PUT /v1/deployments/{stageId}/trigger

Answer

POST /v1/items/{itemId}/publish

Question 2

What is the recommended approach for handling different data source connections across Development, Test, and Production stages in Fabric deployment pipelines?

Accepted Answer

Configure deployment rules to automatically override data source parameters per stage

Answer

Create separate semantic model copies for each environment with hardcoded connections

Answer

Store connection strings in OneLake files and reference them dynamically at runtime

Answer

Manually update connection strings in each workspace after every deployment operation

Question 3

What does the selective deployment feature in Fabric deployment pipelines allow you to do?

Accepted Answer

Deploy only specific items from a stage rather than deploying all items at once

Answer

Deploy only items that have changed since the last pipeline deployment

Answer

Deploy items filtered by a custom classification tag or label

Answer

Deploy items owned by a specific user or service principal

Question 4

How can Fabric deployment pipeline deployments be incorporated into an Azure DevOps CI/CD release pipeline?

Accepted Answer

By calling the Fabric REST API deploy endpoint from a script task in the Azure DevOps pipeline

Answer

By using a Fabric-native task available in the Azure DevOps marketplace

Answer

By using Azure Logic Apps triggered by Azure DevOps completion webhooks

Answer

By installing a Fabric CLI tool on the Azure DevOps build agent

Question 5

What is the primary advantage of combining Git integration with deployment pipelines in a Fabric CI/CD strategy?

Accepted Answer

Git provides version history and branching for collaboration while pipelines handle stage promotion with environment-specific configuration rules

Answer

Git integration is a prerequisite that must be configured before deployment pipelines can function

Answer

Git replaces the need for deployment rules by storing per-environment configurations in branches

Answer

Git integration automatically triggers pipeline deployments whenever changes are committed to the main branch

Question 6

Which type of configuration override is supported by deployment rules in Fabric deployment pipelines for semantic models?

Accepted Answer

Data source connection parameter overrides (e.g., server name, database)

Answer

DAX measure default value overrides per environment

Answer

Report visual theme and color scheme overrides

Answer

Row-level security role membership overrides

Question 7

What is the recommended Git branching strategy for teams using Fabric workspace Git integration?

Accepted Answer

Feature branches per developer that merge to a main branch connected to the development workspace

Answer

All developers commit directly to the main branch connected to the production workspace

Answer

Each pipeline stage must connect to the same shared Git branch simultaneously

Answer

Each Fabric workspace must use its own dedicated Git repository with no sharing