AZ400-Q: avoid rebuilding different release bits
A release pipeline currently rebuilds the application separately for test and production. The team cannot prove both environments used identical bits. What should it do?
- A) Add a timestamp to each build.
- B) Let each environment build from the latest branch state.
- C) Build once, publish an immutable artifact with provenance, and promote that same artifact through environments. ✓
- D) Copy compiled files through chat.
Answer: C. Build-once/promote-many preserves artifact identity and makes environment differences traceable.
Why not the others: Timestamps and latest branches do not prove equivalence; chat copying is uncontrolled.