We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
my thoughts:
the question is about elimination of options not aconfirmation.
since question itself says table is in 1nf or 2nf or 3nf then at least it is 1nf. now we have 2nf or 3nf to choose from.
since city determines zipcode. according to functional dependency condition. and since we know that there are other attribute about whom which we not know then we can say for sure that zipcode is not a prime attribute. this removes the partiaal dependency problem. so it is in 2nf form. this leaves 3nf since city is not a pk and we are only left with 3nf to eliminate it mean our answer is 3nf
Cookie support is required to access HackerRank
Seems like cookies are disabled on this browser, please enable them to open this website
Database Normalization #2 - 1/2/3 NF
You are viewing a single comment's thread. Return to all comments →
my thoughts: the question is about elimination of options not aconfirmation. since question itself says table is in 1nf or 2nf or 3nf then at least it is 1nf. now we have 2nf or 3nf to choose from. since city determines zipcode. according to functional dependency condition. and since we know that there are other attribute about whom which we not know then we can say for sure that zipcode is not a prime attribute. this removes the partiaal dependency problem. so it is in 2nf form. this leaves 3nf since city is not a pk and we are only left with 3nf to eliminate it mean our answer is 3nf