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: SalesTransactions
● Columns: TransactionID (PK), CustomerID, CustomerName, CustomerCity,
ProductID, ProductName, Quantity, UnitPrice
● Sample Data: Multiple rows show the same CustomerID with different
CustomerCity values (e.g., CustomerID 101 appears with “Chicago” and “New
York”).
What normalization problem is demonstrated?
A. Repeating groups (1NF violation)
B. Partial key dependency (2NF violation)
C. Transitive dependency (3NF violation)
D. No primary key
Correct Answer: C
Rationale: Competency D427.1.3: Apply normalization rules to eliminate data
anomalies.
,CustomerCity depends on CustomerID (non-key → non-key), creating a transitive
dependency: TransactionID → CustomerID → CustomerCity.
Violation: 3NF requires non-key attributes depend only on the whole key.
Business Impact: Update anomaly—changing a customer’s city in one row leaves other
rows inconsistent.
Distractors: A) No repeating groups visible; B) PK is single column; D) PK is present.
Q2 (ER-Diagram Screenshot Description):
Screenshot displays an ER diagram with two entities:
● Employee (EmpID, Name, DeptID)
● Department (DeptID, DeptName, Location)
Relationship line shows a double line on Department side and single line on
Employee side, labeled “Works-in”.
What cardinality is depicted?
A. One-to-one
B. Many-to-one (Employee to Department)
C. Many-to-many
D. One-to-many (Department to Employee)
Correct Answer: B
Rationale: Competency D427.1.1: Interpret ER notation.
Double line = total participation; single line = partial. Direction of relationship reads:
Many Employees may work in one Department.
, Business Impact: Ensures every employee is assigned to exactly one department, but a
department can have zero or many employees.
Q3 (Table Screenshot):
Table: ProjectAssignments
ProjectID | EmployeeID | EmployeeName | Role | HourlyRate
100 | 201 | Alice | Dev | 75
100 | 201 | Alice | Test | 80
Which normal form is violated?
A. 1NF
B. 2NF
C. 3NF
D. None
Correct Answer: B
Rationale: Competency D427.1.2: Identify partial key dependencies.
Composite PK (ProjectID, EmployeeID). EmployeeName and HourlyRate depend only on
EmployeeID, not on the full PK → partial dependency, violating 2NF.
Solution: Move EmployeeName & HourlyRate to Employees table.
Q4 (FD List Screenshot):
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: SalesTransactions
● Columns: TransactionID (PK), CustomerID, CustomerName, CustomerCity,
ProductID, ProductName, Quantity, UnitPrice
● Sample Data: Multiple rows show the same CustomerID with different
CustomerCity values (e.g., CustomerID 101 appears with “Chicago” and “New
York”).
What normalization problem is demonstrated?
A. Repeating groups (1NF violation)
B. Partial key dependency (2NF violation)
C. Transitive dependency (3NF violation)
D. No primary key
Correct Answer: C
Rationale: Competency D427.1.3: Apply normalization rules to eliminate data
anomalies.
,CustomerCity depends on CustomerID (non-key → non-key), creating a transitive
dependency: TransactionID → CustomerID → CustomerCity.
Violation: 3NF requires non-key attributes depend only on the whole key.
Business Impact: Update anomaly—changing a customer’s city in one row leaves other
rows inconsistent.
Distractors: A) No repeating groups visible; B) PK is single column; D) PK is present.
Q2 (ER-Diagram Screenshot Description):
Screenshot displays an ER diagram with two entities:
● Employee (EmpID, Name, DeptID)
● Department (DeptID, DeptName, Location)
Relationship line shows a double line on Department side and single line on
Employee side, labeled “Works-in”.
What cardinality is depicted?
A. One-to-one
B. Many-to-one (Employee to Department)
C. Many-to-many
D. One-to-many (Department to Employee)
Correct Answer: B
Rationale: Competency D427.1.1: Interpret ER notation.
Double line = total participation; single line = partial. Direction of relationship reads:
Many Employees may work in one Department.
, Business Impact: Ensures every employee is assigned to exactly one department, but a
department can have zero or many employees.
Q3 (Table Screenshot):
Table: ProjectAssignments
ProjectID | EmployeeID | EmployeeName | Role | HourlyRate
100 | 201 | Alice | Dev | 75
100 | 201 | Alice | Test | 80
Which normal form is violated?
A. 1NF
B. 2NF
C. 3NF
D. None
Correct Answer: B
Rationale: Competency D427.1.2: Identify partial key dependencies.
Composite PK (ProjectID, EmployeeID). EmployeeName and HourlyRate depend only on
EmployeeID, not on the full PK → partial dependency, violating 2NF.
Solution: Move EmployeeName & HourlyRate to Employees table.
Q4 (FD List Screenshot):
