MC A bank needs to store the following information: customer names, customer addresses, city of a branch, number of accounts, account ids and account balances. How many record types do you need to construct a hierarchical database with this information? One incorrect Three correct Four incorrect Five 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 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 extra set type called 'is-main-professor-of' between record types 'professor' and 'course'. correct 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 It is impossible to model this constraint in CODASYL. incorrect MC In CODASYL, a multivalued composite attribute type can be represented as a: Record type incorrect Data item incorrect Vector incorrect Repeated group correct 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 List the parents as a vector in the data item set of every child. incorrect We cannot model this constraint with the CODASYL framework. incorrect