HOOK — Learn free · DataAI Nexus

Self-check

Questions 1–10 of 10

1. Who introduced the HOOK technique for data warehousing?
Question 1A. Bill InmonB. Ralph KimballC. Andrew FoadD. Dan LinstedtE. Edgar Codd
2. What is the single structure that HOOK uses instead of the many table types of Data Vault and Kimball?
Question 2A. A HubB. A BagC. A SatelliteD. A Fact tableE. A Bridge
3. In HOOK, what does a Bag expose from the table it wraps?
Question 3A. Surrogate keys generated by the warehouseB. Row-level security policiesC. Aggregated measures for reportingD. Business Keys aligned to Business Concepts in the Enterprise Data ModelE. Compression settings for the storage layer
4. How are HOOK Bags typically implemented?
Question 4A. As materialised tables reloaded nightlyB. As stored proceduresC. As views defined over existing data warehouse tablesD. As separate physical databasesE. As flat files in object storage
5. What is the purpose of qualifying each HOOK Key with a Key Set?
Question 5A. To compress the key for faster storageB. To encrypt the business key at restC. To record when the key was last refreshedD. To decide which Bag the key belongs toE. To identify the set of values the Business Key belongs to so that joins do not produce unintended matches
6. In the loan example from I Am Datapedia!, why is there no risk of customer C123 from CRM colliding with C123 from CoreBank?
Question 6A. The two systems are never loaded into the same warehouseB. Hook values include Key Sets, so the two keys are distinct valuesC. CoreBank renumbers its customers on ingestionD. The join is done on customer name instead of IDE. The warehouse rejects duplicate IDs at load time
7. How does HOOK differ from Data Vault regarding modelling before ingestion?
Question 7A. HOOK requires a full logical model before any data is loadedB. HOOK requires more upfront modelling than Data VaultC. HOOK does not require upfront modelling before ingesting dataD. HOOK forbids ingesting data until every Business Concept is approvedE. HOOK and Data Vault take exactly the same approach
8. Which statement about HOOK is described as a common misconception?
Question 8A. That HOOK is a data warehouse modelling approachB. That HOOK can be layered over existing architectureC. That Bags can be implemented as viewsD. That HOOK Keys must carry a Key SetE. That HOOK borrows features from Kimball
9. Which of the following is NOT a Hook column used in the LoanApproval join example from I Am Datapedia!?
Question 9A. HK_CustomerB. HK_OfficerC. HK_DateD. HK_BranchE. HK_Loan
10. Why is the HOOK approach described as extremely agile?
Question 10A. Because it stores all data in memoryB. Because it eliminates the need for business keysC. Because it replaces SQL with a graphical query languageD. Because it requires a single central modelling teamE. Because Bags as views can be dropped and recreated without reloading data or consuming resources