1Z0-898 · Question #49
A developer who is designing entity classes to map a legacy database encounters a table called STUDENT_RECORD . This table has two columns, STUDENT_ID and STUDENT_INFO_ID. The primary key of this…
The correct answer is A. Model the student table as a student entity and STUDENT_DATA table Student-Data entity. C. Model the STUDENT table as a Student entity and the STUDENT-DATA table as a Student-Data. There is a many-to-many relationship between the Student table and the Student_table. This can be modeled with one many-to-many relation (A) or two many-to-one relations (C). not B, not D: Not a one-one relationship.
Question
A developer who is designing entity classes to map a legacy database encounters a table called STUDENT_RECORD . This table has two columns, STUDENT_ID and STUDENT_INFO_ID. The primary key of this table consists of both columns, and there is a unique constraint on each info column. The STUDENT_ID column is foreign key to the STUDENT table and STUDENT_INFO_ID column is a foreign key to the STUDENT_DAT table. What entity classes and relationships can the developer use to model these tables and relationship?(Choose two)
Options
- AModel the student table as a student entity and STUDENT_DATA table Student-Data entity.
- BModel the STUDENT table as a Student entity and the STUDENT-DATA table as a Student-Data
- CModel the STUDENT table as a Student entity and the STUDENT-DATA table as a Student-Data
- DModel the STUDENT table as a Student entity and the STUDENT-DATA table as a Student-Data
How the community answered
(63 responses)- A83% (52)
- B11% (7)
- D6% (4)
Explanation
There is a many-to-many relationship between the Student table and the Student_table. This can be modeled with one many-to-many relation (A) or two many-to-one relations (C). not B, not D: Not a one-one relationship.
Topics
Community Discussion
No community discussion yet for this question.