WGU D427 Data Management – Applications OA
Actual Exam 2026/2027 | Questions 1-25 with Verified
Answers | 100% Correct | Pass Guaranteed
SECTION 1: Database Design & Normalization (8 Questions)
Q1 (Screenshot Description): A table screenshot shows:
● Table: CustomerOrders
● Columns: OrderID (PK), CustomerID, CustomerName, OrderDate, ProductID,
ProductName, Quantity, UnitPrice, CustomerEmail
● Sample Data: Multiple rows show same CustomerName with different
CustomerEmail values for same CustomerID.
What normalization problem is demonstrated?
A. No primary key
B. Transitive dependency (3NF violation)
C. Partial key dependency (2NF violation)
D. Repeating groups (1NF violation)
Correct Answer: B
Rationale: Competency D427.1.3: Apply normalization rules to eliminate data
anomalies.
Analysis: CustomerEmail depends on CustomerID (through CustomerName), creating a
transitive dependency: CustomerID → CustomerName → CustomerEmail. The primary
key OrderID determines CustomerID, but CustomerEmail is not directly dependent on the
key.
,Violation: Third Normal Form (3NF) requires that non-key attributes depend only on the
primary key, not on other non-key attributes.
Solution: Split into Customers table (CustomerID, CustomerName, CustomerEmail) and
Orders table (OrderID, CustomerID, OrderDate, etc.).
Business Impact: This causes update anomalies - changing email in one row doesn't
update all rows for same customer, leading to inconsistent data.
Why Distractors are Wrong:
● A: Table has a clear PK (OrderID)
● C: Partial dependency requires composite key; this is single-attribute PK
● D: Repeating groups are multi-valued attributes in single cell, not separate
columns
Q2 (Table Screenshot): A relation R(A, B, C, D) has functional dependencies: A → B, B →
C, C → D. What is the highest normal form this relation satisfies?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
Correct Answer: B
Rationale: Competency D427.1.2: Analyze functional dependencies and normal forms.
Step-by-Step Analysis:
1. Assume 1NF: All attributes contain atomic values (met by definition).
2. Primary Key: A is the only determinant that doesn't depend on others, making it
the PK.
3. 2NF Check: Since PK is single-attribute (A), there can be no partial dependencies
(where part of a composite key determines a non-key attribute). Therefore, 2NF is
satisfied.
4. 3NF Violation: 3NF prohibits transitive dependencies where a non-key attribute
depends on another non-key attribute. Here: A → B → C → D creates a chain
, where D (non-key) depends on C (non-key), violating 3NF. C also depends on B
(non-key), another violation.
5. BCNF: Cannot satisfy BCNF if 3NF is violated.
Business Impact: Storing this in one table causes insertion/deletion anomalies and
redundant data. For example, you cannot add a new product (C) until a customer orders
it (A).
Why Distractors are Wrong:
● A: Too low; relation meets 2NF requirements
● C: Violated by transitive dependency chain A→B→C→D
● D: Requires 3NF first; BCNF demands all determinants be superkeys
Q3 (Screenshot Description): An HR database table shows:
● Table: EmployeeProjects
● Columns: EmpID, EmpName, ProjectCode, ProjectName, Skills
● Sample Data Row 1: E001, John Smith, PRJ-A, Website Redesign,
"SQL,Python,HTML"
● Sample Data Row 2: E001, John Smith, PRJ-B, Database Migration,
"SQL,Python,HTML"
● Skills column contains multiple comma-separated values.
What is the primary normalization issue?
A. Repeating groups (1NF violation)
B. Partial dependency (2NF violation)
C. Transitive dependency (3NF violation)
D. No primary key defined
Correct Answer: A
Rationale: Competency D427.1.1: Apply First Normal Form principles.
Analysis: The Skills column contains multiple atomic values ("SQL,Python,HTML") in a
single cell, violating 1NF's requirement that each attribute contain only indivisible
values. This creates repeating groups - multiple values for one attribute in one tuple.
, Business Impact: Cannot query individual skills efficiently (requires string parsing).
Updating one skill requires reading/modifying entire string. Cannot create proper
indexes on skills.
Solution: Create separate EmployeeSkills junction table (EmpID, Skill) or store one skill
per row.
Why Distractors are Wrong:
● B: No partial dependency exists (no composite PK shown)
● C: Transitive dependency requires non-key → non-key; Skills depends on EmpID
directly
● D: Composite PK (EmpID, ProjectCode) could exist
Q4 (ER Diagram Screenshot): A diagram shows:
● Entities: Order, Product, Customer**
● Relationships: Order-to-Product (many-to-many, no associative entity),
Customer-to-Order (one-to-many)
● Attributes: Order has OrderID (PK) and OrderDate; Product has ProductID (PK)
and Price; Customer has CustomerID (PK)
What is the primary design flaw?
A. Missing primary keys
B. Missing associative entity for many-to-many relationship
C. Incorrect cardinality notation
D. Missing foreign key attributes
Correct Answer: B
Rationale: Competency D427.2.1: Design entity-relationship models accurately.
Analysis: In relational databases, many-to-many relationships cannot be implemented
directly - they require an associative/junction table (e.g., OrderDetail) to break it into two
one-to-many relationships. Without this, you cannot track which products belong to
which orders or store relationship-specific data like Quantity.
Actual Exam 2026/2027 | Questions 1-25 with Verified
Answers | 100% Correct | Pass Guaranteed
SECTION 1: Database Design & Normalization (8 Questions)
Q1 (Screenshot Description): A table screenshot shows:
● Table: CustomerOrders
● Columns: OrderID (PK), CustomerID, CustomerName, OrderDate, ProductID,
ProductName, Quantity, UnitPrice, CustomerEmail
● Sample Data: Multiple rows show same CustomerName with different
CustomerEmail values for same CustomerID.
What normalization problem is demonstrated?
A. No primary key
B. Transitive dependency (3NF violation)
C. Partial key dependency (2NF violation)
D. Repeating groups (1NF violation)
Correct Answer: B
Rationale: Competency D427.1.3: Apply normalization rules to eliminate data
anomalies.
Analysis: CustomerEmail depends on CustomerID (through CustomerName), creating a
transitive dependency: CustomerID → CustomerName → CustomerEmail. The primary
key OrderID determines CustomerID, but CustomerEmail is not directly dependent on the
key.
,Violation: Third Normal Form (3NF) requires that non-key attributes depend only on the
primary key, not on other non-key attributes.
Solution: Split into Customers table (CustomerID, CustomerName, CustomerEmail) and
Orders table (OrderID, CustomerID, OrderDate, etc.).
Business Impact: This causes update anomalies - changing email in one row doesn't
update all rows for same customer, leading to inconsistent data.
Why Distractors are Wrong:
● A: Table has a clear PK (OrderID)
● C: Partial dependency requires composite key; this is single-attribute PK
● D: Repeating groups are multi-valued attributes in single cell, not separate
columns
Q2 (Table Screenshot): A relation R(A, B, C, D) has functional dependencies: A → B, B →
C, C → D. What is the highest normal form this relation satisfies?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
Correct Answer: B
Rationale: Competency D427.1.2: Analyze functional dependencies and normal forms.
Step-by-Step Analysis:
1. Assume 1NF: All attributes contain atomic values (met by definition).
2. Primary Key: A is the only determinant that doesn't depend on others, making it
the PK.
3. 2NF Check: Since PK is single-attribute (A), there can be no partial dependencies
(where part of a composite key determines a non-key attribute). Therefore, 2NF is
satisfied.
4. 3NF Violation: 3NF prohibits transitive dependencies where a non-key attribute
depends on another non-key attribute. Here: A → B → C → D creates a chain
, where D (non-key) depends on C (non-key), violating 3NF. C also depends on B
(non-key), another violation.
5. BCNF: Cannot satisfy BCNF if 3NF is violated.
Business Impact: Storing this in one table causes insertion/deletion anomalies and
redundant data. For example, you cannot add a new product (C) until a customer orders
it (A).
Why Distractors are Wrong:
● A: Too low; relation meets 2NF requirements
● C: Violated by transitive dependency chain A→B→C→D
● D: Requires 3NF first; BCNF demands all determinants be superkeys
Q3 (Screenshot Description): An HR database table shows:
● Table: EmployeeProjects
● Columns: EmpID, EmpName, ProjectCode, ProjectName, Skills
● Sample Data Row 1: E001, John Smith, PRJ-A, Website Redesign,
"SQL,Python,HTML"
● Sample Data Row 2: E001, John Smith, PRJ-B, Database Migration,
"SQL,Python,HTML"
● Skills column contains multiple comma-separated values.
What is the primary normalization issue?
A. Repeating groups (1NF violation)
B. Partial dependency (2NF violation)
C. Transitive dependency (3NF violation)
D. No primary key defined
Correct Answer: A
Rationale: Competency D427.1.1: Apply First Normal Form principles.
Analysis: The Skills column contains multiple atomic values ("SQL,Python,HTML") in a
single cell, violating 1NF's requirement that each attribute contain only indivisible
values. This creates repeating groups - multiple values for one attribute in one tuple.
, Business Impact: Cannot query individual skills efficiently (requires string parsing).
Updating one skill requires reading/modifying entire string. Cannot create proper
indexes on skills.
Solution: Create separate EmployeeSkills junction table (EmpID, Skill) or store one skill
per row.
Why Distractors are Wrong:
● B: No partial dependency exists (no composite PK shown)
● C: Transitive dependency requires non-key → non-key; Skills depends on EmpID
directly
● D: Composite PK (EmpID, ProjectCode) could exist
Q4 (ER Diagram Screenshot): A diagram shows:
● Entities: Order, Product, Customer**
● Relationships: Order-to-Product (many-to-many, no associative entity),
Customer-to-Order (one-to-many)
● Attributes: Order has OrderID (PK) and OrderDate; Product has ProductID (PK)
and Price; Customer has CustomerID (PK)
What is the primary design flaw?
A. Missing primary keys
B. Missing associative entity for many-to-many relationship
C. Incorrect cardinality notation
D. Missing foreign key attributes
Correct Answer: B
Rationale: Competency D427.2.1: Design entity-relationship models accurately.
Analysis: In relational databases, many-to-many relationships cannot be implemented
directly - they require an associative/junction table (e.g., OrderDetail) to break it into two
one-to-many relationships. Without this, you cannot track which products belong to
which orders or store relationship-specific data like Quantity.
