Difficulty: Easy
Correct Answer: Correct — this statement is valid for candidate keys
Explanation:
Introduction / Context:
In the relational model, keys and functional dependencies describe how attributes (columns) relate. A candidate key is central to design because it uniquely identifies tuples (rows). This question asks whether a candidate key can be described as a determinant for all other columns in the relation.
Given Data / Assumptions:
Concept / Approach:
A candidate key K is defined by two properties: uniqueness (K identifies each tuple) and minimality (no subset of K has the uniqueness property). Uniqueness in terms of dependencies means K → all attributes of R. Because K is minimal, removing any attribute from K breaks that determination. Therefore, calling a candidate key a “determinant of all other columns” is consistent with the formal definition.
Step-by-Step Solution:
Verification / Alternative check:
Consider a Student(roll_no, name, program) relation where roll_no uniquely identifies each student. Then roll_no → name, program, and roll_no is minimal. This matches the claim precisely.
Why Other Options Are Wrong:
Common Pitfalls:
Mixing up primary, candidate, and superkeys; forgetting the minimality part of the candidate key definition; assuming determination depends on normal form (it does not).
Final Answer:
Correct — this statement is valid for candidate keys
Discussion & Comments