A city transit API pipeline must promote one build through test, staging, and production with approvals between stages. What CodePipeline practice ensures the same artifact moves across those environments?
Select an answer to reveal the explanation.
Short Explanation
One stamped crate rides the whole train—test, staging, then prod—with conductors (approvals) between cars. Rebuilding in every station invents a new crate and ruins the "what we tested is what we ship" promise.
Full Explanation
Orchestrated CI/CD workflows should promote an immutable build artifact across environments rather than recompiling per stage. CodePipeline stages can consume prior-stage artifacts and insert approval actions before production. Rebuilding per environment or deploying arbitrary branch tips breaks traceability between tested and released bits.