Rationale for Correct Answer: With immutable infrastructure, you don’t modify running servers/resources in place; you replace them with new versions built from a known image/artifact. This reduces configuration drift and “snowflake” issues, making deployments and rollbacks more predictable—often resulting in less operational complexity compared with troubleshooting in-place changes.
B: Not the best answer—upgrades can be fast in some setups, but “quicker” is not guaranteed; replacing infrastructure may take time depending on provisioning and rollout strategy.
C: Incorrect—immutability doesn’t inherently mean upgrades are “automatic”; automation is a separate practice/tooling choice.
Key Concept: Immutable vs mutable infrastructure; replace instead of modify to reduce drift and simplify operations.