How should pipeline changes reach production?
Why A is the answer
Through CI/CD
Using CI/CD means that pipeline changes are tested before they reach production.
In detail
- CI/CD tests changes, and makes them repeatable.
- Test with sample data.
Use case
An illustrative scenario, not a real incident.
A pipeline change passes tests in CI/CD before reaching production, so nobody edits it by hand.
See it in different ways
sequenceDiagram participant C as Managed Service for Apache Airflow participant J as Dataproc job participant L as Cloud Logging participant O as Operator C->>J: Start the step J--xC: Fails C->>J: Retry J->>L: Logs C-->>O: Alert if retries run out
flowchart LR S0["Commit"] --> S1["Test"] --> S2["Deploy"]
Key point: CI/CD moves pipeline changes safely.
Why the other options are wrong
- B. By editing live jobs by hand
- Hand edits are untested.
- C. By editing the running job in the console
- Console edits are untested.
- D. By copying files in the console
- Copying files is untested.