Data organization terminology: In database concepts, what is the term for a group of related fields describing one entity instance (for example, all columns about one customer)?

Introduction / Context:
Understanding the hierarchy of data organization is foundational in information systems: characters → fields → records → files/tables → databases. Correct terms help analysts, developers, and users communicate precisely about structures and operations like indexing, querying, and normalization.

Given Data / Assumptions:

• A field is one attribute (e.g., last_name, price).
• A record is a set of fields about one entity instance.
• A file (or table) is a collection of homogeneous records.

Concept / Approach:
A record aggregates related fields that jointly describe a single real-world entity or transaction. In relational terminology, a record corresponds to a row (and a field corresponds to a column). The schema defines structure and constraints across the whole table/database, not an individual instance. A tuple is the formal relational term for a row, conceptually equivalent to a record, but in general IS usage “record” is the most accessible and accurate term here.

Step-by-Step Solution:

Verification / Alternative check:
Any CREATE TABLE statement implies records (rows) composed of fields (columns), confirming the record as the aggregation level for related attributes.

Why Other Options Are Wrong:

• Tuple: A correct synonym in relational theory, but the common IS term expected in such questions is “record.”
• Schema: Describes structure and rules, not a single instance group of fields.
• File: Container of many records, not the record itself.
• None: Incorrect because “record” precisely fits.

Common Pitfalls:
Confusing schema-level definitions with instance-level data; using “file” when “record” is intended.

Final Answer:
record