What is Normalization? — Learn free

Self-check

Questions 1–10 of 10

1. What is Normalisation?
Question 1A. The systematic process of organising data into well-structured tables by decomposing it step by step into progressively refined formsB. The process of merging tables to speed up reportingC. The process of converting data into text formatD. The process of indexing a databaseE. The process of encrypting sensitive columns
2. What is the core principle that normalisation follows?
Question 2A. Each attribute should depend only on the key, the whole key and nothing but the keyB. Each table should have as many columns as possibleC. Each fact should be stored in several places for safetyD. Each attribute should depend on another non-key attributeE. Each table should contain repeating groups
3. Which normal form is commonly sufficient for most transactional systems?
Question 3A. First Normal FormB. Second Normal FormC. Third Normal FormD. Fifth Normal FormE. Sixth Normal Form
4. How does BCNF relate to 3NF?
Question 4A. BCNF is weaker than 3NFB. BCNF replaces the need for 1NFC. BCNF addresses join dependenciesD. BCNF strengthens 3NF by addressing edge cases involving overlapping candidate keysE. BCNF is the same as 6NF
5. Which normal form decomposes data so that each table represents a single fact, often useful in temporal modelling?
Question 5A. 2NFB. 3NFC. 4NFD. 5NFE. 6NF
6. What is Domain-Key Normal Form (DKNF)?
Question 6A. The first practical normal formB. A denormalised reporting formC. A form that allows repeating groupsD. A theoretical ideal in which all constraints can be expressed solely through domain definitions and key relationshipsE. A NoSQL schema pattern
7. Which of the following is NOT a stated benefit of normalisation?
Question 7A. Consistency through reduced duplicationB. Safer updates because changes occur in one placeC. Fewer joins for analytical reportingD. Clearer, easier-to-enforce integrity rulesE. Insertions and deletions that do not create orphaned data
8. What trade-off does normalisation introduce?
Question 8A. Data becomes less consistentB. Storage use increases through duplicationC. Updates must be made in many placesD. Integrity rules become harder to enforceE. Queries may require multiple joins to reconstruct complete business views, which can hurt performance in read-heavy environments
9. In the loan scenario, what risk arises when customer details are stored directly in every loan record?
Question 9A. Loans cannot be approvedB. If the customer's address changes, every related loan row must be updatedC. The loan amount cannot be storedD. The database cannot be indexedE. Customers cannot take more than one loan
10. How does normalisation resolve the duplicated customer details in the loan example?
Question 10A. By deleting customer details from all loansB. By creating a separate Customer table linked to Loan through a foreign key such as CustIDC. By storing customer details in a text fileD. By merging Loan and Customer into one wider tableE. By adding a new column for each address change