What does deployment pipelines in Fabric do?
Why B is the answer
It promotes content across Dev, Test and Prod stages
Microsoft says deployment pipelines promote content across stages, with configuration rules and content comparison.
In detail
- Deployment pipelines promote content across Dev, Test and Prod.
- Selective deployment lets you promote part of the content.
Use case
An illustrative scenario, not a real incident.
A release manager opens a pipeline, sees which items differ between stages, and deploys only the ones that are ready.
See it in different ways
flowchart LR A["Workspace"] --> B["Git repository"] A --> C["Dev stage"] C --> D["Test stage"] D --> E["Prod stage"]
sequenceDiagram participant G as Git participant D as Dev participant T as Test participant P as Prod G->>D: Syncs the workspace D->>T: Deployment pipeline T->>P: Deployment pipeline P->>P: Deployment rules set production values
mindmap
root(("Deployment pipeline"))
n1["Stages"]
n2["Dev"]
n3["Test"]
n4["Prod"]
n5["Controls"]
n6["Content comparison"]
n7["Configuration rules"]Key point: Deployment pipelines compare and promote.
Why the other options are wrong
- A. It compacts Delta tables on a schedule
- That is OPTIMIZE.
- C. It streams events from a source into an eventhouse
- That is an eventstream.
- D. It masks sensitive columns from nonprivileged users
- That is dynamic data masking.