Network database model: Which statement correctly describes a key property of the CODASYL network data structure?

Introduction / Context:
Early database models included hierarchical and network (CODASYL) structures before the rise of relational systems. This question checks understanding of the core capability that distinguished the network model.

Given Data / Assumptions:

• Network databases represent data via sets (owner–member relationships).
• Navigation proceeds by following pointers between records.
• Many-to-many relationships are naturally modeled via multiple sets.

Concept / Approach:
The network model supports flexible connections among record types, enabling many-to-many associations by joining through intersection sets or by multiple membership. This is a logical model with explicit navigational access, not merely a physical byte layout.

Step-by-Step Solution:

Verification / Alternative check:
Compared with hierarchical models (one-to-many), network structures better represent peer-to-peer linkages without excessive duplication.

Why Other Options Are Wrong:

• Conceptually simple: network navigation can be complex for developers.
• Physical representation: confuses logical model with storage details.
• Dominant future: the relational model became the mainstream standard.
• None of the above: incorrect because many-to-many capability is correct.

Common Pitfalls:
Assuming ‘‘network’’ refers to computer networking; here it is a database model type.

Final Answer:
It allows a many-to-many relationship through owner–member sets