WGU C706 Data
Management Applications –
2025/2026 Verified Correct
Answers
Section 1: Relational Database Concepts (Questions 1-20)
1. In a relational database, what does the term "relation" refer to? A. A connection between
servers B. A table representing entities and attributes C. A type of SQL query D. A
backup procedure
B. A table representing entities and attributes
Rationale: In relational model (Codd's rules), a relation is a table with rows (tuples/records) and
columns (attributes), ensuring data integrity via keys. This foundational concept supports
normalization and querying in C706, distinguishing from non-relational NoSQL.
2. Which relational integrity rule ensures that a foreign key value must match a primary key
in another table or be null? A. Entity integrity B. Referential integrity C. Domain
integrity D. User-defined integrity
B. Referential integrity
Rationale: Referential integrity prevents orphan records by enforcing relationships (e.g., Order
table's CustomerID must exist in Customers primary key). C706 emphasizes this for ERD design
to maintain data consistency.
3. The process of organizing data to minimize redundancy and dependency is called: A.
Denormalization B. Normalization C. Indexing D. Partitioning
B. Normalization
Rationale: Normalization (1NF-5NF) eliminates anomalies (insertion/deletion/update) by
structuring tables; e.g., 1NF removes repeating groups. Core C706 topic for efficient relational
design.
4. In relational databases, a primary key must be: A. Optional B. Unique and not null C.
Composite only D. Foreign to another table
, B. Unique and not null
Rationale: Primary key uniquely identifies tuples (e.g., StudentID); not null ensures no blanks,
enforcing entity integrity per C706 relational rules.
5. A many-to-many relationship between entities is resolved using: A. A direct link B. A
junction/associative table C. Denormalization D. No resolution needed
B. A junction/associative table
Rationale: Junction table (e.g., StudentCourses with StudentID, CourseID as composite PK)
breaks many-to-many into two one-to-many; essential in ERD modeling for C706.
6. Which normal form eliminates partial dependencies on composite keys? A. 1NF B. 2NF
C. 3NF D. BCNF
B. 2NF
Rationale: 2NF requires full functional dependency (non-key attributes depend on whole key);
e.g., split OrderDetails if ItemName depends only on ItemID, preventing update anomalies in
C706 normalization exercises.
7. Domain integrity is enforced by: A. Foreign keys B. Check constraints on data
types/ranges C. Indexes D. Triggers
B. Check constraints on data types/ranges
Rationale: Domain integrity ensures valid entries (e.g., Age BETWEEN 0 AND 120); C706
covers as part of data validation in schema design.
8. In an ERD, cardinality notation 1:M means: A. One-to-one B. One-to-many C. Many-to-
many D. Optional many
B. One-to-many
Rationale: Crow's foot: Single line (1) to crow's foot (M); e.g., one Department has many
Employees, guiding relational schema in C706 modeling.
9. A candidate key is: A. Always the primary key B. Any attribute that uniquely identifies a
tuple C. A foreign key D. An index
B. Any attribute that uniquely identifies a tuple
Rationale: Candidate keys (e.g., Email or SSN for User) qualify for primary; C706 stresses
selection for minimal superkey.
Management Applications –
2025/2026 Verified Correct
Answers
Section 1: Relational Database Concepts (Questions 1-20)
1. In a relational database, what does the term "relation" refer to? A. A connection between
servers B. A table representing entities and attributes C. A type of SQL query D. A
backup procedure
B. A table representing entities and attributes
Rationale: In relational model (Codd's rules), a relation is a table with rows (tuples/records) and
columns (attributes), ensuring data integrity via keys. This foundational concept supports
normalization and querying in C706, distinguishing from non-relational NoSQL.
2. Which relational integrity rule ensures that a foreign key value must match a primary key
in another table or be null? A. Entity integrity B. Referential integrity C. Domain
integrity D. User-defined integrity
B. Referential integrity
Rationale: Referential integrity prevents orphan records by enforcing relationships (e.g., Order
table's CustomerID must exist in Customers primary key). C706 emphasizes this for ERD design
to maintain data consistency.
3. The process of organizing data to minimize redundancy and dependency is called: A.
Denormalization B. Normalization C. Indexing D. Partitioning
B. Normalization
Rationale: Normalization (1NF-5NF) eliminates anomalies (insertion/deletion/update) by
structuring tables; e.g., 1NF removes repeating groups. Core C706 topic for efficient relational
design.
4. In relational databases, a primary key must be: A. Optional B. Unique and not null C.
Composite only D. Foreign to another table
, B. Unique and not null
Rationale: Primary key uniquely identifies tuples (e.g., StudentID); not null ensures no blanks,
enforcing entity integrity per C706 relational rules.
5. A many-to-many relationship between entities is resolved using: A. A direct link B. A
junction/associative table C. Denormalization D. No resolution needed
B. A junction/associative table
Rationale: Junction table (e.g., StudentCourses with StudentID, CourseID as composite PK)
breaks many-to-many into two one-to-many; essential in ERD modeling for C706.
6. Which normal form eliminates partial dependencies on composite keys? A. 1NF B. 2NF
C. 3NF D. BCNF
B. 2NF
Rationale: 2NF requires full functional dependency (non-key attributes depend on whole key);
e.g., split OrderDetails if ItemName depends only on ItemID, preventing update anomalies in
C706 normalization exercises.
7. Domain integrity is enforced by: A. Foreign keys B. Check constraints on data
types/ranges C. Indexes D. Triggers
B. Check constraints on data types/ranges
Rationale: Domain integrity ensures valid entries (e.g., Age BETWEEN 0 AND 120); C706
covers as part of data validation in schema design.
8. In an ERD, cardinality notation 1:M means: A. One-to-one B. One-to-many C. Many-to-
many D. Optional many
B. One-to-many
Rationale: Crow's foot: Single line (1) to crow's foot (M); e.g., one Department has many
Employees, guiding relational schema in C706 modeling.
9. A candidate key is: A. Always the primary key B. Any attribute that uniquely identifies a
tuple C. A foreign key D. An index
B. Any attribute that uniquely identifies a tuple
Rationale: Candidate keys (e.g., Email or SSN for User) qualify for primary; C706 stresses
selection for minimal superkey.
