Answer the following questions based on the table Sales — CBSE Class 12 Informatics Practices 2024 PYQ

Question

Answer the following questions based on the table Salesman given below :

Table : Salesman

salesman_id	name	city	commission
5001	Neil Bhatt	Delhi	0.15
5002	Rohan Malik	Mumbai	0.13
5005	Ravi Mohan	Delhi	0.11
5006	Mehak Rai	Delhi	0.14
5007	Paul Lal	Bangalore	0.13
5003	Raman Sen	Kolkata	0.12

(i) How many tuples does the given table have ? (ii) Suggest the primary key for the given table. (iii) Write the MySQL query to display all the records in descending order of commission.

CBSECBSE Class XII Board 2024Subjective· 3mImportance★★★★★

🔒 Locked · start free trial →

You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.

Start your 14-day free trial to unlock the full solution →

Concept understanding — Primary Key Identification

Primary Key Identification

Think about how you tell two students apart in a classroom. If you call out "Rahul," there might be three Rahul's. But if you say "Rahul Sharma, roll number 12," you've pointed to exactly one person. That unique identifier — the roll number — is doing the job of a primary key.

The Everyday Intuition

Every collection of things needs a way to refer to each item without confusion. In a library, every book has a unique accession number. In a bank, every account has an account number. In a school, every student has a unique admission number. These are not random — they are deliberately chosen so that no two items share the same identifier.

This is the core idea: a primary key is a single attribute (or a combination of attributes) that uniquely identifies each record in a table. No two rows can have the same primary key value, and no primary key can be empty (null).

The Precise Meaning

In database terms, a primary key serves two non-negotiable rules:

Uniqueness — every value in the primary key column must be different from every other value. If you have 100 students, you need 100 distinct roll numbers.
Non-null — every record must have a primary key value. You cannot have a student with "no roll number."

A primary key can be a single column, like a student ID. Or it can be a composite key — two or more columns taken together to create uniqueness. For example, in a table recording which books students have borrowed, neither "Student ID" alone nor "Book ID" alone is unique (a student borrows many books; a book is borrowed by many students over time). But the combination of "Student ID + Book ID + Date Borrowed" together can be unique.

Important

A primary key is not just any unique column. It is the official, chosen identifier for that table. A table can have many columns that are unique (like Aadhaar number, PAN number, and email), but only one of them is designated as the primary key. The others are called candidate keys — they could have been the primary key, but weren't chosen.

Why It Matters

Without a primary key, you cannot reliably update or delete a specific record. Imagine a school database where two students have the same name "Ananya Sharma." If you try to delete "Ananya Sharma," the database has no way to know which one you mean. With a primary key, you say "delete student with roll number 45" — and it's unambiguous. …

Start your 14-day free trial to unlock the full solution →

A tuple in a database table refers to a single row or record. Counting the rows in the provided Salesman table shows there are six distinct tuples.
A primary key is a column (or set of columns) that uniquely identifies each row in a table. It must contain unique values for every record and cannot be null. In the Salesman table, salesman_id is the most suitable primary key because each ID is unique and non-null, ensuring every salesman record can be distinctly identified. Columns like name, city, or commission contain or could potentially contain duplicate values, making them unsuitable. …

Start your 14-day free trial to unlock the full solution →

The table has 6 tuples, salesman_id is the primary key, and the MySQL query to order by commission descending is SELECT * FROM Salesman ORDER BY commission DESC;.

Let's break down these questions by first understanding the fundamental concepts behind relational databases, which are crucial for working with tables like Salesman.

In a relational database, data is organized into tables, often called relations. Each table consists of rows and columns. Understanding the terminology is key to answering these questions accurately.

(i) How many tuples does the given table have?

The term 'tuple' in the context of relational databases refers to a single row in a table. Each tuple represents a complete record for a specific entity. For instance, in your Salesman table, each row provides all the information about one particular salesman: their ID, name, city, and commission rate.

To find the number of tuples, we simply count the number of rows present in the table.

Looking at the Salesman table:

