Database Concepts 6th Edition Kroenke Test Bank Download

Database Concepts, 6e (Kroenke/Auer)
Full download at:

Solution Manual:
https://testbankpack.com/p/solution-manual-for-database-concepts-6th-edition-by-kroenke-and-
auer-isbn-0132742926-9780132742924/
Test bank:
https://testbankpack.com/p/test-bank-for-database-concepts-6th-edition-by-kroenke-and-auer-
isbn-0132742926-9780132742924/
Chapter 5 Database Design
1) The first step in representing entities using the relational model is to determine which
identifier will be used as the key.
Answer: FALSE
Diff: 2 Page Ref: 260
2) Relations should always be normalized to the highest degree possible.

Answer: FALSE
3) If a weak entity is ID-dependent but not existence-dependent, it can be represented using the
same techniques as a strong entity.
Answer: FALSE
4) The key of the parent entity becomes part of the key of an ID-dependent entity.
Answer: TRUE
Diff: 1 Page Ref: 266-267
5) From a pragmatic standpoint, the only important rule of normalization is that the determinant
of every functional dependency must be a candidate key.
Answer: TRUE
6) A table that meets the definition of a relation is in 1NF.

Answer: TRUE
7) Boyce-Codd Normal Form was created to address the problem of multivalued dependencies.
Answer: FALSE
8) DK/NF requires that all constraints on data values be logical implications of the definitions of
domains and keys.
Answer: TRUE
1
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall
9) The technique for representing E-R relationships in the relational model is dependent on the
minimum cardinality.
Answer: FALSE
2
10) For a 1:1 relationship, the key of each table should be placed in the other table as the foreign
key.
Answer: FALSE
11) Relationships that are 1:1 do not require referential integrity constraints.
Answer: FALSE
12) In certain circumstances, there may be a preference as to which table in a 1:1 relationship
contains the foreign key.
Answer: TRUE
13) When applied to 1:N relationships, the term "parent" refers to the many side of the
relationship since a child may have many parents.
Answer: FALSE
14) To represent a 1:N relationship in the relational model, the key of the entity on the one side
of the relationship is placed as a foreign key in the entity on the many side of the relationship.
Answer: TRUE
15) To represent a 1:N relationship in the relational model, the key of either entity may be placed
as a foreign key in the other entity.
Answer: FALSE
16) In the relational model, many-to-many relationships cannot be directly represented by

relations the way 1:1 and 1:N relationships can.
Answer: TRUE
17) To represent a M:N relationship in the relational model, an intersection relation is created to
represent the relationship itself.
Answer: TRUE
18) The key for an intersection relation is always the combination of the keys of the parent
entities.
Answer: TRUE
19) All recursive relationships are 1:1.

Answer: FALSE
3
20) Recursive relationships can be represented in the relational model using the same techniques
that are used for binary relationships.
Answer: TRUE
21) Microsoft Access uses the same pure N:M relationships that occur in data modeling.
Answer: FALSE
22) As far as Microsoft Access is concerned, there are no N:M relationships.

Answer: TRUE
23) As far as Microsoft Access is concerned, there are no 1:N relationships.

Answer: FALSE
24) By default, Microsoft Access creates 1:1 relationships between tables.

Answer: FALSE
25) To create a 1:1 relationship in Microsoft Access, the Indexed property of the foreign key
column must be set to Yes (No Duplicates).
Answer: TRUE
26) Which of the following is the first step in representing entities using the relational model?
A) Define a table for each entity.
B) Determine identifiers.
C) Determine foreign keys.
D) Examine the entity against normalization criteria.
E) Define a primary key.
Answer: A
27) Which of the following would be a reason to denormalize a relation?

A) Relax security
B) Lack of design time
C) End user preference
D) Improve performance
E) None of the above
Answer: D
4
28) Which of the following is true about representing a weak entity with the relational model?
A) If the weak entity is existence-dependent, the key of the parent must be part of the key of the
weak entity.
B) If the strong entity has a minimum cardinality of 1, the key of the weak entity must be part of
the strong entity.
C) If the weak entity is ID-dependent, the key of the weak entity must be part of the key of the
parent entity.
D) If the weak entity is ID-dependent, the key of the parent entity must be part of the key of the
weak entity.
E) If the parent entity is existence-dependent, then the minimum cardinality of the weak entity is
zero.
Answer: D
29) Which normal form is defined as any table meeting the definition of a relation?
A) 1NF
B) 2NF
C) BCNF
D) 4NF
E) DK/NF
Answer: A
30) E. F. Codd and R. Boyce developed Boyce-Codd Normal Form (BCNF) to resolve anomalies
in the:
A) 1NF.
B) 2NF.
C) 3NF.
D) 4NF.
E) DK/NF.
Answer: C
31) Which normal form was developed in order to eliminate multivalued dependencies?
A) 3NF
B) BCNF
C) 4NF
D) 5NF
E) DK/NF
Answer: C
5
32) Which normal form deals with the problem of tables that can be split apart but not correctly
joined back together?
A) 3NF
B) BCNF
C) 4NF
D) 5NF
E) DK/NF
Answer: D
33) The fundamental rule of normalization can be stated as:

