✔ Scroll down and test yourself — answers are hidden under the “View Answer” button.
A. One-to-one
B. One-to-many
C. Many-to-many
D. Recursive
Explanation:
Each patient can have multiple appointments, making this a one-to-many relationship from Patient to Appointment.
A. One-to-one
B. One-to-many
C. Many-to-many
D. Recursive relationship
Explanation:
This is a one-to-many relationship from Professor to Student because each professor can supervise many students, but a student has only one supervisor.
A. Multivalued attribute
B. Weak entity
C. Associative entity
D. Derived attribute
Explanation:
Cart contents involve a relationship-specific attribute (quantity), so an associative entity linking Cart and Product is required.
A. Simple attribute
B. Multivalued attribute
C. Weak entity
D. Derived attribute
Explanation:
Since a book can belong to multiple genres, “genre” is a multivalued attribute or can be represented as a separate entity.
A. Simple attribute
B. Derived attribute
C. Weak entity
D. Multivalued attribute
Explanation:
Total Bill is a derived attribute because it can be calculated from the sum of individual treatment charges.
A. Weak entity
B. Associative entity
C. Derived attribute
D. Simple attribute
Explanation:
Enrollment is an associative entity because it connects Student and Course and contains additional attributes like grades.
A. Multivalued attribute
B. Derived attribute
C. Weak entity
D. Simple attribute
Explanation:
Position is a multivalued attribute because an employee may hold multiple positions simultaneously or sequentially.
A. One-to-one
B. One-to-many
C. Many-to-many
D. Derived attribute
Explanation:
This is a one-to-many relationship where an account can have multiple transactions, but each transaction belongs to a single account.
A. Simple attribute
B. Multivalued attribute
C. Derived attribute
D. Weak entity
Explanation:
Transcript is a derived attribute as it is computed from the grades of all courses taken by the student.
A. One-to-one
B. One-to-many
C. Many-to-many
D. Derived relationship
Explanation:
This is a many-to-many relationship between Passenger and Flight, best implemented with an associative entity to store booking details.
No comments:
Post a Comment