31. In a university, each course may have prerequisites. How should prerequisites be represented?

A. One-to-many relationship
B. Recursive relationship
C. Multivalued attribute
D. Derived attribute

Answer: B
Explanation:

Prerequisites are modeled as a recursive relationship within the Course entity, linking courses to other courses.

32. In a hospital, a doctor can specialize in multiple departments, and each department can have multiple doctors. How should this relationship be modeled?

A. One-to-one
B. One-to-many
C. Many-to-many
D. Weak entity

Answer: C
Explanation:

This is a many-to-many relationship between Doctor and Department, which may require an associative entity to store additional attributes like years of experience.

33. In a banking system, a loan may be co-owned by multiple customers, and a customer may have multiple loans. How should this be represented?

A. One-to-one
B. One-to-many
C. Many-to-many
D. Derived attribute

Answer: C
Explanation:

This is a many-to-many relationship between Customer and Loan. An associative entity can capture relationship attributes like loan percentage owned by each customer.

34. In a hospital, “Medication Schedule” depends on the patient and prescription. How should it be modeled?

A. Simple attribute
B. Derived attribute
C. Weak entity
D. Associative entity

Answer: D
Explanation:

The schedule is a relationship-specific entity, so an associative entity linking Patient and Prescription is appropriate.

35. In a university, a student may be enrolled in multiple clubs, and each club may have multiple students. How is this relationship represented?

A. One-to-one
B. One-to-many
C. Many-to-many
D. Recursive

Answer: C
Explanation:

This is a many-to-many relationship between Student and Club, usually implemented with an associative entity to capture membership details.

36. In a travel agency, a booking may include multiple passengers, and each passenger may have multiple bookings. How should this be modeled?

A. One-to-one
B. One-to-many
C. Many-to-many
D. Derived relationship

Answer: C
Explanation:

This is a many-to-many relationship between Booking and Passenger, typically implemented via an associative entity.

37. In a hospital, the “BMI” of a patient is computed from weight and height. How should BMI be represented?

A. Simple attribute
B. Derived attribute
C. Multivalued attribute
D. Weak entity

Answer: B
Explanation:

BMI is a derived attribute because it can be calculated from other stored attributes like weight and height.

38. In a university, “Student Address” is composed of Street, City, and ZIP. How should this be modeled?

A. Simple attribute
B. Derived attribute
C. Composite attribute
D. Weak entity

Answer: C
Explanation:

Address is a composite attribute because it consists of multiple subparts (Street, City, ZIP).

39. In an e-commerce system, a review is associated with a customer and a product. How should Review be represented?

A. Simple attribute
B. Weak entity
C. Derived attribute
D. Recursive relationship

Answer: B
Explanation:

Review is a weak entity because it depends on both Customer and Product for identification.

40. In a university, a student may take multiple exams, and each exam may include multiple students. How should this be modeled?

A. One-to-one
B. One-to-many
C. Many-to-many
D. Derived relationship

Answer: C
Explanation:

This is a many-to-many relationship between Student and Exam, best implemented with an associative entity to store grades.