FC0-U71 Data and Database Fundamentals Practice Question
Which TWO of the following are key characteristics of a NoSQL database compared to a traditional relational database?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Flexible schema design
Option D (Flexible schema design) is correct because NoSQL databases such as document stores (MongoDB), key-value stores (Redis), and wide-column stores (Cassandra) do not require a fixed, predefined table schema, allowing each record to have different fields and structures. Option E (Horizontal scalability) is correct because NoSQL systems are architecturally designed to scale out by distributing data across many commodity servers via sharding and partitioning, rather than relying on expensive vertical scaling of a single server. In contrast, option A (Strict schema enforcement) describes relational databases, which enforce a rigid schema via DDL constraints, and is not a NoSQL trait. Option B (Uses SQL as the query language) is incorrect because NoSQL databases typically use non-SQL APIs such as JSON queries, key lookups, or CQL, though some offer SQL-like interfaces. Option C (ACID transactions are always guaranteed) is incorrect because many NoSQL databases follow the BASE model and provide only eventual consistency, with ACID guarantees limited to single-document or optional multi-document transactions rather than being always guaranteed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Strict schema enforcement
Why it's wrong here
NoSQL databases typically use flexible, schema-on-read models, so strict schema enforcement describes relational databases instead. It is tempting because some NoSQL products offer optional schema validation, but that is not a defining characteristic distinguishing NoSQL from traditional relational systems.
- ✗
Uses SQL as the query language
Why it's wrong here
SQL is the query language of relational databases; NoSQL stores use varied APIs such as document queries, key-value access or graph traversal. It is tempting because some NoSQL databases offer SQL-like interfaces, but that is an add-on rather than a defining characteristic of the category.
- ✗
ACID transactions are always guaranteed
Why it's wrong here
NoSQL databases often relax ACID guarantees in favour of availability and partition tolerance, offering BASE semantics instead. It is tempting because several modern NoSQL products do support ACID transactions, but universal, always-guaranteed ACID behaviour characterises relational databases, not NoSQL generally.
- ✓
Flexible schema design
Why this is correct
NoSQL stores such as document and key-value databases permit each record to carry its own fields, so schema changes need no migration or ALTER TABLE. This contrasts with the fixed, predefined columns of a relational database, satisfying the flexible schema characteristic.
- ✓
Horizontal scalability
Why this is correct
Horizontal scalability means adding more commodity nodes to distribute load and data, rather than upgrading a single larger server. NoSQL databases are designed for this scale-out partitioning across clusters, unlike traditional relational databases that typically scale vertically.
Go deeper
Related to this question
About these practice questions
Courseiva writes every FC0-U71 question from scratch — 988 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This FC0-U71 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U71 exam.