A) every table must meet the definition of a relation.
B) every determinant must be a candidate key.
C) every domain must be a logical consequence of the constraints.
D) every key must be a candidate key.
E) every constraint must be a determinant.
Answer: B
34) Given the generic relation:

GENERIC (PKey1, PKey2, Attribute1, Attribute2, Attribute3),
and the functional dependencies:
(PKey1, PKey2) → Attribute1 and PKey2 → (Attribute2, Attribute3),
which of the following is true?
A) GENERIC is not fully normalized.
B) PKey1 is a determinant.
C) PKey2 is a candidate key.
D) GENERIC is in DK/NF.
E) All of the above
Answer: A
35) Which of the following is not necessarily true of a relation that is in 4NF?
A) It is in 2NF.
B) It is in DK/NF.
C) It has no multivalued dependencies.
D) It is in Boyce-Codd Normal Form.
E) All of the above are true.
Answer: B
6
36) DK/NF requires:
A) every determinant must be a logical consequence of the definition of domains.
B) every domain of data values must be a logical consequence of the definition of keys.
C) every constraint on data values must be a logical consequence of the definition of domains
and keys.
D) every key must be a logical consequence of the definition of constraints and determinants.
E) every consequence of data values must originate in the definition of determinants and keys.
Answer: C
37) Which of the following is true when representing a 1:1 binary relationship using the
relational model?
A) The key of the entity with the highest minimum cardinality must be placed in the other entity
as a foreign key.
B) The key of each entity must be placed in the other as a foreign key.
C) The key of either entity is placed in the other as a foreign key.
D) The key of the entity with the most attributes must be placed in the other entity as a foreign
key.
E) Both entities must have the same primary key.
Answer: C
38) Given TABLE_A (Attribute1, Attribute2, Attribute3) and TABLE_B (Attribute4,

Attribute5, Attribute6) shown in the figure below, which of the following would display the
correct placement of foreign keys in the relational model?
A) TABLE_A (Attribute1, Attribute2, Attribute3)

TABLE _B (Attribute4, Attribute5, Attribute6, Attribute1)
B) TABLE _A (Attribute1, Attribute2, Attribute3, Attribute4, Attribute5)
TABLE _B (Attribute4, Attribute5, Attribute6)
C) TABLE _A (Attribute1, Attribute2, Attribute3, Attribute4)
TABLE _B (Attribute4, Attribute5, Attribute6, Attribute1)
D) TABLE _A (Attribute1, Attribute2, Attribute3)
E) TABLE _A (Attribute1, Attribute2, Attribute3, Attribute6)
Answer: A
7
39) Which of the following is the correct technique for representing a 1:N relationship in the
relational model?
A) The key of the entity on the one side is placed into the relation for the entity on the many side.
B) The key of the child is placed into the relation of the parent.
C) The key of either relation can be placed into the other relation.
D) The key of the entity on the many side is placed into the relation for the entity on the one side.
E) An intersection relation is created, and the keys from both parent entities are placed as keys in
the intersection relation.
Answer: A
40) Given the entities PRODUCT and SUPPLIER shown in the figure below, which of the
following would represent the correct placement of foreign keys?
A) PRODUCT (ProductID, Description, Cost)

