Adventure Works maintains Dev, Test, and Prod workspaces on the same Fabric capacity. Every change must be reviewed in a pull request before it can reach Test, and promotion between environments must not require re-authoring content. The team wants the smallest number of moving parts. Which approach should you recommend?
- A.
Connect all three workspaces to three long-lived branches and promote content by merging branches, without a deployment pipeline.
- B.
Connect the Prod workspace to the main branch and have developers commit from Prod after each deployment so that the repository always matches production.
- C.
Connect only the Dev workspace to the repository, require pull requests into the main branch, and use a deployment pipeline to promote Dev to Test to Prod.
- D.
Skip Git integration and export each item from Dev, then import it into Test and Prod after the review meeting.
Show answer
Answer: C
Git on the development workspace gives code review through pull requests, and a deployment pipeline promotes the reviewed content forward without rebuilding it in each environment.
- A. Three connected workspaces and branch merges add sync overhead and give up deployment rules and the pipeline comparison view.
- B. Committing from Prod makes production the source of truth, so changes made there are never reviewed before they take effect.
- C. Git on Dev supplies the pull request gate while the pipeline promotes the same reviewed artifacts forward with rules and auto-binding.
- D. Manual export and import has no version history, cannot enforce a pull request, and loses automatic rebinding of dependent items.