What best describes environment promotion in deployment workflows?

What best describes environment promotion in deployment workflows?

• A. Moving artifacts from dev to test to prod environments along a controlled path.
• B. Deploying all environments in parallel.
• C. Releasing features directly to production without testing.
• D. Using manual handoffs between teams.

Answer: (A)

Environment promotion means moving a built artifact through a sequence of environments in a controlled, repeatable pipeline, with validations and gates at each step before it proceeds. This approach ensures that the same artifact is tested and validated in progressively closer production-like environments, reducing risk of drift and increasing traceability. The best description is the gradual, controlled progression from development to testing to production. It captures the idea of gates and checks at each stage, so only artifacts that meet criteria advance. Deploying all environments in parallel bypasses the staged validation that promotion relies on, and releasing directly to production without testing ignores essential quality gates. Relying on manual handoffs between teams emphasizes process handoffs rather than the automated, auditable progression of artifacts through environments.

Environment promotion means moving a built artifact through a sequence of environments in a controlled, repeatable pipeline, with validations and gates at each step before it proceeds. This approach ensures that the same artifact is tested and validated in progressively closer production-like environments, reducing risk of drift and increasing traceability.

The best description is the gradual, controlled progression from development to testing to production. It captures the idea of gates and checks at each stage, so only artifacts that meet criteria advance.

Deploying all environments in parallel bypasses the staged validation that promotion relies on, and releasing directly to production without testing ignores essential quality gates. Relying on manual handoffs between teams emphasizes process handoffs rather than the automated, auditable progression of artifacts through environments.