Question

Your team maintains a Fabric workspace containing a semantic model and several reports. The team wants developers to work in isolated feature branches with pull-request reviews before merging, while release managers separately promote validated content from a Development workspace through Test to a Production workspace without touching source files. Which combination of Fabric lifecycle tools should you configure to meet both requirements?

Accepted Answer

Use Git integration for the Development workspace to enable branching and pull requests, and use a deployment pipeline to promote content from Development through Test to Production.

Answer

Use a deployment pipeline for all environments and rely on its built-in branch creation feature for developer isolation and pull-request reviews.

Answer

Use Git integration on all three workspaces (Development, Test, and Production) and merge branches directly into each workspace instead of using a deployment pipeline.

Answer

Export .pbip files to a Git repository for review, then manually import the reviewed files into the Test and Production workspaces for each release.