You need to promote a Fabric solution from dev to test to prod in a controlled way. What should you use?
Why C is the answer
Deployment pipelines
Deployment pipelines exist for moving content between stages, and they pair with version control for lifecycle management.
In detail
- Deployment pipelines promote content through stages.
- Compare stages before you deploy, to see what will change.
Use case
An illustrative scenario, not a real incident.
A team tested a change in dev and wants it live with no manual rebuild. A deployment pipeline moves the items to test, then prod.
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
flowchart LR S0["Dev"] --> S1["Compare"] --> S2["Test"] --> S3["Compare"] --> S4["Prod"]
Key point: Deployment pipelines promote content in stages.
Why the other options are wrong
- A. A shortcut to the dev workspace
- A shortcut only reads data, and does not promote it.
- B. Exporting items by hand
- Exporting by hand is error prone.
- D. Email approvals
- An approval email does not move content.