Final answer:
Option D. is correct. In normalization, every non-primary key attribute depends upon the entire primary key, ensuring data integrity and preventing partial dependencies.
Step-by-step explanation:
The result of normalization is that every non-primary key attribute depends upon the whole primary key. Normalization is a process in database design that organizes data to reduce redundancy and improve data integrity. The usual aim is to ensure that data dependencies make sense (maintain data integrity) and to add, modify, and delete operations can be made in one place without affecting other data (maintain data non-redundancy). The correct answer to the question is:
In the context of relational database design, the term 'non-primary key attribute' refers to an attribute that is not part of any candidate key. According to normalization rules, specifically the Second Normal Form (2NF), every non-primary key attribute must be functionally dependent on the entire primary key and not just part of it. This ensures that all attributes are associated with the key uniquely identified to a record and not to portions of a composite primary key, thereby preventing partial dependencies and data anomalies.