Database Systems 6th Edition by Thomas Connolly |
Design, Implementation & Management | 2026/2027
Study Guide - 300 UNIQUE QUESTIONS x 300 UNIQUE
DESIGNS (Original Content)
DOMAIN 1: DATABASE CONCEPTS & ARCHITECTURE & ER
MODELING (60 Q)
Question 1 [Design-2]
Scenario Q1: DB Concept 1: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
A. emp_id candidate key, B. All superkeys primary
composite superkey, choose
minimal candidate as primary
C. No key D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
Question 2 [Design-3]
SATA Q2: DB Concept 2: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
■ A. Specialization/Generalization
■ B. Aggregation
■ C. Composition
■ D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
,Question 3 [Design-4]
Architecture Q3: ANSI-SPARC 3-level for DB Concept 3: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual community logical, Internal physical storage
B. Only external
C. Only internal
D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
Question 4 [Design-5]
ER Modeling Q4: DB Concept 4: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - A university has Students enroll in
many Courses, each Course has many Students. What cardinality and participation?
Student --< Enrolls >-- Course
Cardinality: M:N, Participation: Optional both sides
A. Many-to-Many with associative B. One-to-One
entity Enrollment
C. One-to-Many only D. No relationship
Answer: A - Many-to-Many with associative entity Enrollment
Rationale: M:N requires junction table. Participation: total = must participate, partial = optional. ER to
relational: entity becomes table, M:N becomes new table with FKs.
Question 5 [Design-6]
Scenario Q5: DB Concept 5: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
■ A. emp_id candidate key, composite superkey, choose minimal candidate as
primary
■ B. All superkeys primary
■ C. No key
■ D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
,Question 6 [Design-7]
SATA Q6: DB Concept 6: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
A. Specialization/Generalization
B. Aggregation
C. Composition
D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
Question 7 [Design-8]
Architecture Q7: ANSI-SPARC 3-level for DB Concept 7: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual B. Only external
community logical, Internal physical
storage
C. Only internal D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
Question 8 [Design-9]
ER Modeling Q8: DB Concept 8: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - A university has Students enroll in
many Courses, each Course has many Students. What cardinality and participation?
Student --< Enrolls >-- Course
Cardinality: M:N, Participation: Optional both sides
■ A. Many-to-Many with associative entity Enrollment
■ B. One-to-One
■ C. One-to-Many only
■ D. No relationship
Answer: A - Many-to-Many with associative entity Enrollment
Rationale: M:N requires junction table. Participation: total = must participate, partial = optional. ER to
relational: entity becomes table, M:N becomes new table with FKs.
, Question 9 [Design-10]
Scenario Q9: DB Concept 9: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
A. emp_id candidate key, composite superkey, choose minimal candidate as primary
B. All superkeys primary
C. No key
D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
Question 10 [Design-11]
SATA Q10: DB Concept 10: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
A. Specialization/Generalization
B. Aggregation
C. Composition
D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
Question 11 [Design-12]
Architecture Q11: ANSI-SPARC 3-level for DB Concept 11: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual B. Only external
community logical, Internal physical
storage
C. Only internal D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
Design, Implementation & Management | 2026/2027
Study Guide - 300 UNIQUE QUESTIONS x 300 UNIQUE
DESIGNS (Original Content)
DOMAIN 1: DATABASE CONCEPTS & ARCHITECTURE & ER
MODELING (60 Q)
Question 1 [Design-2]
Scenario Q1: DB Concept 1: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
A. emp_id candidate key, B. All superkeys primary
composite superkey, choose
minimal candidate as primary
C. No key D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
Question 2 [Design-3]
SATA Q2: DB Concept 2: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
■ A. Specialization/Generalization
■ B. Aggregation
■ C. Composition
■ D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
,Question 3 [Design-4]
Architecture Q3: ANSI-SPARC 3-level for DB Concept 3: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual community logical, Internal physical storage
B. Only external
C. Only internal
D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
Question 4 [Design-5]
ER Modeling Q4: DB Concept 4: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - A university has Students enroll in
many Courses, each Course has many Students. What cardinality and participation?
Student --< Enrolls >-- Course
Cardinality: M:N, Participation: Optional both sides
A. Many-to-Many with associative B. One-to-One
entity Enrollment
C. One-to-Many only D. No relationship
Answer: A - Many-to-Many with associative entity Enrollment
Rationale: M:N requires junction table. Participation: total = must participate, partial = optional. ER to
relational: entity becomes table, M:N becomes new table with FKs.
Question 5 [Design-6]
Scenario Q5: DB Concept 5: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
■ A. emp_id candidate key, composite superkey, choose minimal candidate as
primary
■ B. All superkeys primary
■ C. No key
■ D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
,Question 6 [Design-7]
SATA Q6: DB Concept 6: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
A. Specialization/Generalization
B. Aggregation
C. Composition
D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
Question 7 [Design-8]
Architecture Q7: ANSI-SPARC 3-level for DB Concept 7: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual B. Only external
community logical, Internal physical
storage
C. Only internal D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
Question 8 [Design-9]
ER Modeling Q8: DB Concept 8: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - A university has Students enroll in
many Courses, each Course has many Students. What cardinality and participation?
Student --< Enrolls >-- Course
Cardinality: M:N, Participation: Optional both sides
■ A. Many-to-Many with associative entity Enrollment
■ B. One-to-One
■ C. One-to-Many only
■ D. No relationship
Answer: A - Many-to-Many with associative entity Enrollment
Rationale: M:N requires junction table. Participation: total = must participate, partial = optional. ER to
relational: entity becomes table, M:N becomes new table with FKs.
, Question 9 [Design-10]
Scenario Q9: DB Concept 9: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Identify primary key vs composite key
Employee(emp_id, dept_id, name) - emp_id unique, (emp_id, dept_id) also unique
A. emp_id candidate key, composite superkey, choose minimal candidate as primary
B. All superkeys primary
C. No key
D. Only composite
Answer: A - emp_id candidate key, composite superkey, choose minimal
candidate as primary
Rationale: Superkey any set uniquely identifies, candidate minimal superkey, primary chosen
candidate, alternate remaining candidates, composite = multiple columns.
Question 10 [Design-11]
SATA Q10: DB Concept 10: ER modeling, entities, relationships, attributes, cardinality,
participation, enhanced ER, architecture ANSI-SPARC - Which are enhanced ER concepts?
A. Specialization/Generalization
B. Aggregation
C. Composition
D. Simple attribute
Answer: A, B, C - Specialization/Generalization
Rationale: Enhanced ER: specialization (top-down), generalization (bottom-up), aggregation
(relationship as entity), composition, inheritance, union type.
Question 11 [Design-12]
Architecture Q11: ANSI-SPARC 3-level for DB Concept 11: ER modeling, entities, relationships,
attributes, cardinality, participation, enhanced ER, architecture ANSI-SPARC
External -> Conceptual -> Internal
A. External user views, Conceptual B. Only external
community logical, Internal physical
storage
C. Only internal D. No levels
Answer: A - External user views, Conceptual community logical, Internal
physical storage
Rationale: ANSI-SPARC: external multiple user views, conceptual unified logical, internal physical.
Provides data independence: logical and physical.
