The correct answer is Key-value pairs.

Table services are designed to store simple, schema-less entities that are accessed by a primary key and often a partition key. This maps directly to a collection of Key-value pairs where each entity is a set of properties associated with a unique key. That is why Key-value pairs is the correct choice for the Contoso Table service.

Relational data is incorrect because relational databases rely on fixed schemas, normalized tables, and joins or complex transactions. Table services do not provide the same relational features or query semantics as a relational database.

Unstructured data is incorrect because raw files, images, and blobs are typically stored in object or blob storage rather than in a table service. Table services are intended for structured or semi structured records tied to keys rather than arbitrary unstructured content.

Wide-column data is incorrect because wide-column stores use a different model with rows that can contain many dynamic columns and are optimized for different access patterns. While some table offerings share similarities with wide-column systems, the simplest and most accurate description of Contoso Table service is as a Key-value pairs store.

Full AWS Practitioner Certification Question