For an application that requires both high availability and durability of data, which ECS storage abstraction should be utilized?

Question

Options

• ATransient storage for ephemeral data
• BObject storage with versioning and lifecycle policies
• CBlock storage attached to a single instance
• DFile storage without replication

• A
  4% (1)
• B
  85% (23)
• C
  7% (2)
• D
  4% (1)

Explanation

Object storage with versioning and lifecycle policies (B) delivers both high availability and durability because it stores data redundantly across multiple nodes or zones, supports automatic versioning to recover from accidental deletions or corruption, and uses lifecycle policies to manage data retention - making it purpose-built for resilient, long-lived data workloads.

Why the distractors fail:

• A (Transient storage): By definition ephemeral - data is lost when the container stops, which is the opposite of durable.
• C (Block storage attached to a single instance): Single-instance attachment creates a single point of failure; if that instance goes down, data becomes inaccessible, violating high availability.
• D (File storage without replication): No replication means no redundancy - a single failure can cause permanent data loss, sacrificing both durability and availability.

Memory tip: Think "VOL = Versioning + Object + Lifecycle = Vault of Longevity." Object storage's versioning acts like a vault that keeps every copy of your data safe, while lifecycle policies keep it organized - exactly what high availability + durability demands.

No community discussion yet for this question.