SUPPLIER (SupplierID, ContactName, PhoneNumber)
B) PRODUCT (ProductID, Description, Cost)
SUPPLIER (SupplierID, ContactName, PhoneNumber, ProductID)
C) PRODUCT (ProductID, Description, Cost, SupplierID)
D) PRODUCT (ProductID, Description, Cost, ContactName)
E) PRODUCT (ProductID, Description, Cost, SupplierID)
Answer: E
41) Which of the following is the correct technique for representing a M:N relationship using the
relational model?
A) An intersection relation is created, and the key of either entity is placed as a key in both the
intersection relation and in the other relation.
B) An intersection relation is created with a surrogate key, which is placed in each of the parent
entities.
C) An intersection relation is created, and the keys of both parent entities are placed as a
composite key in the intersection relation.
D) The key from either relation is placed as a foreign key in the other relation.
E) None of the above
Answer: C
8
42) Given the PRODUCT and SUPPLIER entities in the figure below, which of the following
would represent the correct placement of foreign keys?
A) PRODUCT (ProductID, Description, Cost)

B) PRODUCT (ProductID, Description, Cost, SupplierID)
C) PRODUCT (ProductID, Description, Cost)
PRODUCT_SUPPLIER (ProductID, SupplierID)
D) PRODUCT (ProductID, Description, Cost, SupplierID)
E) PRODUCT (ProductID, Description, Cost)
PRODUCT_SUPPLIER (ProductID, SupplierID)
Answer: E
43) What relationship pattern is illustrated in the following schema?
PRODUCT (ProductID, Description)

PRODUCT_SUPPLIER (ProductID, SupplierID, Cost)
ProductID in PRODUCT_SUPPLIER must exist in ProductID in PRODUCT

SupplierID in PRODUCT_SUPPLIER must exist in SupplierID in PRODUCT
A) Association relationship
B) Intersection relationship
C) Recursive relationship
D) Strong entity relationship
E) Supertype/subtype relationship
Answer: A
9
VEHICLE (VehicleID, Cost)

CAR (VehicleID, NumberOfSeats)
TRUCK (VehicleID, CargoCapacity)
VehicleID in CAR must exist in VehicleID in VEHICLE

VehicleID in TRUCK must exist in VehicleID in VEHICLE
Answer: E
EMPLOYEE (EmployeeID, OfficePhone, Manager)
Manager in EMPLOYEE must exist in EmployeeID in EMPLOYEE

Answer: C
46) Microsoft Access does not create N:M relationships because:

A) Microsoft Access creates databases based on database designs instead of data models.
B) Microsoft Access creates databases based on data models instead of database designs.
C) Microsoft Access cannot implement association relationships.
D) Microsoft Access cannot implement supertype/subtype relationships.
E) Microsoft Access cannot implement recursive relationships.
Answer: A
47) As far as Microsoft Access is concerned, there are no:

A) 1:1 relationships.
B) 1:N relationships.
C) N:1 relationships.
D) N:M relationships.
E) recursive relationships.
Answer: D
10
48) By default, when Microsoft Access creates a relationship between two tables, it creates a(n):
A) 1:1 relationship.
B) 1:N relationship.
C) N:M relationship.
D) association relationship.
E) recursive relationship.
Answer: B
49) To create a 1:1 relationship between two tables in Microsoft Access:

A) the Indexed property of the foreign key column must be set to No.
B) the Indexed property of the foreign key column must be set to Yes (Duplicates OK).
C) the Indexed property of the foreign key column must be set to Yes (No Duplicates).
D) the Data Type of the foreign key column must be set to AutoNumber.
E) the Smart Tag property of the foreign key column must be set to Foreign Key.
Answer: C
50) After a 1:1 relationship has been created between two tables in Microsoft Access, the
Relationship Type of One-To-One appears:
A) in the Relationship Type property of the primary key column in table Design View.
B) in the Relationship Type property of the foreign key column in table Design View.
C) in the table object in the Relationships window.
D) in the Show Table dialog box.
E) in the Edit Relationships dialog box.
Answer: E
51) The first step of database design is to define a table for each ________.
Answer: entity
52) Once a table has been defined, it should be examined according to ________ criteria.
Answer: normalization
53) There are cases where it is possible to normalize a table too far, in which case there may be a
need for ________.
Answer: denormalization
54) If a table meets the definition of a relation, it is said to be in ________.

Answer: first normal form (1NF)
11
55) ________ eliminated some anomalies found in the third normal form, and was later followed
by a fourth and fifth normal form.
Answer: Boyce-Codd Normal Form (BCNF)
56) R. Fagin defined the ________, and a relation in this form has no anomalies.
Answer: domain key / normal form (DK/NF)
57) To normalize a relation, the determinant of every functional dependency should be a(n)
________.
Answer: candidate key
58) To represent a many-to-many relationship in the relational model, a(n) ________ table is
used.
Answer: intersection
59) For a(n) ________ weak entity, it is necessary to add the key of the parent entity to the weak
entity's relation so that this added attribute becomes part of the weak entity's key.
Answer: ID-dependent
60) A(n) ________ is a relationship among entities of the same class.

