While you may not know much about IT, you do know enough to realize that taking over your fathers business will mean switching from his paper records to a computerized system. The consultant you hired to do this has transferred the information into what he refers to as a first normal form table, which looks to you like a big spreadsheet with a lot of the information repeating itself in various places. Is he correct when he explains to you that the next steps involve determining the functional dependencies by defining the associations of particular attributes with each other, then using normalization methodology to organize attributes into separate tables to eliminate non-key attribute redundancies, and finally using join operations to combine the records in the different tables into a database? Why or why not?

• A: No. Functional dependencies express entities associated with attributes of other entities; normalization uses functional dependencies, is a means of expressing a value, and minimizes integrity; and the join operation combines records from two or more tables to obtain information located in different tables.

• B : No. Functional dependencies express entities associated with attributes of other entities; normalization uses functional dependencies, is a means of analysis, and minimizes redundancy; and the join operation combines records from two or more tables to obtain information located in different tables.

• C : Yes. He will create a relational database with optimal processing performance, maximum data integrity, and minimum redundancy.

• D :No. Functional dependencies express values of an attribute associated with a value of another; normalization uses functional dependencies, is a means of expressing a value, and minimizes integrity; and the join operation combines records from two or more tables to obtain information located in different tables.