It means servers are never modified after they are created. To change anything you build a new image or container, roll out fresh instances, and destroy the old ones instead of patching in place. It matters because it removes configuration drift, makes environments reproducible from source, turns rollback into redeploying the previous artifact, and means a compromised or degraded host is replaced rather than repaired.
Why interviewers ask this
The interviewer wants to see whether you understand the reasoning, not just the slogan. Strong answers connect immutability to drift, to reproducibility, and to fast rollback, then acknowledge where it is awkward, such as stateful systems and long lived data. Being able to name the trade offs, like slower iteration and image build pipelines to maintain, shows you have actually operated this way.
How to structure your answer
- Define it by what you never do: no in place changes.
- List the concrete benefits: no drift, reproducible, easy rollback.
- Describe how a change ships under this model.
- Name where it gets awkward, especially state.
Example answer
It means nothing gets changed after it is built. No sshing in to fix a config, no running a package upgrade on a live box. If something needs to change, the change goes into source, we bake a new image or container, and the fleet gets replaced with instances from that image. The payoff is that the state of production is entirely determined by an artifact and a version, so staging and production genuinely match, and a host that has been running for three months has no accumulated hand edits that nobody remembers. Rollback becomes deploying the previous digest, which takes minutes and has no unknowns. It also helps security: patching means rebuilding from an updated base and rolling, and if a host looks compromised you terminate it rather than trying to clean it. The awkward part is anything that holds state. Databases and stateful sets still need in place upgrades and careful migrations, and the discipline there is separating the data lifecycle from the compute lifecycle so the compute can stay disposable.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you handle patching an urgent CVE under this model?
- How does immutability apply to a stateful database cluster?
- What do you do when you must debug on a live production host?
Related devops engineer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions