How do you promote a build through environments, and why does staging need to match production?

Question

Accepted Answer

Promotion means taking one immutable artifact and moving it through dev, then staging, then production, gaining confidence at each step, and critically not rebuilding along the way. The same image digest that passed dev is the one that reaches prod, so what runs in production is exactly what passed every earlier gate. Each environment adds validation matched to its cost. Dev runs the fast cheap checks, unit tests in under 5 minutes so developers can iterate, while staging runs the fuller integration suite, a load test at something like 2 times expected peak, and any manual acceptance testing before the production gate. Staging has to match production because the whole value of a pre-prod environment is predictive. Passing there only means something if staging is close enough to prod that success predicts success. If staging holds 10,000 rows and prod holds 50 million, or the topology differs, or a dependency is stubbed, a green run tells you almost nothing, and you get the classic surprise where everything passed in staging and then a query that took 20 milliseconds on the small dataset took 8 seconds in prod. So I push for parity: the same architecture and topology, a representative data shape, the same configuration approach, with only environment specific values differing, endpoints, secrets, instance sizes. Those differences come from injected configuration, never a different build, so the artifact stays identical and the test stays honest.

Answer

What happens when staging diverges significantly from production?

Tests passing in staging stop predicting prod behavior, you get works-in-staging-breaks-in-prod surprises. The pre-prod environment loses its value; parity (topology, data shape, config approach) is what makes staging meaningful.

Answer

What should differ between environments, and what should not?

Only configuration (endpoints, secrets, sizes) should differ, injected at deploy time. The artifact must stay identical across environments so the thing you tested is the thing you ship.

How do you promote a build through environments, and why does staging need to match production?

How do you promote a build through environments, and why does staging need to match production?

The follow-ups they ask next

What the interviewer is listening for

What sinks the answer

If you genuinely do not know

Keep going with deployment

Knowing the answer is not the same as recalling it under pressure