Where should reviewed deployment changes go before production?
Why D is the answer
A CI/CD pipeline with tests
Reviewed changes should go through a CI/CD pipeline with tests before production.
In detail
- A CI/CD pipeline tests each change.
- Infrastructure changes need tests too.
Use case
An illustrative scenario, not a real incident.
Reviewed changes pass through a CI/CD pipeline with tests before production.
See it in different ways
flowchart LR
A["Deploy to a canary"] --> B{"Metrics healthy?"}
B -->|Yes| C["Roll out further"]
B -->|No| D["Roll back"]sequenceDiagram participant D as Developer participant P as CI/CD pipeline participant C as Canary participant U as All users D->>P: Reviewed change P->>C: Small share of traffic C-->>P: Alerts on user-facing symptoms P->>U: Complete the rollout, or roll back
flowchart LR S0["Review"] --> S1["CI/CD tests"] --> S2["Deploy"]
Key point: Changes pass through tested pipelines.
Why the other options are wrong
- A. Straight to production by hand
- That is untested.
- B. A manual change in the console
- That is untested.
- C. A shared drive
- A drive does not deploy.