Database Design Quiz Week 4

A single attribute marked with a #.

A combination of attributes and relationships.

A derived attribute like totalSales.

A subtype entity.

A relationship is missing between two entities.

Three entities have unresolved many-to-many relationships.

A subtype is nested beyond three levels.

Historical data is stored redundantly.

A supertype-subtype hierarchy.

An entity linked to itself (e.g., employee-manager).

A mandatory arc between two entities.

A weak entity dependency.

Must always be a surrogate key.

Depends on the UID of its parent entity.

Cannot include attributes from the parent.

Is optional.

Delete redundant attributes.

Add a direct relationship between two entities.

Use nested subtypes.

Convert a composite UID to a simple UID.

Redundant attributes in the original entity.

A new entity linked to the original entity.

A derived attribute.

A recursive relationship.

Create separate entities for each role.

Use a supertype (e.g., PERSON) with subtypes.

Add optional attributes to a single entity.

Use arcs to represent exclusivity.

The UID is still valid.

The UID becomes non-unique.

The entity instance is deleted.

A surrogate key is automatically generated.

A recursive relationship.

Mutually exclusive relationships.

A weak entity dependency.

A hierarchical structure.

Adding a supertype.

Introducing an intersection entity.

Using a composite UID.

Deleting redundant relationships.