2. Which of the following is the correct way to describe a primary key in a table?
easy
A. A column or set of columns that uniquely identifies each row
B. A column that stores only numbers
C. A column that can have duplicate values
D. A column used to sort the table
Solution
Step 1: Recall the role of a primary key
A primary key uniquely identifies each record in a table, so no two rows share the same primary key value.
Step 2: Check the options
Only A column or set of columns that uniquely identifies each row describes uniqueness and identification, others describe unrelated properties.
Final Answer:
A column or set of columns that uniquely identifies each row -> Option A
Quick Check:
Primary key = unique identifier [OK]
Hint: Primary key means unique row ID [OK]
Common Mistakes:
Thinking primary key allows duplicates
Confusing primary key with sorting or data type
Assuming primary key is always numeric
3. Given a table Employees with columns EmpID (primary key), Name, and Department, what will the following SQL query return?
SELECT Name FROM Employees WHERE Department = 'Sales';
medium
A. Only employees with no department assigned
B. All employee names regardless of department
C. All employee names who work in the Sales department
D. An error because Department is not a primary key
Solution
Step 1: Understand the SELECT and WHERE clauses
The query selects the Name column from Employees where Department equals 'Sales'.
Step 2: Determine the output
It returns all employee names whose Department is exactly 'Sales'. It does not return others or cause errors.
Final Answer:
All employee names who work in the Sales department -> Option C
Quick Check:
WHERE filters rows, SELECT chooses columns [OK]
Hint: WHERE filters rows; SELECT picks columns [OK]
Common Mistakes:
Thinking it returns all employees ignoring WHERE
Assuming Department must be primary key to filter
Expecting error due to non-primary key in WHERE
4. Consider this SQL snippet:
CREATE TABLE Products (ProductID INT, Name VARCHAR(50), Price DECIMAL); ALTER TABLE Products ADD PRIMARY KEY (ProductID); INSERT INTO Products VALUES (1, 'Pen', 1.5), (1, 'Pencil', 0.5);
What is the problem with this code?
medium
A. Price column cannot be DECIMAL
B. It tries to insert duplicate primary key values
C. The primary key is not defined correctly
D. The table has no columns
Solution
Step 1: Check primary key uniqueness
Primary key ProductID must be unique. The insert tries to add two rows with ProductID = 1.
Step 2: Identify the error cause
Inserting duplicate primary keys violates uniqueness, causing an error.
Final Answer:
It tries to insert duplicate primary key values -> Option B
Quick Check:
Primary key must be unique [OK]
Hint: Primary keys cannot repeat values [OK]
Common Mistakes:
Ignoring duplicate key violation
Thinking DECIMAL is invalid for Price
Assuming primary key syntax is wrong
5. You have two tables: Orders(OrderID, CustomerID, Amount) and Customers(CustomerID, Name). Which relational model concept explains why CustomerID appears in both tables?
hard
A. Column aliasing to rename data
B. Primary key duplication for faster queries
C. Data redundancy to store copies
D. Foreign key linking related records between tables
Solution
Step 1: Understand the role of CustomerID in both tables
CustomerID uniquely identifies customers in Customers and links orders to customers in Orders.
Step 2: Identify relational model concept
This linking is done by a foreign key, which references the primary key in another table to connect related data.
Final Answer:
Foreign key linking related records between tables -> Option D
Quick Check:
Foreign key = link between tables [OK]
Hint: Foreign key connects tables via shared column [OK]
Common Mistakes:
Confusing foreign key with primary key duplication
Thinking it's just data redundancy
Mixing foreign key with column aliasing
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.