A dev database connection must point to prod after promotion. What do you use?
Why A is the answer
Deployment rules
Deployment rules set stage-specific values, such as a data source, so promoted content connects to the right database.
In detail
- Deployment rules change values for each stage.
- Rules let the same content work in each stage.
Use case
An illustrative scenario, not a real incident.
A pipeline deploys a dataset that still points at the dev database. A deployment rule swaps the connection to prod in that stage.
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(("Deployed item"))
n1["Dev stage"]
n2["Dev database"]
n3["Prod stage"]
n4["Prod database"]Key point: Deployment rules change settings per stage.
Why the other options are wrong
- B. A sensitivity label
- A label classifies data.
- C. A KQL function
- A KQL function queries data.
- D. A manual edit in production after each release
- Manual edits are easy to get wrong.