Which set of data types is commonly considered valid values in a key-value store?

Which set of data types is commonly considered valid values in a key-value store?

• A. Number, String, True, False, or Null
• B. Date, Time, Sequence
• C. Binary Large Objects Only
• D. Objects and Arrays at top level

Answer: (A)

In a key-value store, the value you store with a key is usually a simple, primitive type that can be represented and transmitted easily. The most common set includes numbers, strings, booleans (true/false), and a null value to indicate absence. This combination covers numeric data, textual data, logical flags, and a clear way to represent “no value,” and it’s widely supported across different implementations. That’s why the option listing Number, String, True, False, or Null is the best fit: it aligns with how key-value stores are typically used—storing straightforward, atomic values that are easy to serialize and retrieve. Other options describe more specialized or complex data types (dates, times, sequences; only binary large objects; or nested objects/arrays), which aren’t universally treated as native value types in the basic key-value model.

In a key-value store, the value you store with a key is usually a simple, primitive type that can be represented and transmitted easily. The most common set includes numbers, strings, booleans (true/false), and a null value to indicate absence. This combination covers numeric data, textual data, logical flags, and a clear way to represent “no value,” and it’s widely supported across different implementations.

That’s why the option listing Number, String, True, False, or Null is the best fit: it aligns with how key-value stores are typically used—storing straightforward, atomic values that are easy to serialize and retrieve. Other options describe more specialized or complex data types (dates, times, sequences; only binary large objects; or nested objects/arrays), which aren’t universally treated as native value types in the basic key-value model.