✔ Scroll down and test yourself — answers are hidden under the “View Answer” button.
Attempt all questions first.
✔️ Click SUBMIT at the end to unlock VIEW ANSWER buttons.
Explanation:
5NF (Projection-Join NF) addresses join dependencies — a relation is in 5NF when it cannot be non-trivially decomposed into smaller relations without loss.
Explanation:
BCNF ensures lossless decomposition, but it may break dependency preservation — some FDs might not be enforceable without joins.
Explanation:
If there are no partial dependencies and no transitive dependencies, the relation is at least in 3NF.
Explanation:
Transitive dependencies cause redundancy and can result in insertion, deletion and update anomalies — so all of these.
Explanation:
OrderID → CustomerID and CustomerID → CustomerPhone creates a transitive dependency OrderID → CustomerPhone via CustomerID. This violates 3NF.
Explanation:
Two independent sets of attributes cause multivalued dependency. A non-trivial MVD suggests need for 4NF decomposition.
Explanation:
BCNF handles functional dependencies. MVDs are a different redundancy source, handled only in 4NF.
Explanation:
A table in 2NF must first be in 1NF and then remove partial dependencies on composite keys.
Explanation:
3NF eliminates transitive dependencies where non-key determines non-key.
Explanation:
D → A and A → BC implies D → ABC. With D itself present, it determines all — so D is a key.