Chapter 5 Flashcards

1
Q

A data model is a plan for a database design.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

The method of constructing data models used in the text is the extended entity-relationship (E-R) model.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

An entity is something that users want to track.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Entities of a given type are grouped into entity classes.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

An entity class is described by the structure of the entities in that class.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

An entity instance is the occurrence of a particular entity.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

An entity instance of an entity class is the representation of a particular entity and is described by the values of the attributes of the entity.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

An identifier of an entity instance is one or more attributes that name or identify entity instances.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

A compound identifier is an identifier consisting of two or more attributes.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

In E-R modeling, an attribute describes the characteristics of an entity.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

In E-R modeling, entities within an entity class may have different attributes.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

An identifier of an entity instance must consist of one and only one attribute.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

A composite identifier is defined as a composite attribute that is an identifier.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

An identifier serves the same role for a table that a key does for an entity.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Entities can be associated with one another in relationships.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

The degree of a relationship is the number of entity classes in the relationship.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

A binary relationship is a relationship between two or more entities.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Relationships of degree two are referred to as binary relationships.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

E-R modeling recognizes both relationship classes and relationship instances.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

In today’s E-R models, attributes of relationships are still used.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

A single relationship class involves only one entity class.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

A binary relationship is a relationship based on numerical entity instance identifiers.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

The degree of a relationship is expressed as the relationship’s maximum cardinality.

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

When transforming a data model into a relational design, relationships of all degrees are treated as combinations of binary relationships.

25
The principal difference between an entity and a table is that you can express a relationship between entities without using foreign keys.
True
26
When designing a database, first identify the entities, then determine the attributes, and finally create the relationships.
False
27
The notation 1:N shows the relationship's maximum cardinality.
True
28
Relationships are classified by their cardinality.
True
29
A relationship's maximum cardinality indicates the maximum number of entities that can participate in the relationship.
False
30
In an E-R model, the three types of maximum cardinality are 1:1, 1:N and N:M.
True
31
In a 1:N relationship, the term parent refers to the N side of the relationship.
False
32
In a 1:N relationship, the parent entity is on the one side of the relationship, and the child entity is on the many side of the relationship.
True
33
A relationship's minimum cardinality indicates the number of entity instances that must participate in the relationship.
True
34
A relationship's minimum cardinality indicates whether or not an entity must participate in the relationship.
True
35
In an E-R model, the three types of minimum cardinality are mandatory, optional and indeterminate.
False
36
An entity that represents something that can exist on its own is called a strong entity.
True
37
E-R models use an identifying relationship to connect entities that are ID-dependent.
True
38
An ID-dependent entity is an entity whose identifier includes the identifier of another entity.
True
39
ID-dependent entities are associated by a nonidentifying relationship.
False
40
A weak entity is an entity that cannot exist in the database without (and is logically dependent upon) another type of entity also existing in the database.
True
41
) ID-dependent entities are a common type of weak entity.
True
42
All weak entities must have a minimum cardinality of 1 on the entity on which it depends.
True
43
Subtype entities contain only attributes unique to the subtypes.
True
44
An attribute that determines which subtype is appropriate is called a discriminator.
True
45
An exclusive subtype pattern has one supertype entity that relates to one or more subtype entities.
False
46
Entities with an IS-A relationship should have the same identifier.
True
47
One example of a database design using an ID-dependent relationship is the association pattern.
True
48
One example of a database design using a strong relationship is the multivalued attribute pattern.
False
49
One example of a database design using an ID-dependent relationship is the archetype/instance pattern.
True
50
Data modelers agree that weak, non-ID-dependent entities exist and are important.
False
51
Entities containing optional sets of attributes are often represented using subtypes.
False
52
The supremetype entity contains the attributes that are common to all subtypes.
False
53
An attribute that determines which subtype is appropriate is called a discriminator.
True
54
Subtypes can be exclusive or inclusive.
True
55
Relationships between supertypes and subtypes are called IS-A relationships.
True
56
Relationships among instances of a single entity class are called redundant relationships.
False
57
There are three types of recursive relationships: 1:1, 1:N and N:M.
True
58
Recursive relationships only exist for one-to-one relationships.
False