Question 1

Figuer:
The table STUDENTA has the following meaning. A student may have several majors and several minors; the choice of majors and minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTA $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { GREEN } & \text { PHILO } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { LAMPO } & \text { MKTG } & \text { MGT } \
\hline \text { Takker } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is a functional dependency in the table STUDENTA:
A) Name -> Minor
B) Name -> Major
C) Name -> Minor, Major
D) None of the above

Accepted Answer

Given the table structure and data, no single column (Name, Major, or Minor) can uniquely determine any other column due to the presence of multiple majors and minors for a single name and the independence of majors and minors. Therefore, none of the listed functional dependencies are correct.

Question 2

Figuer:
Name is the unique candidate key in the table STUDENT. Each row in the table describes a different student. A student may only have one major and one minor. The choice of a major is independent of the choice of a minor
STUDENT $$\begin{array} { | l | l | l | l | } 
\hline \text { NAME } & \text { AGE } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & 26 & \text { MATH } & \text { INFO } \
\hline \text { HONEY } & 18 & \text { INFO } & \text { MATH } \
\hline \text { LAMPOC } & 33 & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & 45 & \text { MKTG } & \text { MGT } \
\hline \text { TRAN } & 45 & \text { MATH } & \text { INFF } \
\hline \text { YONAR } & 28 & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is a functional dependency in the table STUDENT:
A) Major -> Minor
B) Minor -> Major
C) Major -> Age
D) Name -> Minor

Accepted Answer

The unique candidate key is "Name," which means each name uniquely identifies a row in the table, including the minor chosen by the student. The other options (A, B, C) are not guaranteed by the data provided, as multiple students can have the same major or minor without a direct functional dependency on age or each other.

Question 3

A database design with many tables results in the database being easier to change but more difficult to query.

Accepted Answer

This is because having many tables allows for a more normalized database structure, which makes it easier to make changes to the database schema without affecting the rest of the database. However, querying the data from many tables can become more complex and require more advanced SQL statements.

Question 4

Figuer:
The table STUDENTB has the following meaning. A student may have one major only and several minors; the choice of the major and of minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTB $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { HONEY } & \text { INFO } & \text { MGT } \
\hline \text { LAMPOC } & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is a functional dependency in the table STUDENTB:
A) Name -> Minor
B) Name -> Major
C) Major -> Minor
D) Major -> Name

Accepted Answer

Given that each student has a unique name and can have only one major, but multiple minors, the only functional dependency that holds is "Name -> Major". This means a student's name uniquely determines their major.

Question 5

Figuer:
The table STUDENTA has the following meaning. A student may have several majors and several minors; the choice of majors and minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTA $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { GREEN } & \text { PHILO } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { LAMPO } & \text { MKTG } & \text { MGT } \
\hline \text { Takker } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is a multivalued dependency in the table STUDENTA:
A) Name -> ->Major | Minor
B) Name -> Major
C) Name -> Minor
D) None of the above

Accepted Answer

A multivalued dependency exists when, for a single key (in this case, Name), there can be multiple values for other columns (Major and Minor) independently of each other. The table shows that a student (Name) can have multiple Majors and Minors independently, fitting the definition of a multivalued dependency.

Question 6

An experienced database designer always tries to achieve at least 3NF in all of their tables.

Accepted Answer

The answer of An experienced database designer always tries to...

Question 7

Normalization techniques may be used in database development to improve the design that results from the Entity Relationship approach,but you cannot directly build database tables from the functional dependencies.

Accepted Answer

Normalization techniques directly use functional dependencies to define the structure of tables, ensuring that the database is free of redundancy and update anomalies.

Question 8

Figuer:
The table STUDENTA has the following meaning. A student may have several majors and several minors; the choice of majors and minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTA $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { GREEN } & \text { PHILO } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { LAMPO } & \text { MKTG } & \text { MGT } \
\hline \text { Takker } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The table STUDENTA satisfies the following normal form (choose the highest NF):
A) 1NF
B) 2NF
C) 3NF
D) 4NF

Accepted Answer

The table is in 3NF because it is in 2NF and every non-prime attribute is functionally dependent on the primary key.

Question 9

In the table STUDENTB,when Green replaces her MATH major by a PHYSICS major,the following anomaly is evidenced:
A) update anomaly
B) insertion anomaly
C) deletion anomaly
D) none of the above

Accepted Answer

An update anomaly occurs when updating data in a database results in inconsistencies or errors due to the data being stored in multiple tables. In this scenario, if Green updates her major from MATH to PHYSICS in the STUDENTB table, records in other tables that are related to her student ID may still have her listed as a MATH major, creating an inconsistency in the data. This is an example of an update anomaly.

