In the context of operations automation, why is it important to design solutions that take advantage of immutable cloud infrastructure?

Question

Options

• AIt allows for frequent and manual configuration changes
• BTo ensure that each deployment is unique and not reproducible
• CFor easier rollback and version control of environments
• DTo increase the time required for deploying and managing applications

• A
  5% (2)
• B
  11% (4)
• C
  81% (30)
• D
  3% (1)

Explanation

Immutable cloud infrastructure means environments are never modified after deployment - instead, new versions are deployed fresh and old ones are replaced, making C correct: this pattern inherently supports rollback (just redeploy the previous version) and version control (each environment state is a versioned artifact).

Why the distractors fail:

• A is the opposite of immutable - immutability eliminates manual configuration changes, not enables them.
• B contradicts immutability's core value; the whole point is that deployments are reproducible, not unique.
• D immutability actually reduces deployment time and management overhead through automation and consistency.

Memory tip: Think of immutable infrastructure like Docker images - you never "patch" a running container, you build a new image and swap it in. That swap-and-roll-back capability is exactly what makes option C the answer.

No community discussion yet for this question.