Solution:Step 1: Identify primary keyThe primary key is composite: (StudentID, ClassID).Step 2: Check dependenciesStudentEmail depends only on StudentID, a part of the composite key, causing partial dependency.Final Answer:StudentEmail causes a partial dependency violating 2NF. -> Option BQuick Chec

[Solved] Analyze the table:CREATE TABLE Registration (StudentID INT, ClassID INT, StudentEmail VARCHAR(100), PRIMARY KEY (StudentID, ClassID));StudentEmail depends only... What is the issue related to 2NF? | SQL

SQL - Database Design and Normalization

Analyze the table:
CREATE TABLE Registration (StudentID INT, ClassID INT, StudentEmail VARCHAR(100), PRIMARY KEY (StudentID, ClassID));
StudentEmail depends only on StudentID. What is the issue related to 2NF?

APrimary key is not defined correctly.

BStudentEmail causes a partial dependency violating 2NF.

CStudentEmail depends on both StudentID and ClassID.

DThere is no violation; table is in 2NF.

Step-by-Step Solution

Solution:

Step 1: Identify primary key
The primary key is composite: (StudentID, ClassID).
Step 2: Check dependencies
StudentEmail depends only on StudentID, a part of the composite key, causing partial dependency.
Final Answer:
StudentEmail causes a partial dependency violating 2NF. -> Option B
Quick Check:
Partial dependency on StudentEmail found [OK]

Quick Trick: Partial dependency on composite key attribute breaks 2NF [OK]

Common Mistakes:

Assuming single attribute dependencies are allowed
Ignoring composite key structure
Confusing 2NF with 3NF

Master "Database Design and Normalization" in SQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More SQL Quizzes

Analyze the table:

Step 1: Identify primary key

Step 2: Check dependencies

Final Answer:

Quick Check:

Want More Practice?