FC0-U71 Data and Database Fundamentals Practice Question
A developer modifies a database and wants to ensure that every value in a column meets a specific condition, such as age must be between 0 and 120. Which type of integrity constraint should be used?
⚠ Common exam trap
The trap is confusing domain integrity with user-defined integrity — candidates may think any custom business rule is 'user-defined,' but the exam expects simple value-range or format constraints on a single column to be classified as domain 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
✓
Domain integrity
Domain integrity ensures that values in a column fall within a defined valid range or set of values, such as age between 0 and 120. It is enforced through CHECK constraints, data type definitions, and default values that restrict the domain of acceptable values for an attribute. The scenario explicitly describes a condition on column values, which is the definition of domain integrity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Referential integrity
Why it's wrong here
Referential integrity keeps foreign key values matching existing primary keys in a related table; it cannot restrict a column's numeric range. It would be correct when preventing orphaned child rows, whereas age between 0 and 120 is a domain constraint.
- ✓
Domain integrity
Why this is correct
Domain integrity constrains a column's permitted values to a defined set, range or format, such as age between 0 and 120. It operates on the values themselves, unlike entity, referential or key constraints, which govern rows or relationships between tables.
- ✗
User-defined integrity
Why it's wrong here
User-defined integrity enforces bespoke business rules across rows or tables, not a single column's permitted value range. It would be correct for cross-field rules like salary caps by grade; a column range such as age 0–120 is a domain constraint.
- ✗
Entity integrity
Why it's wrong here
Entity integrity guarantees each row has a unique, non-null primary key; it says nothing about a column's permitted value range. It would be correct when preventing duplicate or null identifier rows, whereas age between 0 and 120 is a domain constraint.
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.