What is the purpose of the Key-Value data model?

• A. A storage model that uses key-value pairs for flexible data
• B. A serialized JSON blob stored in a single field
• C. Consolidates related information and provides more consistency
• D. Imposes strict schemas with fixed columns

Answer: (C)

Key-Value stores are built around mapping a single, unique key to a value that represents a cohesive unit of data. The main idea is to consolidate related information behind one key so you can retrieve or update that entire piece of data in one go, which helps keep the data consistent and easy to manage. This setup means you’re not juggling multiple scattered fields or tables; instead, you access a single value that encapsulates the related attributes, making operations straightforward and reducing the chances of mismatches across separate pieces of data.

While flexibility exists in what can be stored inside the value (it can be a simple primitive or a richer structure), the essence is the consolidation of related information under one key to promote consistency and simple access. The other descriptions describe different aspects or drawbacks—such as storing a blob of JSON or enforcing a rigid schema—neither captures this consolidating, cohesive access as clearly.