easyMultiple Select
FC0-U71 Practice Question: Which TWO of the following are advantages of…
Which TWO of the following are advantages of using a relational database over a NoSQL database? (Choose two.)
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
✓
ACID compliance
Relational databases are designed around ACID transactions—atomicity, consistency, isolation, and durability—which guarantee reliable, predictable behavior for multi-row operations, something most NoSQL databases only partially support. Option D (Standard query language (SQL)) is correct because relational databases use SQL, a standardized, widely known language that provides portable, declarative querying and broad tool/ecosystem support across vendors. Option A (Schema flexibility) is not an advantage of relational databases; it is a hallmark of NoSQL systems like document or key-value stores, since relational databases enforce a predefined schema. Option B (Low latency for large volumes) is not a general relational advantage; NoSQL databases are often chosen specifically for high-throughput, low-latency access to massive datasets. Option E (Horizontal scalability) is also typically a NoSQL strength, since relational databases traditionally scale vertically and require sharding or clustering add-ons to scale horizontally.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Schema flexibility
Why it's wrong here
Schema flexibility belongs to NoSQL document and key-value stores, which accept heterogeneous records without migrations; relational engines enforce a fixed schema with typed columns and constraints. It tempts because flexible schemas speed early development, but that is precisely the NoSQL advantage the question contrasts against.
- ✗
Low latency for large volumes
Why it's wrong here
Relational engines serve low latency through indexed B-tree lookups on structured rows, not across the massive, sparse volumes NoSQL targets. It tempts because tuned relational queries are fast, yet the stem contrasts advantages over NoSQL, where high-volume throughput is the NoSQL design goal.
- ✓
ACID compliance
Why this is correct
ACID compliance guarantees that transactions complete fully or not at all, preserving consistency across concurrent operations. Relational engines enforce this natively, giving the stem's requested advantage over most NoSQL databases, which typically relax such guarantees for scale.
- ✓
Standard query language (SQL)
Why this is correct
SQL provides a standardised, declarative query language across relational products, so skills and queries transfer between systems. This portability is the advantage the stem asks for over NoSQL databases, which each expose their own query APIs.
- ✗
Horizontal scalability
Why it's wrong here
Relational databases scale vertically, so horizontal sharding must be added manually; NoSQL engines distribute partitions across nodes natively. It tempts because horizontal scaling is a genuine strength of distributed systems, but the question asks what relational engines offer over NoSQL, where this axis favours NoSQL.
Go deeper
Related to this question
About these practice questions
This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.