You work as a Software Developer for ArchiTech Inc. You plan to create a well-designed database for
the company. You implement normalization rules for designing the database. Choose the
appropriate normalization rules from the Choose and Reorder window pane.

Answer:

Explanation:
The following are some normalization rules that can be made for achieving a well-designed
database: Each table in a database should have a unique row identifier, i.e. an ID column in which
no two records can share the same ID value. Such column is known as the primary key column that
serves as the unique row identifier for the table. For example, ProductID can be the primary key
column for the Products table.Each table in a database should store information for a single type of
entity. Too much information stored in one table can hinder the efficiency and reliability of data in

the table. For example, in a table, the columns that contain information of both sales order and
customer details can lead to several problems. It is a best practice to store both these information in
separate tables for better maintenance and avoidance of any query issues.A table in a database
should avoid containing nullable columns. However, some columns of a table can be defined to
allow null values. A table in a database should not contain repeated values or columns for a specific
piece of information. For example, a product may be purchased from multiple vendors. If the
product name and the names of all the vendors are stored in one table, it will contain columns for all
the vendors with repeating product ID. This will create several problems. Therefore, it is a best
practice to store product information in one table and the names of all vendors in another table. For
creating relationships between the two tables, a common column such as ProductID should be
placed in both the tables.