Question

QUESTION 4

1. Which of the two choices below are the reasons why the relation below is not BCNF.

   in_dep (ID, name, salary, dept_name, building, budget )

   with a functional dependency dept_name --> building, budget

   		dept_name is not a superkey
   		dept_name --> building, budget is not a trivial dependency
   		id --> name, salary, dept_name is also a functional dependency
   		It is not 3NF

QUESTION 5

1. in_dep (ID, name, salary, dept_name, building, budget )

   Choose the following decompositions of in_dep into BCNF when

   dept_name->building, budget  causes a violation of BCNF.

   		id, name, salary, dept_name
   		id, name, salary
   		dept_name, building, budget
   		salary, dept_name, budget

QUESTION 6

1. List the advantages of 3NF over BCNF

   		Can always preserve functional dependencies
   		Ensures no losslessness
   		It's a subset of BCNF
   		It's stricter

Answer 1

Question 1) Answer Option B and D

Reason: Option A is correct because dept_name is a superkey and in order to be in BCNF the first element should be a superkey

Option B is incorrect because building and budget is a trivial dependency and it should not be there

Option C is correct because the given values are functional dependency

Option D is incorrect because it cannot be in BCNF. Since it is not in 3NF

question 2) Answer Option D

Reason: Option D is correct and all the option are wrong because salary, dept_name and budget if there are any violation in BCNF then the following given data will be decomposed into these values only.

Question 3) Option A

Reason: Option A is correct because 3NF can always preserve functional dependency

Option B is incorrect because it ensures loselessness

Option C is incorrect because being a subset of BCNF is not an advantage for 3NF.

Option D is incorrect because it is not stricter than BCNF

If you liked the solution then give a thumbs up ? it will be really appreciated ?