Question 10

Figuer:
The table STUDENTB has the following meaning. A student may have one major only and several minors; the choice of the major and of minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTB $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { HONEY } & \text { INFO } & \text { MGT } \
\hline \text { LAMPOC } & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The table STUDENTB satisfies the following normal form (choose the highest NF):
A) 1NF
B) 2NF
C) 3NF
D) 4NF

Accepted Answer

The answer of Figuer:
The table STUDENTB has the following meaning....

Question 11

Figuer:
Name is the unique candidate key in the table STUDENT. Each row in the table describes a different student. A student may only have one major and one minor. The choice of a major is independent of the choice of a minor
STUDENT $$\begin{array} { | l | l | l | l | } 
\hline \text { NAME } & \text { AGE } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & 26 & \text { MATH } & \text { INFO } \
\hline \text { HONEY } & 18 & \text { INFO } & \text { MATH } \
\hline \text { LAMPOC } & 33 & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & 45 & \text { MKTG } & \text { MGT } \
\hline \text { TRAN } & 45 & \text { MATH } & \text { INFF } \
\hline \text { YONAR } & 28 & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is not a functional dependency in the table STUDENT:
A) Name -> Age
B) Age -> Name
C) Name -> Minor
D) Name -> Major

Accepted Answer

A functional dependency exists when a particular value of one attribute (column) uniquely determines another attribute's value within a database table. In this table, "Name" is a unique candidate key, meaning each name uniquely identifies a row, so "Name -> Age", "Name -> Minor", and "Name -> Major" are all valid functional dependencies. However, "Age -> Name" is not a functional dependency because the same age value (e.g., 45) does not uniquely determine a single name; both "TAKKER" and "TRAN" are 45.

Question 12

The table STUDENTA contains many more rows than shown.It is replaced by the following two tables with appropriate distribution of data to the new tables. $Table1\
\begin{array}{|l|l|}
\hline \text { NAME} & \text { MAJOR} \
\hline
\end{array}$

$Table2\
\begin{array}{|l|l|}
\hline \text { NAME} & \text { MINOR } \
\hline
\end{array}$
A) Some information is lost in this transformation and some meaningless information is provided
B) The new tables provide the same information as the old one with less data duplication
C) The new tables provide the same information as the old one with more data duplication
D) None of the above

Accepted Answer

The new tables provide the same information as the old one with less data duplication.

Question 13

The difference between value-based constraints and value-neutral constraints is that value-based constraints are based on the comparison of columns while value-neutral constraints are based on the comparison of a column to constant using a comparison operator.

Accepted Answer

Value-based constraints and value-neutral constraints differ primarily in their basis for restriction: value-based constraints are influenced by ethical, cultural, or personal values, guiding what is considered acceptable or not in a decision-making process, whereas value-neutral constraints are applied without such considerations, focusing solely on logical or factual limitations. The description provided mixes concepts from database management (comparing columns or a column to a constant) with the broader concept of value-based versus value-neutral decision-making principles.

Question 14

Figuer:
Name is the unique candidate key in the table STUDENT. Each row in the table describes a different student. A student may only have one major and one minor. The choice of a major is independent of the choice of a minor
STUDENT $$\begin{array} { | l | l | l | l | } 
\hline \text { NAME } & \text { AGE } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & 26 & \text { MATH } & \text { INFO } \
\hline \text { HONEY } & 18 & \text { INFO } & \text { MATH } \
\hline \text { LAMPOC } & 33 & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & 45 & \text { MKTG } & \text { MGT } \
\hline \text { TRAN } & 45 & \text { MATH } & \text { INFF } \
\hline \text { YONAR } & 28 & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following anomaly exists in the table STUDENT:
A) update anomaly
B) insertion anomaly
C) deletion anomaly
D) none of the above

Accepted Answer

The answer of Figuer:
Name is the unique candidate key in...

Question 15

The table schema STUDENT is replaced by the following two tables' schemas: $Table1\
\begin{array}{|l|l|l|}
\hline \text { NAME } & \text { AGE } & \text { MAJOR } \
\hline
\end{array}$

$Table2\
\begin{array}{|l|l|}
\hline \text { MAJOR } & \text { MINOR } \
\hline
\end{array}$
A) Some information is lost in this transformation and some meaningless information is provided
B) The new tables provide the same information as the old ones with less data duplication
C) The new tables provide the same information as the old ones with more data duplication
D) None of the above

Accepted Answer

The transformation introduces the possibility of having a MAJOR associated with multiple MINORS in Table2, which was not explicitly represented in the original STUDENT table schema. Additionally, if the original STUDENT table included unique student identifiers or other attributes, this information would be lost in the transformation. The separation into two tables without a clear linkage for individual students' minors introduces ambiguity and potential data integrity issues, thus leading to loss of specific information and introduction of potentially meaningless associations between majors and minors without context to specific students.

