In the relational data model, a ‘‘tuple’’ corresponds to which familiar data structure in file or table terminology?

Introduction / Context:
The relational model uses specific terminology: relation (table), attribute (column), and tuple (row). Understanding these mappings helps learners transition between conceptual theory and practical SQL usage without confusion.

Given Data / Assumptions:

• We compare relational terms to traditional file system terminology.
• A tuple is one instance of data across all attributes in a relation.
• Each tuple represents a single entity occurrence in the table.

Concept / Approach:

In a table, each row collects values for each column, forming a complete entity instance—this is a tuple. In legacy file terms, the analogous unit is a record. Therefore, tuple ≈ row ≈ record; attribute ≈ column ≈ field; relation ≈ table; database ≈ collection of relations and other objects.

Step-by-Step Solution:

Verification / Alternative check:

Any introductory SQL or database theory text aligns tuple with row/record; SQL operations like INSERT add tuples (records) to relations (tables).

Why Other Options Are Wrong:

Field: A single column value, not the entire row.

File/database: Containers above the record level; wrong granularity.

Data item: Vague; usually a single value, not a row.

Common Pitfalls:

Confusing attribute vs. tuple; ensuring the row/column mapping is clear prevents schema design errors.

Final Answer:

record