04
Chapter 4: Constraints
TRUE/FALSE
1. Constraints are rules used to enforce business rules, practices, and policies.
ANS: T PTS: 1 REF: 91
2. Constraints are used to ensure the accuracy and integrity of the data contained in the database.
ANS: T PTS: 1 REF: 91
3. A constraint can only be created as part of the CREATE TABLE command.
ANS: F PTS: 1 REF: 93
4. A constraint name can consist of up to 10 characters.
ANS: F PTS: 1 REF: 93
5. A primary key is usually given the abbreviation _pk in the constraint name if the name is assigned by the user.
ANS: T PTS: 1 REF: 93
6. Any constraint can be created at the table or the column level.
ANS: F PTS: 1 REF: 94
7. A foreign key constraint can only be created at the column level.
ANS: F PTS: 1 REF: 94 | 99
8. A NOT NULL constraint can only be created at the column level.
ANS: T PTS: 1 REF: 94
9. A constraint for a composite primary key must be created at the table level.
ANS: T PTS: 1 REF: 96
10. The CONSTRAINT keyword is required if the user is going to assign a name to a constraint.
ANS: T PTS: 1 REF: 94
11. A constraint is always enforced at the table level.
ANS: T PTS: 1 REF: 95
12. The table level approach can be used to create any constraint, except a CHECK constraint.
ANS: F PTS: 1 REF: 94
13. A PRIMARY KEY constraint will make certain the column designated as the primary key does not contain a NULL value.
ANS: T PTS: 1 REF: 95
14. The MODIFY clause is used with the ALTER TABLE command to add a PRIMARY KEY constraint to an existing table.
ANS: F PTS: 1 REF: 96
15. Only one PRIMARY KEY constraint can exist for each table.
ANS: T PTS: 1 REF: 97
16. A FOREIGN KEY constraint can be added to the column of a table to ensure that the referenced data value actually exists in the other table.
ANS: T PTS: 1 REF: 99
17. If a FOREIGN KEY constraint exists, then a record cannot be deleted from the parent table if that row is referenced by an entry in the child table.
ANS: T PTS:
TRUE/FALSE
1. Constraints are rules used to enforce business rules, practices, and policies.
ANS: T PTS: 1 REF: 91
2. Constraints are used to ensure the accuracy and integrity of the data contained in the database.
ANS: T PTS: 1 REF: 91
3. A constraint can only be created as part of the CREATE TABLE command.
ANS: F PTS: 1 REF: 93
4. A constraint name can consist of up to 10 characters.
ANS: F PTS: 1 REF: 93
5. A primary key is usually given the abbreviation _pk in the constraint name if the name is assigned by the user.
ANS: T PTS: 1 REF: 93
6. Any constraint can be created at the table or the column level.
ANS: F PTS: 1 REF: 94
7. A foreign key constraint can only be created at the column level.
ANS: F PTS: 1 REF: 94 | 99
8. A NOT NULL constraint can only be created at the column level.
ANS: T PTS: 1 REF: 94
9. A constraint for a composite primary key must be created at the table level.
ANS: T PTS: 1 REF: 96
10. The CONSTRAINT keyword is required if the user is going to assign a name to a constraint.
ANS: T PTS: 1 REF: 94
11. A constraint is always enforced at the table level.
ANS: T PTS: 1 REF: 95
12. The table level approach can be used to create any constraint, except a CHECK constraint.
ANS: F PTS: 1 REF: 94
13. A PRIMARY KEY constraint will make certain the column designated as the primary key does not contain a NULL value.
ANS: T PTS: 1 REF: 95
14. The MODIFY clause is used with the ALTER TABLE command to add a PRIMARY KEY constraint to an existing table.
ANS: F PTS: 1 REF: 96
15. Only one PRIMARY KEY constraint can exist for each table.
ANS: T PTS: 1 REF: 97
16. A FOREIGN KEY constraint can be added to the column of a table to ensure that the referenced data value actually exists in the other table.
ANS: T PTS: 1 REF: 99
17. If a FOREIGN KEY constraint exists, then a record cannot be deleted from the parent table if that row is referenced by an entry in the child table.
ANS: T PTS: