FC0-U71 Data and Database Fundamentals Practice Question
A software developer is building an application that needs to store user profiles with varying attributes, such as some users having multiple phone numbers and others having none. The developer wants a flexible schema that allows different users to have different sets of fields without altering the database structure. Which type of database is best suited for this requirement?
⚠ Common exam trap
The trap here is assuming that a relational database can easily handle varying attributes; while possible with additional tables, it requires complex joins and schema changes, which is not the flexible approach described.
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
✓
NoSQL document database
The requirement is for a flexible schema that allows different users to have different fields without structural changes. NoSQL document databases store data as self-describing documents, so each user profile can have its own set of attributes. This eliminates the need for schema migrations and supports varying numbers of phone numbers or other fields, making it the best fit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
NoSQL document database
Why this is correct
NoSQL document databases store data in flexible, JSON-like documents, allowing each user profile to have different fields without a fixed schema. This is ideal for varying attributes, such as some users having multiple phone numbers while others have none. The developer can easily add or remove fields per document, meeting the requirement for schema flexibility.
- ✗
Hierarchical database
Why it's wrong here
Hierarchical databases organize data in a tree-like structure with parent-child relationships. They require a predefined schema and are not designed for flexible, per-record variations. Adding optional attributes would require modifying the entire hierarchy, making it unsuitable for the dynamic user profiles described in the scenario.
- ✗
Flat file database
Why it's wrong here
A flat file database stores data in a single table, typically with a fixed set of columns. It cannot accommodate varying attributes per user without leaving many empty fields or creating separate files. This approach is inefficient and does not provide the flexible schema needed for diverse user profiles with optional fields.
- ✗
Relational database
Why it's wrong here
Relational databases use a fixed schema with predefined columns and data types. Adding a new attribute, like a second phone number, requires altering the table structure, which is inflexible for varying user profiles. While possible with additional tables, it complicates queries and does not provide the dynamic schema needed for this scenario.
Go deeper
Related to this question
About these practice questions
One of 988 original FC0-U71 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.