MC	If a hierarchical model contains N:M relationship types that have been integrated by repeating the child nodes where necessary, what are the dangers of updating the database?	Slower retrieval of data	incorrect	Creating data inconsistency	correct	Creating unnecessary records	incorrect	All of the above	incorrect	
MC	In CODASYL, a multivalued composite attribute type can be represented as a:	Vector	incorrect	Record type	incorrect	Repeated group	correct	Data item	incorrect	
MC	The human resources department of a university wants to make sure that every course has exactly one main professor. How can they implement this constraint using the CODASYL framework?	They introduce an 'is-main-professor' record type between record types 'professor' and 'course' to model the correct relationship.	incorrect	It is impossible to model this constraint in CODASYL.	incorrect	They introduce an extra set type called 'is-main-professor-of' between record types 'professor' and 'course'.	correct	They introduce 'main professor' as a data item in the record type 'professor'.	incorrect	
MC	The human resources department of a university wants to make sure that every course has exactly one main professor. How can they implement this constraint using the CODASYL framework?	They introduce an 'is-main-professor' record type between record types 'professor' and 'course' to model the correct relationship.	incorrect	They introduce 'main professor' as a data item in the record type 'professor'.	incorrect	They introduce an extra set type called 'is-main-professor-of' between record types 'professor' and 'course'.	correct	It is impossible to model this constraint in CODASYL.	incorrect	
MC	If a hierarchical model contains N:M relationship types that have been integrated by repeating the child nodes where necessary, what are the dangers of updating the database?	Slower retrieval of data	incorrect	Creating data inconsistency	correct	Creating unnecessary records	incorrect	All of the above	incorrect	
MC	In CODASYL, a multivalued composite attribute type can be represented as a:	Repeated group	correct	Data item	incorrect	Record type	incorrect	Vector	incorrect	
MC	If a hierarchical model contains N:M relationship types that have been integrated by repeating the child nodes where necessary, what are the dangers of updating the database?	Slower retrieval of data	incorrect	Creating data inconsistency	correct	Creating unnecessary records	incorrect	All of the above	incorrect	
MC	How can the CODASYL framework correctly model a family tree, taking into account that every child has to have (at least) two parents?	Use a set type 'is parent of' between record types 'parent' and 'child'.	incorrect	Use a dummy record type 'is parent of' between record types 'parent' and 'child'.	correct	We cannot model this constraint with the CODASYL framework.	incorrect	List the parents as a vector in the data item set of every child.	incorrect	
MC	How can the CODASYL framework correctly model a family tree, taking into account that every child has to have (at least) two parents?	Use a dummy record type 'is parent of' between record types 'parent' and 'child'.	correct	We cannot model this constraint with the CODASYL framework.	incorrect	Use a set type 'is parent of' between record types 'parent' and 'child'.	incorrect	List the parents as a vector in the data item set of every child.	incorrect	
MC	How can the CODASYL framework correctly model a family tree, taking into account that every child has to have (at least) two parents?	We cannot model this constraint with the CODASYL framework.	incorrect	Use a set type 'is parent of' between record types 'parent' and 'child'.	incorrect	Use a dummy record type 'is parent of' between record types 'parent' and 'child'.	correct	List the parents as a vector in the data item set of every child.	incorrect