Chapter 5: Advanced Data Modeling
69. An entity cluster is considered “virtual” or “ ” in the sense that it is not actually an entity in the final
ERD.
70. Usually, a data modeler uses a natural identifier as the of the entity being modeled, assuming that the
entity has a natural identifier.
71. Unique values can be better managed when they are , because the database can use internal routines to
implement a counter-style attribute that automatically increments values with the addition of each new row.
72. Composite primary keys are particularly useful as identifiers of composite entities, where each primary key
combination is allowed in the M:N relationship.
73. A weak-entity in a strong identifying relationship with a parent entity is normally used to represent a(n)
that is represented in the data model as two separate entities.
74. Composite keys are useful as identifiers of weak entities, where the weak entity has a strong relationship
with the parent entity.
75. One practical advantage of a(n) key is that because it has no intrinsic meaning, values for it can be
generated by the DBMS to ensure that unique values are always provided.
76. While using a surrogate key, one must ensure that the candidate key of the entity in question performs properly
through the use of the “ ” and “not null” constraints.
77. From a data modeling point of view, data refer to data whose values change over time and for which
one must keep a history of the data changes.
78. A occurs when a relationship is improperly or incompletely identified and is therefore represented in a
way that is not consistent with the real world.
79. The main concern with redundant relationships is that they remain across the model.