Database Design Quiz Week 4

Database Design Quiz Week 4

University

15 Qs

quiz-placeholder

Similar activities

CH 3(2)-Database Design

CH 3(2)-Database Design

University

10 Qs

RDBMS

RDBMS

University

10 Qs

Kunci kekalahan

Kunci kekalahan

University

20 Qs

Database Design & Development Design 1

Database Design & Development Design 1

University

17 Qs

Data modelling

Data modelling

University

10 Qs

Data Model

Data Model

University

10 Qs

GIS Spatial Data Models

GIS Spatial Data Models

University

15 Qs

Linux User Management

Linux User Management

10th Grade - University

20 Qs

Database Design Quiz Week 4

Database Design Quiz Week 4

Assessment

Quiz

Computers

University

Medium

Created by

Atisang Molapo

Used 3+ times

FREE Resource

15 questions

Show all answers

1.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

A composite UID in Barker’s Notation is best defined as:

A single attribute marked with a #.

A combination of attributes and relationships.

A derived attribute like totalSales.

A subtype entity.

2.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

A fan trap occurs in an ERD when:

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.

3.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

A recursive relationship is used to model:

A supertype-subtype hierarchy.

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

A mandatory arc between two entities.

A weak entity dependency.

4.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

In a multi-level UID structure, the UID of a child entity:

Must always be a surrogate key.

Depends on the UID of its parent entity.

Cannot include attributes from the parent.

Is optional.

5.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

To resolve a chasm trap, you must:

Delete redundant attributes.

Add a direct relationship between two entities.

Use nested subtypes.

Convert a composite UID to a simple UID.

6.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

Storing historical data (e.g., price changes) requires:

Redundant attributes in the original entity.

A new entity linked to the original entity.

A derived attribute.

A recursive relationship.

7.

MULTIPLE CHOICE QUESTION

30 sec • 1 pt

When modelling roles (e.g., mechanic/customer), the BEST approach is to:

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.

Create a free account and access millions of resources

Create resources
Host any resource
Get auto-graded reports
or continue with
Microsoft
Apple
Others
By signing up, you agree to our Terms of Service & Privacy Policy
Already have an account?