ER-to-Relational Mapping — Regular (Strong) Entity When mapping a regular (strong) entity type from an entity–relationship model into the relational model, which statement correctly describes how many relations (tables) are created for that single entity?

Introduction:
Converting an entity–relationship (ER) design into a relational schema is a foundational database skill. A common question is how many relations (tables) result from mapping a single regular, also called strong, entity. Understanding this baseline helps you reason about more complex cases such as weak entities, multivalued attributes, and associative entities.

Given Data / Assumptions:

• The source construct is a regular (strong) entity with a single primary key attribute or a composite key.
• Attributes are atomic and already satisfy first normal form.
• No multivalued attributes or repeating groups are present for this specific mapping step.

Concept / Approach:
The standard rule is straightforward: one regular entity becomes one base relation. All simple attributes of the entity become columns of that relation. The entity’s identifier becomes the relation’s primary key. Only if additional modeling features exist (for example, multivalued attributes) would extra relations be introduced, but those are separate steps, not part of the core strong-entity mapping.

Step-by-Step Solution:
Create a relation named after the entity (or a clear, singularized name).Place every simple attribute as a column in that relation.Designate the entity identifier as the primary key of the relation.Do not create extra relations unless you encounter multivalued attributes, weak entities, or relationships requiring separate tables.

Verification / Alternative check:
Check any introductory database textbook procedure: strong entity to single relation is the canonical first mapping step. Any departure implies the presence of special attributes or relationships that trigger additional rules.

Why Other Options Are Wrong:

• Two, three, or four relations imply extra constructs (multivalued attributes, associative entities) not stated here.
• A view is not the standard product of ER-to-relational mapping for base data; a base relation is.

Common Pitfalls:
Accidentally creating additional tables for simple attributes or failing to declare the appropriate primary key after mapping.

Final Answer:
One relation is created.