Question 338 of 512
Database FundamentalshardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is many-to-many because the scenario describes a bidirectional relationship where each book can have multiple authors and each author can write multiple books, which cannot be modeled with simple one-to-many foreign keys without causing data duplication. In relational database design, a many-to-many relationship is implemented using a junction table—also called an associative or linking table—that contains foreign keys referencing the primary keys of both the Book and Author entities, allowing the database to efficiently store all pairings without redundancy. On the CompTIA ITF+ FC0-U61 exam, this concept tests your understanding of entity relationship modeling and normalization; a common trap is confusing many-to-many with one-to-many, but remember that if both sides can have multiple instances, it’s many-to-many. A helpful memory tip is to think of a library: one book can have several authors, and one author can write several books—that’s the classic many-to-many pattern.

FC0-U61 Database Fundamentals Practice Question

This FC0-U61 practice question tests your understanding of database fundamentals. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A database designer is modeling a system where each book can have multiple authors and each author can write multiple books. Which type of relationship should be used between the Book and Author entities?

Question 1hardmultiple choice
Full question →

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

The scenario describes a many-to-many relationship because each book can have multiple authors and each author can write multiple books. In relational database design, this is modeled using a junction (or associative) table that contains foreign keys referencing both the Book and Author primary keys, enabling the bidirectional association without data redundancy.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • One-to-one

    Why it's wrong here

    One-to-one would force each book to have only one author and each author only one book.

  • Hierarchical

    Why it's wrong here

    Hierarchical is a model used in older systems, not a standard relationship in relational databases.

  • One-to-many

    Why it's wrong here

    One-to-many would allow one author to many books, but not many authors for one book without repeating author data in the book table.

  • Many-to-many

    Why this is correct

    Many-to-many allows a book to have multiple authors and an author to have multiple books, typically implemented via a junction table.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse a one-to-many relationship with many-to-many, mistakenly thinking that adding multiple author fields to the Book table (violating first normal form) is acceptable, rather than recognizing the need for a junction table.

Detailed technical explanation

How to think about this question

In relational database theory, a many-to-many relationship is implemented by creating a third table (often called a junction table) that contains composite primary keys or foreign key columns referencing both related entities. For example, a BookAuthor table with (BookID, AuthorID) as a composite primary key ensures each combination is unique and supports efficient joins. This design avoids data anomalies and adheres to normalization principles, specifically eliminating repeating groups and partial dependencies.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related FC0-U61 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free FC0-U61 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this FC0-U61 question test?

Database Fundamentals — This question tests Database Fundamentals — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Many-to-many — The scenario describes a many-to-many relationship because each book can have multiple authors and each author can write multiple books. In relational database design, this is modeled using a junction (or associative) table that contains foreign keys referencing both the Book and Author primary keys, enabling the bidirectional association without data redundancy.

What should I do if I get this FC0-U61 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This FC0-U61 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-U61 exam.