easyMultiple Choice
FC0-U71 Practice Question: A user needs to store customer information…
A user needs to store customer information including name, address, and order history. Which database type is most appropriate?
⚠ Common exam trap
Watch out — candidates often choose NoSQL databases (Option C) because they assume 'order history' implies large-scale or flexible data, but the question specifies structured customer information with clear relationships, making relational databases the correct fit for ACID-compliant transactional integrity.
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
✓
Relational database
A relational database is the most appropriate choice because it organizes data into tables with rows and columns, allowing efficient storage and retrieval of structured customer information (name, address) while supporting relationships to order history via foreign keys. This structure enables ACID compliance and complex queries using SQL, which is ideal for transactional data with clear schema requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hierarchical database
Why it's wrong here
Hierarchical databases model data as a strict parent-child tree, so a customer's multiple orders and shared address attributes cannot be represented without duplicating records across branches. They suit fixed one-to-many structures like file systems or bill-of-materials, not the relational links this scenario requires.
- ✗
Flat-file database
Why it's wrong here
A flat-file database holds one table with no relational links, so order history cannot reference customers without repeating name and address on every row, causing update anomalies. Flat files suit single-entity lists such as a standalone contact or inventory export, not linked customer and order records.
- ✗
NoSQL database
Why it's wrong here
NoSQL databases sacrifice fixed schemas and multi-table joins, so enforcing consistent customer-to-order relationships and ad-hoc queries across name, address and history is awkward. They suit high-volume, denormalised or rapidly changing data such as logs or catalogues, not structured relational customer records.
- ✓
Relational database
Why this is correct
Customer name, address and order history form structured, related entities with defined fields and relationships. A relational database enforces schemas and joins across customer and order tables, preserving referential integrity and supporting the querying this scenario requires.
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.