Q.1
When transforming an entity-relationship model into a relational database design, each entity is represented as a table.
Q.2
Surrogate keys have much meaning for users.
Q.3
(STREET ADDRESS, CITY, STATE, ZIP) is an ideal primary key.
Q.4
When the parent entity is required and the parent has a surrogate key, update actions can be ignored.
Q.5
When the parent entity is required, a new parent row can always be inserted.
Q.6
For every relationship, there are six possible referential integrity actions.
Q.7
An ideal primary key is short, numeric and seldom changing.
Q.8
The DBMS allows surrogate keys to be changed.
Q.9
Cascading updates refers to child rows being automatically deleted when a parent row is deleted.
Q.10
When the child entity is required, we are restricted from creating a new parent row without also creating a corresponding child row at the same time.
Q.11
When the parent entity is required, a new child row can always be inserted.
Q.12
All primary keys are required.
Q.13
Intersection tables are ID-dependent on both their parent tables.
Q.14
For every relationship, there are six possible sets of minimum cardinalities.
Q.15
An intersection table is required to represent M:N relationships.
Q.16
A foreign key is used to implement relationships between tables.
Q.17
The terms alternate key and candidate key mean the same thing.
Q.18
In 1:N relationships, which entity becomes the parent entity is arbitrary.
Q.19
When the parent entity is required, cascading updates and cascading deletions should be allowed or the associated actions on the parent should be prohibited.
Q.20
In a 1:1 relationship, the primary key placement is arbitrary.
0 h : 0 m : 1 s