Immutable cloud infrastructure promotes several benefits. Which of the following is a key characteristic of designing solutions with immutable infrastructure?

Question

Options

• AFrequent in-place updates and patches to servers
• BManual configuration of servers for each deployment
• CAutomated deployment of servers from a base image without modifications
• DHigh reliance on physical servers for critical applications

• A
  4% (1)
• B
  12% (3)
• C
  80% (20)
• D
  4% (1)

Explanation

Immutable infrastructure means servers are never modified after deployment - instead, any change requires replacing the entire server with a freshly built one from a base image, making C correct. This approach eliminates configuration drift, ensures consistency across environments, and makes rollbacks trivial.

• A is wrong because in-place updates are the hallmark of mutable infrastructure - patching running servers is exactly what immutability avoids.
• B is wrong because manual configuration introduces human error and inconsistency, the opposite of what immutable infrastructure solves; deployments should be automated and reproducible.
• D is wrong because immutable infrastructure is a cloud-native software design principle, unrelated to physical vs. virtual hardware.

Memory tip: Think "immutable = immortal image" - you never change the server, you replace it with a clean copy from a golden image, just like stamping coins from a fixed mold.

No community discussion yet for this question.