salesman_id | name        | city      | commission
------------|-------------|-----------|-----------
5001        | Neil Bhatt  | Delhi     | 0.15
5002        | Rohan Malik | Mumbai    | 0.13
5005        | Ravi Mohan  | Delhi     | 0.11
5006        | Mehak Rai   | Delhi     | 0.14
5007        | Paul Lal    | Bangalore | 0.13
5003        | Raman Sen   | Kolkata   | 0.12

We can clearly see there are six distinct rows of data.

Note

A column in a database table is often referred to as an 'attribute', and a row is called a 'tuple'. The entire table is a 'relation'. This terminology comes from relational algebra, the theoretical foundation of relational databases.

Therefore, the table has 6 tuples.

(ii) Suggest the primary key for the given table.

A primary key is a fundamental concept in database design. It is a column, or a set of columns, that uniquely identifies each row in a table. This means two things:

Uniqueness: No two rows can have the same primary key value.
Non-nullability: A primary key column cannot contain null (empty) values.

The purpose of a primary key is to ensure data integrity and to provide a reliable way to reference individual records. When suggesting a primary key, we look for a column that inherently meets these criteria and is unlikely to change over time.

Let's examine the columns in the Salesman table:

salesman_id: The values are 5001, 5002, 5005, 5006, 5007, 5003. All these values are unique. It's also highly probable that every salesman will have a unique ID, and this ID will not be null. This is a strong candidate.
name: While "Neil Bhatt", "Rohan Malik", etc., are unique in this specific sample data, it's entirely possible in a real-world scenario for two different salesmen to have the same name (e.g., two "Ravi Mohan"s). Therefore, name is generally not a good choice for a primary key.
city: The values include "Delhi" multiple times. This column is clearly not unique.
commission: The value "0.13" appears twice. This column is also not unique.

Based on this analysis, salesman_id is the most suitable choice because it uniquely identifies each salesman and is designed to be distinct for every record. …

Start your 14-day free trial to unlock the full solution →

Same / Similar Concept — real previous-year questions on the same or a closely similar concept, not this exact question.

CBSE 2026Set 91/41 markMCQ
$Q. Assertion (A) : The PRIMARY KEY constraint in SQL ensures that each value in the column(s) is unique and cannot be NULL. Reason (R) : Candidate keys are not eligible to become a primary key. (A) Both Assertion (A) and Reason (R) are true and Reason (R) is the correct explanation for Assertion (A). (B) Both Assertion (A) and Reason (R) are true and Reason (R) is not the correct explanation for Assertion (A). (C) Assertion (A) is true, but Reason (R) is false. (D) Assertion (A) is false, but Reason (R) is true.$
›Reveal solutionSolution

Assertion (A) is correct—a PRIMARY KEY enforces uniqueness and disallows NULL values—but Reason (R) is false because candidate keys are precisely the keys eligible to become a primary key.

The assertion captures the essence of what a PRIMARY KEY constraint does in a relational database. When you designate a column (or a combination of columns) as the primary key of a table, the database management system enforces two iron rules: every value in that column must be unique across all rows, and no row may have a NULL value in that column. This dual guarantee—uniqueness plus mandatory presence—is what makes a primary key the definitive identifier for each record. Without it, you cannot reliably distinguish one row from another, and the entire relational model begins to crumble.

Now consider the reasoning offered. It claims that candidate keys are not eligible to become a primary key. This is precisely backwards. In database design, a candidate key is any column or set of columns that satisfies the two criteria above: it uniquely identifies each row, and it contains no NULL values. A table may have several candidate keys—employee ID, email address, and passport number might all uniquely identify a person—but you choose exactly one of these candidate keys to serve as the primary key. The others remain as alternate keys (sometimes called unique keys), still enforcing uniqueness but not bearing the special status of "primary." So candidate keys are not merely eligible to become the primary key; they are the only keys eligible for that role.

Important

A candidate key is defined as a minimal superkey—any attribute or combination of attributes that can uniquely identify a tuple and contains no NULL values. The primary key is simply the candidate key you select to be the principal identifier. …

Start your 14-day free trial to see the full solution →

(i) How many tuples does the given table have?

(ii) Suggest the primary key for the given table.

🎓Unlock everything free for 14 days

Unlock everything free for 14 days