Answer: recursive relationship
61) Microsoft Access does not create N:M relationships because Microsoft Access creates
databases based on ________.
Answer: database designs
62) As far as Microsoft Access is concerned, there are no ________.

Answer: N:M relationships
63) By default, when Microsoft Access creates a relationship between two tables it creates a(n)
________ relationship.
Answer: 1:N
64) To create a 1:1 relationship between two tables in Microsoft Access, the Indexed property of
the foreign key column must be set to ________.
Answer: Yes (No Duplicates)
12
65) After a 1:1 relationship has been created between two tables in Microsoft Access, the
Relationship Type of One-To-One appears in the ________.
Answer: Edit Relationships dialog box
66) Explain the process of representing an entity using the relational model.
Answer: To represent an entity using the relational model, first define a relation for the entity.
The name of the entity is the name of the relation. Each attribute in the entity becomes a column
in the relation. If the entity had a unique identifier that would make an appropriate primary key,
then that attribute is made the key. If there is no such attribute, then the development team
discusses identifiers with the users to determine if an acceptable key attribute exists. If not, then
a surrogate key may be used. Finally, the relation is evaluated against the normalization criteria.
Changes to the design may be necessary to satisfy the normalization requirements.
67) What is denormalization and why can it be desirable?

Answer: Denormalization is the process of consolidating relations that are in a higher normal
form into a single relation that is in a lower normal form, thereby making it susceptible to more
anomalies. Denormalization can be desirable for two reasons. First, sometimes the act of
normalizing a table can cause it to become too cumbersome or contrived, which makes it
difficult to work with. Therefore denormalization may be preferable when the dangers of the
additional anomalies are considered to be of less importance than the ease of working with the
relations. Second, processing multiple tables requires more processing overhead than processing
a single table. Therefore, performance can often be improved by using a single, denormalized
table than multiple, normalized tables. When the performance gain outweighs the dangers of the
additional anomalies, the denormalized table may be preferred.
68) What are "normal forms"?

Answer: Normal forms are a way of classifying tables based on the types of anomalies to which
they are vulnerable. Each normal form in the group — 1NF, 2NF, 3NF, BCNF, 4NF, and 5NF —
addresses anomalies that were identified in the preceding normal form. Domain Key normal
form is another type of normal form, but it does not build off of the other normal forms. Any
table in DK/NF is known to have no anomalies.
69) What is Boyce-Codd Normal Form, and why was it developed?

Answer: The Boyce-Codd Normal Form (BCNF) is a normal form that falls between 3NF and
4NF. E. F. Codd developed the first three normal forms (1NF, 2NF, and 3NF) to deal with
various table anomalies. After it was discovered that some anomalies could exist in tables in
3NF, Codd and R. Boyce developed BCNF to deal with the 3NF anomalies.
13
70) What makes DK/NF different from all of the other normal forms?
Answer: Domain Key Normal Form (DK/NF) is different from 1NF, 2NF, 3NF, BCNF, 4NF,
and 5NF in terms of its evolution and the scope of anomalies addressed. All normal forms
previous to DK/NF were developed by an evolutionary process in which each normal form
represented a solution to a given anomaly that was found to exist in the preceding normal form.
Therefore, even with 5NF the possibility exists that more anomalies are present but haven't yet
been found. DK/NF developed outside this evolutionary process as the result of an investigation
to find a set of conditions that would prevent any anomalies from existing. Therefore, a table in
DK/NF cannot have any anomalies, known or unknown.
71) Explain the representation of ID-dependent weak entities using the relational model.
Answer: A weak entity is represented in the relational model similarly to the representation of a
strong entity. First, a relation is defined for the entity. Each attribute in the weak entity becomes
a column in the relation. The primary key of the strong entity on which the weak entity is ID-
dependent is added to the relation and is made a part of the primary key of the weak entity's
relation along with the weak entity's identifier. Finally, the relation is evaluated according to the
normalization criteria, and any necessary design changes are made to normalize the relation.
72) What is an association relationship, and how does it differ from an N:M relationship?
Answer: An association relationship is very similar to an N:M relationship except that the
intersection table has attributes of its own. This means that in addition to the foreign key fields
linking to the two strong entities, there is at least one additional field in what would otherwise be
called the intersection table but is now an association table. For example, the intersection table
ENROLLMENT for STUDENT and CLASS showing student enrollment in each class would
normally have two columns: StudentID and ClassID. However, we can turn this intersection
table into an association table by adding the column Grade, which records each student's grade in
each class.
73) Write the schema to represent the entities below, including tables, the proper placement of
the foreign key, and referential integrity constraint.
Answer: STUDENT (StudentID, StuName, StuMajor, StuPhone, AdvisorID)

