1. (TCO B) For a relationship to be considered a binary relationship, it must satisfy which of the following conditions?
A. It must involve exactly two entity classes.
B. It must have a maximum cardinality of 1:1.
C. It must have a maximum cardinality of 1:N.
D. It must have two entity instances that satisfy the relationship.
Both A and D
Question 2.2. (TCO B) The characteristics of a thing are described by its _____.
identifiers
entities
objects
attributes
relationships
Question 3.3. (TCO C) Which of the following is not true about surrogate keys?
They are identifiers that are supplied by the system, not the users.
They have no meaning to the users.
They are non-unique within a table.
They can be problematic when combining databases.
The DBMS will not allow their values to be changed.
Question 4.4. (TCO C) Many-to-many relationships are represented by _____.
two tables with an M:N relationship
two tables with a 1:N relationship
an intersection table that has M:N relationships with the two tables
an intersection table that has 1:N relationships with the two tables
two intersection tables that each have 1:N relationships with the two tables
Question 5.5. (TCO C) In relational database design, ID-dependent entities are used to _____.
represent N:M relationship
handle associative relationships
handle multivalued attributes
handle archetype/instance relationships
All of the above
Question 6.6. (TCO B) Match the following terms to their definitions.
Potential Matches:
1 : something that the users want to track in their environment
2 : an entity that holds specialized attributes that distinguish it from one or more other similar entities
3 : describes characteristic of an entity
4 : an entity whose identifier includes the identifier of another entity
5 : an entity whose existence depends on the presence of another entity but whose identifier does not include the identifier of the other entity
Answer
: ID-dependent entity
: Subtype
: Weak entity
: Attribute
: Entity
Question 7. 7. (TCO C) How would you represent a one-to-many strong entity relationship in a physical relational database design?