FC0-U71 Data and Database Fundamentals Practice Question
A hospital's scheduling system must answer questions such as 'which appointments belong to patient 4471, and which physician is assigned to each?' Records change frequently, and staff need immediate, consistent answers. Which data structure characteristic is most important for this requirement?
⚠ Common exam trap
The trap here is reading 'immediate, consistent answers' as a performance or hardware issue, when the requirement is really about how records are linked.
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
✓
Defined relationships between records held in related tables
The scheduling question is fundamentally relational: an appointment is tied to one patient and one physician. Modeling each entity separately and enforcing the links lets the system follow those connections and return accurate answers while records are being edited. Storage-size and file-format choices do not address the connection requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Defined relationships between records held in related tables
Why this is correct
The questions asked are about how one record connects to others: appointments point to a patient and to a physician. A relational structure stores each entity in its own table and enforces those links, so a query can follow the connections and return consistent results even while records are being updated.
- ✗
Very large binary media objects stored alongside each patient record
Why it's wrong here
Storing scans or images is useful clinically, but it does not by itself let the system reliably link an appointment to a patient and to a physician. The stated need is about relationships between records and about consistency as data changes, which is a structural concern rather than a media-storage concern.
- ✗
A single flat file listing every appointment in arrival order
Why it's wrong here
A flat chronological list can be searched, but it does not model the connections between patients, physicians, and appointments as first-class facts. Repeated patient and physician details would drift, and answering the relational question across many records would depend on fragile text matching rather than enforced links.
- ✗
Compression of every text field to reduce file size
Why it's wrong here
Compression reduces storage footprint and can speed transfers, but it does not create or enforce the link between an appointment, a patient, and a physician. Two compressed tables with no defined relationship would still leave staff unable to answer the scheduling question reliably.
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.