Denormalization MCQs in DBMS

1. 1. Primary purpose of normalization

(A) To increase data redundancy

(B) To reduce data redundancy

(C) To improve data consistency

(D) To increase data retrieval speed

2. 2. Normal form concerned with elimination of partial dependencies

(A) First Normal Form (1NF)

(B) Second Normal Form (2NF)

(C) Third Normal Form (3NF)

(D) Boyce-Codd Normal Form (BCNF)

3. 3. Normal form ensuring no transitive dependencies

(A) 1NF

(B) 2NF

(C) 3NF

(D) BCNF

4. 4. Transitive dependency

(A) A dependency between non-prime attributes

(B) A dependency between a non-prime attribute and a candidate key

(C) A dependency in which one attribute is functionally dependent on another through a third attribute

(D) A functional dependency that can be removed by splitting the table

5. 5. Normal form stricter than 3NF but not as strict as 4NF

(A) 2NF

(B) BCNF

(C) 1NF

(D) 5NF

6. 6. Requirement for First Normal Form (1NF)

(A) The table must have a primary key

(B) All attributes must depend on the whole primary key

(C) No repeating groups are allowed

(D) There should be no partial dependencies

7. 7. Condition for Boyce-Codd Normal Form (BCNF)

(A) It has no multi-valued dependencies

(B) It has no partial dependencies

(C) It has only one candidate key

(D) Every determinant is a candidate key

8. 8. Primary advantage of decomposing a database during normalization

(A) Improved data redundancy

(B) Simplified data retrieval

(C) Minimized update anomalies

(D) Increased complexity of queries

9. 9. Update anomaly

(A) An error caused by the accidental update of redundant data

(B) A situation where updates cannot be performed due to missing data

(C) An inconsistency caused by the accidental update of non-key attributes

(D) An issue that arises when a table contains redundant data

10. 10. Not a goal of normalization

(A) Eliminating redundant data

(B) Reducing data integrity issues

(C) Increasing data retrieval speed

(D) Organizing data efficiently