3NF requires separating data so non-key columns do not depend on other non-key columns. CustomerName depends on CustomerID, so it should be in a separate table.
Step 2: Analyze options
CREATE TABLE Orders (OrderID INT PRIMARY KEY, CustomerID INT); CREATE TABLE Customers (CustomerID INT PRIMARY KEY, CustomerName VARCHAR(50)); splits Orders and Customers, following 3NF. CREATE TABLE Orders (OrderID INT PRIMARY KEY, CustomerID INT, CustomerName VARCHAR(50)); stores CustomerName in Orders, violating 3NF. The other options miss primary keys or mix data improperly.
Final Answer:
CREATE TABLE Orders (OrderID INT PRIMARY KEY, CustomerID INT); CREATE TABLE Customers (CustomerID INT PRIMARY KEY, CustomerName VARCHAR(50)); -> Option C
Quick Check:
Separate related data into tables = 3NF [OK]
Quick Trick:Split tables to avoid non-key dependencies [OK]
Common Mistakes:
Putting dependent data in the same table
Missing primary keys
Ignoring data duplication issues
Master "Database Design and Normalization" in SQL
9 interactive learning modes - each teaches the same concept differently