easyMultiple Choice
FC0-U71 Practice Question: A database designer wants to avoid duplicate data…
A database designer wants to avoid duplicate data across tables and ensure each table stores information about a single entity. Which process should the designer apply?
⚠ Common exam trap
It's easy for candidates to confuse normalization with indexing, assuming both reduce redundancy, but indexing only optimizes query speed without addressing data duplication or entity isolation.
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
✓
Normalization
Normalization is the process of organizing data in a database to reduce redundancy and dependency by dividing large tables into smaller, related tables and defining relationships between them. This ensures each table stores information about a single entity and avoids duplicate data across tables, aligning with the designer's goal.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Indexing
Why it's wrong here
Indexing creates lookup structures to speed query retrieval; it does not restructure tables or remove redundancy. Normalisation achieves the stated goal by decomposing tables so each stores one entity's attributes. Indexing would be the right choice when read performance on large tables is the concern.
- ✗
Transaction isolation
Why it's wrong here
Transaction isolation controls how concurrent transactions see each other's uncommitted changes, preventing anomalies such as dirty reads; it does not eliminate duplicate data across tables. Normalisation is the process that removes redundancy and enforces single-entity tables. Isolation would be correct when concurrent access anomalies must be prevented.
- ✓
Normalization
Why this is correct
Normalization organises tables so each stores data about one entity and attributes depend only on that table's key, eliminating duplicate data through decomposition. This directly satisfies the goal of avoiding redundancy and enforcing single-entity tables.
- ✗
Backup and recovery
Why it's wrong here
Backup and recovery preserves and restores data after loss or corruption; it neither removes redundancy nor enforces one entity per table. Normalisation is the design process that achieves both. Backup and recovery would be the correct choice when the requirement is resilience against data loss or disaster.
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 →
Same concept, more angles
1 more way this is tested on FC0-U71
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A database designer wants to reduce data redundancy and avoid update anomalies. Which process should be applied?
medium- A.Denormalization
- ✓ B.Normalization
- C.Encryption
- D.Indexing
Why B: Normalization is the process of organizing database tables to minimize redundancy and eliminate update, insert, and delete anomalies by decomposing tables according to normal forms (1NF, 2NF, 3NF, BCNF). It systematically removes partial and transitive dependencies so that each fact is stored in exactly one place. This directly addresses the designer's goal of reducing redundancy and avoiding update anomalies.
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.