What does it mean for a database to be "Normalized"?

For a database to be "Normalized," it specifically refers to the process of organizing tables in a way that reduces data redundancy and dependency. This means that the data is structured in such a manner that duplicate data is minimized, which helps maintain data integrity and efficiency. Each piece of information is stored in only one place, which simplifies the database management and ensures that updates or changes to the data occur in a single location, preventing discrepancies and anomalies.

Normalization typically involves dividing large tables into smaller, related tables and defining relationships between them. This structured method of data management aids in achieving a more efficient and logical database design, ultimately enhancing the performance of data operations and reducing storage needs.

The other options, while touching upon various aspects of databases, do not accurately capture the essence of normalization. For instance, reducing the number of tables or allowing data duplication contradicts the fundamental principles of normalization. Thus, the focus on organizing tables to minimize data redundancy is what makes option B the correct choice.