FC0-U71 Data and Database Fundamentals Practice Question
Which of the following is a primary advantage of using a database over a flat file system for storing customer records?
⚠ Common exam trap
FC0-U71 often tests the trade-off between simplicity and capability — candidates pick 'simpler to set up' or 'no query language' as advantages when those are actually characteristics of flat files, not databases.
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
✓
Supports simultaneous multi-user access
A database management system supports concurrent multi-user access through locking, transactions, and isolation levels, allowing many users to read and write customer records simultaneously without corrupting data. A flat file system offers no such concurrency control, so simultaneous writes can overwrite each other.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Simpler to set up and manage
Why it's wrong here
While flat file systems can be set up with minimal overhead, they lack the relational integrity and concurrent-access controls that a database management system provides. This option is tempting because for a small, single-user list of records, a flat file is indeed quick to configure. However, in a scenario requiring simultaneous multi-user updates and enforced data consistency across customer records, the absence of transaction management and referential constraints makes a flat file system unsuitable.
- ✓
Supports simultaneous multi-user access
Why this is correct
A database management system provides concurrency control, letting many users read and write customer records simultaneously without corrupting data. A flat file offers no such locking or transaction mechanism, so concurrent edits overwrite each other, making the database the appropriate choice.
- ✗
Stores data in a non-structured format
Why it's wrong here
Storing records without a fixed schema prevents the enforcement of column types, primary keys and referential integrity across customer tables, so duplicate and orphaned records cannot be blocked. Non-structured storage suits media files, logs or documents where fields vary per item — not relational customer records requiring consistent querying.
- ✗
No need for a query language
Why it's wrong here
Databases still require SQL or another query language, so this is not an advantage they hold over flat files. Avoiding a query language describes fixed-format interchange such as CSV consumed directly by scripts, not relational storage of customer records.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
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.