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):
The screenshot shows a single table named EmployeeProjects:
● Columns: EmpID (PK), EmpName, DeptID, DeptName, ProjectID, ProjectName,
HoursWorked
● Sample Data: EmpID 101 appears 3 rows; each row has identical EmpName &
DeptName but different ProjectID.
Which normal-form violation is demonstrated?
A. Repeating groups (1NF)
B. Partial dependency (2NF)
C. Transitive dependency (3NF)
D. No violation; table is BCNF
Correct Answer: B
Rationale: Competency D427.1.2 – Design normalized database structures.
● The composite candidate key would be (EmpID, ProjectID).
● Non-key attribute DeptName depends only on DeptID, which is part of the key (via
EmpID → DeptID), not the whole key → partial dependency → violates 2NF.
● Fix: split into Employees(EmpID, EmpName, DeptID), Departments(DeptID,
DeptName), and ProjectHours(EmpID, ProjectID, HoursWorked).
, ● Business impact: update anomalies—changing a department name requires
multiple row updates.
Q2 (ER-Diagram Screenshot Description):
A crow’s-foot ER diagram shows:
● Entity A ──< Entity B (>—| indicates many-to-one)
● Entity B ──< Entity C
● Entity C ──< Entity A (many side pointing back to A)
Which rule has been broken?
A. No direct many-to-many
B. Referential integrity
C. Entity integrity
D. No error; diagram is valid
Correct Answer: A
Rationale: Competency D427.1.1 – Interpret ER diagrams.
● The combination creates a circular many-to-one chain that hides a logical
many-to-many between A and C.
● WGU modeling standard requires explicit associative entity when cardinality is
many-to-many; here the designer left it implicit.
● Resolution: introduce associative entity between A and C with foreign keys to
both.
Q3 (Table Screenshot):
Table Sales: OrderID, ProductID, Quantity, UnitPrice, ExtendedPrice (computed as
Quantity*UnitPrice).
, ExtendedPrice is stored in the table. Which normal form is violated?
A. 1NF
B. 2NF
C. 3NF
D. None; computed columns are allowed
Correct Answer: C
Rationale: Competency D427.1.3 – Eliminate redundant data.
● ExtendedPrice is derivable from two non-key attributes → introduces transitive
dependency (OrderID → Quantity,UnitPrice → ExtendedPrice).
● 3NF demands no non-key attribute depend on anything except the key.
● Best practice: remove column and compute in queries/views to guarantee
consistency.
Q4 (FD List Screenshot):
Relation R(A,B,C,D,E) with functional dependencies:
AB→C, C→D, D→E, E→A.
What is the highest normal form satisfied?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
Actual Exam 2026/2027 | Questions 1-25 with
Verified Answers | 100% Correct | Pass Guaranteed
SECTION 1: Database Design & Normalization (8 Questions)
Q1 (Screenshot Description):
The screenshot shows a single table named EmployeeProjects:
● Columns: EmpID (PK), EmpName, DeptID, DeptName, ProjectID, ProjectName,
HoursWorked
● Sample Data: EmpID 101 appears 3 rows; each row has identical EmpName &
DeptName but different ProjectID.
Which normal-form violation is demonstrated?
A. Repeating groups (1NF)
B. Partial dependency (2NF)
C. Transitive dependency (3NF)
D. No violation; table is BCNF
Correct Answer: B
Rationale: Competency D427.1.2 – Design normalized database structures.
● The composite candidate key would be (EmpID, ProjectID).
● Non-key attribute DeptName depends only on DeptID, which is part of the key (via
EmpID → DeptID), not the whole key → partial dependency → violates 2NF.
● Fix: split into Employees(EmpID, EmpName, DeptID), Departments(DeptID,
DeptName), and ProjectHours(EmpID, ProjectID, HoursWorked).
, ● Business impact: update anomalies—changing a department name requires
multiple row updates.
Q2 (ER-Diagram Screenshot Description):
A crow’s-foot ER diagram shows:
● Entity A ──< Entity B (>—| indicates many-to-one)
● Entity B ──< Entity C
● Entity C ──< Entity A (many side pointing back to A)
Which rule has been broken?
A. No direct many-to-many
B. Referential integrity
C. Entity integrity
D. No error; diagram is valid
Correct Answer: A
Rationale: Competency D427.1.1 – Interpret ER diagrams.
● The combination creates a circular many-to-one chain that hides a logical
many-to-many between A and C.
● WGU modeling standard requires explicit associative entity when cardinality is
many-to-many; here the designer left it implicit.
● Resolution: introduce associative entity between A and C with foreign keys to
both.
Q3 (Table Screenshot):
Table Sales: OrderID, ProductID, Quantity, UnitPrice, ExtendedPrice (computed as
Quantity*UnitPrice).
, ExtendedPrice is stored in the table. Which normal form is violated?
A. 1NF
B. 2NF
C. 3NF
D. None; computed columns are allowed
Correct Answer: C
Rationale: Competency D427.1.3 – Eliminate redundant data.
● ExtendedPrice is derivable from two non-key attributes → introduces transitive
dependency (OrderID → Quantity,UnitPrice → ExtendedPrice).
● 3NF demands no non-key attribute depend on anything except the key.
● Best practice: remove column and compute in queries/views to guarantee
consistency.
Q4 (FD List Screenshot):
Relation R(A,B,C,D,E) with functional dependencies:
AB→C, C→D, D→E, E→A.
What is the highest normal form satisfied?
A. 1NF
B. 2NF
C. 3NF
D. BCNF
