Where is erasure coding applied in ECS?

Question

Options

• ATo the system index only
• BTo the metadata chunks only
• CTo chunks containing object data only
• DTo the data tables only

• B
  2% (1)
• C
  93% (39)
• D
  5% (2)

Explanation

Erasure coding in ECS (EMC Elastic Cloud Storage) is applied specifically to chunks containing object data because that is where the bulk of storage capacity is consumed, and erasure coding provides space-efficient redundancy compared to full replication - making it ideal for large data payloads. Option A is wrong because the system index uses replication, not erasure coding, to ensure fast and consistent access to structural data. Option B is incorrect because metadata chunks are also protected via replication, which prioritizes low-latency access over storage efficiency. Option D ("data tables") is not an accurate term for how ECS organizes object data and conflates ECS architecture with relational storage concepts.

Memory tip: Think "big data, big savings" - erasure coding is applied where data volume lives (object data chunks), not where speed or structure matters (indexes and metadata, which use replication).

No community discussion yet for this question.