FC0-U71 Data and Database Fundamentals Practice Question
A logistics analyst needs to record which driver delivered each shipment. A driver can deliver many shipments, and each shipment is delivered by exactly one driver. Which relationship type exists between drivers and shipments?
⚠ Common exam trap
The trap here is reaching for a junction table whenever two entities are involved, when a linking table is needed only for many-to-many relationships.
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
✓
One-to-many
The business rule is asymmetric: one driver appears against many shipment rows, but each shipment row names only one driver. That is a one-to-many relationship, and it is normally implemented by storing the driver's key value in the shipment table rather than by creating a separate linking table.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Zero-to-one
Why it's wrong here
Zero-to-one describes optional existence, such as an employee who may or may not have a company laptop assigned. It says nothing about one driver covering many shipments. The scenario describes cardinality between two entity sets, not the optionality of a single attribute, so this choice does not fit.
- ✗
One-to-one
Why it's wrong here
A one-to-one relationship would mean each driver is tied to a single shipment and each shipment to a single driver. That contradicts the stated rule that a driver delivers many shipments, so it cannot describe this situation and would wrongly force a new driver record for every delivery.
- ✓
One-to-many
Why this is correct
One driver appears on many shipment records, while each shipment record names only one driver. That is the definition of a one-to-many relationship, and it is implemented by placing the driver identifier in the shipment table as a foreign key referencing the driver's primary key.
- ✗
Many-to-many
Why it's wrong here
Many-to-many would allow a shipment to be delivered by several drivers simultaneously. The scenario states each shipment has exactly one driver, so the shipment side is singular. A many-to-many model would also require an extra linking table that this business rule does not need.
Quick reference
Symmetric Encryption Algorithm Comparison
| Algorithm | Key Size | Block Size | Status | Notes |
|---|---|---|---|---|
| AES-128 | 128-bit | 128-bit | Current standard | NIST approved; WPA3, TLS |
| AES-256 | 256-bit | 128-bit | Current standard | Preferred for sensitive / govt data |
| 3DES | 112-bit effective | 64-bit | Deprecated (2023) | Replaced by AES |
| DES | 56-bit | 64-bit | Broken | Cracked in < 24 h; never deploy |
| ChaCha20 | 256-bit | Stream cipher | Current | TLS 1.3, WireGuard |
About these practice questions
Courseiva writes every FC0-U71 question from scratch — 988 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.