Database FInal Exam

A foreign key must always contain a value

False

A foreign key must always have a unique value

False

A foreign key should never have a uniqueness constraint placed on it.

False

A primary key field should always be of numeric data type

False

A single attribute primary key may also serve as a foreign key in some circumstances.

False

If a table is in First Normal Form and has a single attribute primary key, it is automatically in Third Normal Form

False

If a table is in First Normal Form and has no non-key attributes, it is automatically in Second Normal Form

False

If a table is in First Normal Form and has no non-key attributes, it is automatically in Third Normal Form

False

In a relational database, all tables must have a primary key

False

It is not possible to implement a many-to-many relationship between two tables in a relational database without introducing an additional intersection table

False

It is not possible to implement a one-to-one relationship between two tables in a relational database without introducing an additional intersection table

False

The value of a primary key field should be changed frequently for security reasons

False

A table cannot have more than one foreign key

False. A fact table have more than one foreign key

A composite primary key may contain within it an attribute that is also a foreign key.

True

A primary key must always contain a value

True

A primary key must always have a unique value

True

If a table is in First Normal Form and has only one non-key attribute, it is automatically in Second Normal Form

True

If a table is in Second Normal Form and has only one non-key attribute (whose value is not derived/computed), it is automatically in Third Normal Form

True

It is not possible to implement a recursive one-to-many relationship between two tables in a relational database without introducing an additional intersection table

True

The data type of a foreign key field should be the same as that of the primary key field that it links to

True

To implement a one-to-many relationship, a foreign key must be inserted into the table at the "many" side

True

To implement a one-to-one relationship between two halves of a table that is being deliberately split (e.g. EMPLOYEE_NONCONFIDENTIAL and EMPLOYEE_CONFIDENTIAL), it is not necessary to define a foreign key provided that both tables have matching primary key values.

True

To implement a policy that all students in a university must be registered on a programme, a foreign key value with a NOT NULL constraint must be inserted into the STUDENT table

True

In a relational database, all tables must have a foreign key

True. Because to establish a relation between tables, connection is necessary.

A table can have more than one primary key

True. Composite Primary Key.