ADVISOR (AdvisorID, AdvName, AdvOffice, AdvPhone)
AdvisorID in STUDENT must exist in AdvisorID in ADVISOR.

14
74) How are many-to-many relationships addressed in the relational model?
Answer: Many-to-many relationships cannot be directly addressed in the relational model;
therefore, they must be reduced to one-to-many relationships. This is done by creating an
intersection relation that represents the complex many-to-many relationship. This intersection
relation is given the keys of the two parent relations and both of these are used together to make
the primary key of the intersection relation. The parent entities will have one-to-many
relationships with the intersection relation, which can be represented normally within the
relational model.
75) How are one-to-one recursive relationships addressed using the relational model?
Answer: One-to-one recursive relationships are addressed just the same as one-to-one
nonrecursive relationships. The only difference is that both of the related entity instances are in
the same entity class. The key of either instance is placed in the other instance as a foreign key.
In the case of a recursive relationship, this means that a new attribute is added to the entity class
with the recursive relationship. For each instance, this new attribute will contain the value of the
key attribute of the instance that is related.
76) How are 1:1, 1:N and N:M relationships handled in Microsoft Access?
Answer: By default, when Microsoft Access creates a relationship between two tables, it creates
a 1:N relationship. N:M relationships are created in Microsoft Access, as in all other DBMS
products, as two 1:N relationships linking the two tables (based on the original two entities)
through an intersection table. As far as Microsoft Access is concerned, there are no N:M
relationships! To create a 1:1 relationship between two tables in Microsoft Access, the Indexed
property of the foreign key column in the table containing the foreign key must be set to Yes (No
Duplicates) before the relationship is created. With the property set, the relation is automatically
created as a 1:1 relationship.
15

Database Concepts 6th Edition Kroenke Test Bank Download

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Database Concepts 6th Edition Kroenke Test Bank Download

Uploaded by

Copyright:

Available Formats

Database Concepts, 6e (Kroenke/Auer)

Full download at:

Chapter 5 Database Design

2) Relations should always be normalized to the highest degree possible.

6) A table that meets the definition of a relation is in 1NF.

16) In the relational model, many-to-many relationships cannot be directly represented by

19) All recursive relationships are 1:1.

22) As far as Microsoft Access is concerned, there are no N:M relationships.

23) As far as Microsoft Access is concerned, there are no 1:N relationships.

24) By default, Microsoft Access creates 1:1 relationships between tables.

27) Which of the following would be a reason to denormalize a relation?

33) The fundamental rule of normalization can be stated as:

34) Given the generic relation:

38) Given TABLE_A (Attribute1, Attribute2, Attribute3) and TABLE_B (Attribute4,

A) TABLE_A (Attribute1, Attribute2, Attribute3)

A) PRODUCT (ProductID, Description, Cost)

A) PRODUCT (ProductID, Description, Cost)

43) What relationship pattern is illustrated in the following schema?

PRODUCT (ProductID, Description)

ProductID in PRODUCT_SUPPLIER must exist in ProductID in PRODUCT

VEHICLE (VehicleID, Cost)

VehicleID in CAR must exist in VehicleID in VEHICLE

45) What relationship pattern is illustrated in the following schema?

EMPLOYEE (EmployeeID, OfficePhone, Manager)

Manager in EMPLOYEE must exist in EmployeeID in EMPLOYEE

46) Microsoft Access does not create N:M relationships because:

47) As far as Microsoft Access is concerned, there are no:

49) To create a 1:1 relationship between two tables in Microsoft Access:

54) If a table meets the definition of a relation, it is said to be in ________.

60) A(n) ________ is a relationship among entities of the same class.

62) As far as Microsoft Access is concerned, there are no ________.

67) What is denormalization and why can it be desirable?

68) What are "normal forms"?

69) What is Boyce-Codd Normal Form, and why was it developed?

Answer: STUDENT (StudentID, StuName, StuMajor, StuPhone, AdvisorID)

AdvisorID in STUDENT must exist in AdvisorID in ADVISOR.

You might also like