Question

A data engineering team manages a Fabric workspace containing lakehouses, notebooks, and semantic models. They want to enforce peer review of every code change through pull requests before changes are merged, while also promoting validated content across Development, Test, and Production workspaces without manually rebuilding items. Which combination of lifecycle management features should they configure to satisfy BOTH requirements?

Accepted Answer

Use Git integration with a feature-branch workflow for pull-request review, and use deployment pipelines to promote items across the three workspace stages.

Answer

Use deployment pipelines alone, relying on stage comparison and deployment rules to handle code review and promotion.

Answer

Use Git integration alone, committing directly to the main branch and syncing each workspace to a different branch for promotion.

Answer

Export items as database projects, review the SQL in a repository, and manually import them into each workspace stage.