Question 16

One of the arguments in favor of using normalization as a refinement tool instead of an initial design tool is that by first developing an ERD,much of the normalization is done informally and therefore is not as tedious a process as recording all the functional dependencies.

Accepted Answer

Developing an ERD involves identifying the entities, attributes, and relationships in a system, which can lead to the informal identification of functional dependencies. This makes the normalization process less tedious when refining the design, rather than starting from scratch.

Question 17

Figuer:
Name is the unique candidate key in the table STUDENT. Each row in the table describes a different student. A student may only have one major and one minor. The choice of a major is independent of the choice of a minor
STUDENT $$\begin{array} { | l | l | l | l | } 
\hline \text { NAME } & \text { AGE } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & 26 & \text { MATH } & \text { INFO } \
\hline \text { HONEY } & 18 & \text { INFO } & \text { MATH } \
\hline \text { LAMPOC } & 33 & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & 45 & \text { MKTG } & \text { MGT } \
\hline \text { TRAN } & 45 & \text { MATH } & \text { INFF } \
\hline \text { YONAR } & 28 & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The table STUDENT satisfies the following normal form (choose the highest NF):
A) 1NF
B) 2NF
C) 3NF
D) 4NF

Accepted Answer

The answer of Figuer:
Name is the unique candidate key in...

Question 18

Figuer:
The table STUDENTB has the following meaning. A student may have one major only and several minors; the choice of the major and of minors is independent of each other. Each student has a unique name. The table has only one candidate key.
STUDENTB $$\begin{array} { | l | l | l | } 
\hline \text { NAME } & \text { MAJOR } & \text { MINOR } \
\hline \text { GREEN } & \text { MATH } & \text { INFO } \
\hline \text { GREEN } & \text { MATH } & \text { MKTG } \
\hline \text { HONEY } & \text { INFO } & \text { MATH } \
\hline \text { HONEY } & \text { INFO } & \text { MGT } \
\hline \text { LAMPOC } & \text { MKTG } & \text { MGT } \
\hline \text { TAKKER } & \text { MKTG } & \text { MGT } \
\hline \text { YONA } & \text { INFO } & \text { MATH } \
\hline
\end{array}$$
-The following is a multivalued dependency in the table STUDENTB:
A) Name -> ->Major | Minor
B) Name -> Major
C) Name -> Minor
D) None of the above

Accepted Answer

Given the table structure and the data, none of the options A, B, or C correctly describe a multivalued dependency in the table STUDENTB. A multivalued dependency would imply a certain structure that is not present here, especially considering the unique nature of the candidate key and the independence of majors and minors.

Question 19

Even if a database is to be used mostly for querying data,with little or no change to the data,the highest degree of normalization should still be implemented.

Accepted Answer

Normalization primarily aims to reduce redundancy and improve data integrity, but the highest degree of normalization (e.g., going to 5th Normal Form) can lead to increased complexity and potentially slower query performance. For databases focused on querying, a balance between normalization and performance needs is often sought, sometimes accepting some denormalization for faster read operations.

Question 20

Deleting the second row from the table STUDENTA causes:
A) an update anomaly
B) a deletion anomaly
C) an insertion anomaly
D) no loss of information

Accepted Answer

The answer of Deleting the second row from the table...

Quiz 7: Normalization of Relational Tables

A database design with many tables results in the database being easier to change but more difficult to query.

An experienced database designer always tries to achieve at least 3NF in all of their tables.

Normalization techniques may be used in database development to improve the design that results from the Entity Relationship approach,but you cannot directly build database tables from the functional dependencies.

In the table STUDENTB,when Green replaces her MATH major by a PHYSICS major,the following anomaly is evidenced:

The difference between value-based constraints and value-neutral constraints is that value-based constraints are based on the comparison of columns while value-neutral constraints are based on the comparison of a column to constant using a comparison operator.

The table schema STUDENT is replaced by the following two tables' schemas: $Table1\\\begin{array}{|l|l|l|}\hline \text { NAME } & \text { AGE } & \text { MAJOR } \\\hline\end{array}$ $Table2\\\begin{array}{|l|l|}\hline \text { MAJOR } & \text { MINOR } \\\hline\end{array}$

One of the arguments in favor of using normalization as a refinement tool instead of an initial design tool is that by first developing an ERD,much of the normalization is done informally and therefore is not as tedious a process as recording all the functional dependencies.

Even if a database is to be used mostly for querying data,with little or no change to the data,the highest degree of normalization should still be implemented.

Deleting the second row from the table STUDENTA causes: