Which scenario best matches choosing a relational database?

• A. When you need globally distributed eventual consistency
• B. When you require schema-less storage for irregular data
• C. When data is highly structured and strong transaction integrity is needed
• D. When schema must be completely flexible and scalable without joins

Answer: (C)

Relational databases excel when data is highly structured and you require strong transactional integrity. They rely on a fixed schema, defined data types, and constraints that enforce accuracy and consistency. With ACID transactions, operations across multiple tables stay all-or-nothing, and the system preserves data integrity even in complex, multi-step processes. The ability to model relations with primary and foreign keys and to perform powerful joins lets you query and combine related data efficiently, which is essential for areas like financial records, inventory, or any domain where precision and reliability across updates are crucial.

Other approaches are better suited to different needs. Globally distributed systems that emphasize eventual consistency trade immediate consistency for availability and partition tolerance. Schema-less storage fits irregular or highly evolving data where a fixed schema would be too rigid. Fully flexible schemas with no joins describe non-relational stores designed for scalability and flexible data models, often at the cost of complex relational queries and strict transactions.