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 the same CustomerID with different
CustomerEmail values for the same CustomerName.
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.
CustomerEmail depends on CustomerName (a non-key attribute), which in turn depends
on CustomerID. This creates a transitive dependency violating 3NF. The fix is to move
,CustomerName and CustomerEmail into a separate Customers table. Business impact:
update anomalies—changing a customer’s email in one row does not propagate to all
rows.
Q2 (ER Diagram Screenshot Description):
Screenshot shows an ER diagram with:
● Entity EMPLOYEE (EmpID PK, EmpName, DeptID FK, DeptName)
● Entity DEPARTMENT (DeptID PK, DeptName)
● Relationship: EMPLOYEE –belongs to– DEPARTMENT (1:N)
Which normal-form violation exists in the EMPLOYEE table?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
Correct Answer: B
Rationale: Competency D427.1.2 – Design normalized database structures.
EmpName depends on the whole PK (EmpID), so 2NF is satisfied for EmpName.
However, DeptName depends only on DeptID (a non-key attribute), creating a partial
dependency on the composite key if the table were redesigned with a composite PK. In
the current design the violation is actually transitive dependency (3NF) because
DeptName depends on DeptID, a non-key attribute.
Revised Correct Answer: C (3NF violation).
, Rationale: DeptName is stored redundantly in EMPLOYEE; it should be removed to
eliminate the transitive dependency EmpID → DeptID → DeptName.
Q3 (Table Screenshot):
Table BookAuthors with columns:
ISBN (PK), Title, Author1, Author2, Author3, Author4
Which normalization step should be applied first?
A. Achieve 2NF by removing partial dependencies
B. Achieve 1NF by removing repeating groups
C. Achieve 3NF by removing transitive dependencies
D. Achieve BCNF by removing anomalies
Correct Answer: B
Rationale: Competency D427.1.1 – Convert unnormalized data to 1NF.
The four Author columns are repeating groups—the same logical attribute (Author)
stored multiple times. Convert to 1NF by creating a separate Author table with (ISBN,
AuthorName) rows.
Q4 (Functional-Dependency List):
Given relation R(A,B,C,D,E) and FDs:
AB → C, C → D, D → E, E → A
What is the highest normal form satisfied?
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 the same CustomerID with different
CustomerEmail values for the same CustomerName.
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.
CustomerEmail depends on CustomerName (a non-key attribute), which in turn depends
on CustomerID. This creates a transitive dependency violating 3NF. The fix is to move
,CustomerName and CustomerEmail into a separate Customers table. Business impact:
update anomalies—changing a customer’s email in one row does not propagate to all
rows.
Q2 (ER Diagram Screenshot Description):
Screenshot shows an ER diagram with:
● Entity EMPLOYEE (EmpID PK, EmpName, DeptID FK, DeptName)
● Entity DEPARTMENT (DeptID PK, DeptName)
● Relationship: EMPLOYEE –belongs to– DEPARTMENT (1:N)
Which normal-form violation exists in the EMPLOYEE table?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
Correct Answer: B
Rationale: Competency D427.1.2 – Design normalized database structures.
EmpName depends on the whole PK (EmpID), so 2NF is satisfied for EmpName.
However, DeptName depends only on DeptID (a non-key attribute), creating a partial
dependency on the composite key if the table were redesigned with a composite PK. In
the current design the violation is actually transitive dependency (3NF) because
DeptName depends on DeptID, a non-key attribute.
Revised Correct Answer: C (3NF violation).
, Rationale: DeptName is stored redundantly in EMPLOYEE; it should be removed to
eliminate the transitive dependency EmpID → DeptID → DeptName.
Q3 (Table Screenshot):
Table BookAuthors with columns:
ISBN (PK), Title, Author1, Author2, Author3, Author4
Which normalization step should be applied first?
A. Achieve 2NF by removing partial dependencies
B. Achieve 1NF by removing repeating groups
C. Achieve 3NF by removing transitive dependencies
D. Achieve BCNF by removing anomalies
Correct Answer: B
Rationale: Competency D427.1.1 – Convert unnormalized data to 1NF.
The four Author columns are repeating groups—the same logical attribute (Author)
stored multiple times. Convert to 1NF by creating a separate Author table with (ISBN,
AuthorName) rows.
Q4 (Functional-Dependency List):
Given relation R(A,B,C,D,E) and FDs:
AB → C, C → D, D → E, E → A
What is the highest normal form satisfied?
