FC0-U71 Data and Database Fundamentals Practice Question
In a relational database, which type of relationship is typically implemented by creating a third table (junction table) that contains foreign keys from both related tables?
⚠ Common exam trap
It's easy for candidates to confuse many-to-many with one-to-many: candidates often think a third table is needed for one-to-many, but it is only required for many-to-many. FC0-U71 often tests the implementation differences between relationship types.
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
✓
Many-to-many
A many-to-many relationship occurs when multiple records in one table relate to multiple records in another. Relational databases cannot directly implement this with a single foreign key, so a junction table (also called an associative or bridge table) is created. This third table contains foreign keys referencing the primary keys of both related tables, and each row represents a unique association between the two entities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Many-to-many
Why this is correct
A many-to-many relationship cannot be stored in two tables, so a junction table holds foreign keys referencing both related tables, with each row representing one association. This resolves the cardinality that one-to-many and one-to-one schemas cannot represent directly.
- ✗
Self-referencing
Why it's wrong here
Self-referencing relationships link rows within one table using a foreign key to the same table's primary key, so no third table is created. It is tempting because it also uses foreign keys, but the scenario's requirement for a junction table containing keys from two related tables indicates many-to-many.
- ✗
One-to-one
Why it's wrong here
One-to-one is implemented by adding a unique foreign key to one of the two tables, or by sharing the primary key; no junction table is needed. It is tempting because both tables are directly linked, but many-to-many is the relationship requiring a third table with foreign keys from both.
- ✗
One-to-many
Why it's wrong here
One-to-many is implemented by placing a foreign key in the child table pointing to the parent, requiring no junction table. It is tempting because junction tables do contain foreign keys, but many-to-many is the relationship that actually demands a third table holding keys from both sides.
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.