Hierarchical Data Modelling — Learn free

Self-check

Questions 1–10 of 10

1. How does Hierarchical Data Modelling structure data?
Question 1A. In a strict tree where each child record has exactly one parentB. In owner–member sets allowing many parents per recordC. In nodes and edges with typed relationshipsD. In JSON documents with nested arraysE. In fact and dimension tables
2. Which mainframe system is given as the classic example of hierarchical data modelling in the 1960s and 1970s?
Question 2A. CODASYL IDMSB. IBM's Information Management System (IMS)C. ObjectStoreD. Neo4jE. Cassandra
3. In the hierarchical loan example Bank → Branch → Loan Officer → Customer → Loan → Repayment, what is true of a Repayment record?
Question 3A. It can belong to several loans at onceB. It is stored independently of any loanC. It cannot exist without a LoanD. It is the root of the hierarchyE. It links directly to a Branch
4. Why is retrieving all repayments for a specific loan straightforward in a hierarchical model?
Question 4A. Because the database performs a declarative joinB. Because repayments are stored in a separate fact tableC. Because the query engine infers the relationship semanticallyD. Because the system simply navigates down the predefined tree pathE. Because repayments are indexed by customer
5. Which query illustrates the kind of question a strict hierarchical model struggles to answer?
Question 5A. Which repayments belong to loan L001?B. Which customers belong to this loan officer?C. Which loans belong to this customer?D. Which branches belong to this bank?E. Which loan officers approved loans across multiple branches?
6. Why does normalisation theory not apply to hierarchical data modelling?
Question 6A. Because the model predates the relational model and is based on physical navigation paths rather than dependency theoryB. Because hierarchical databases are always already in 3NFC. Because hierarchical models have no keysD. Because hierarchical databases store only unstructured textE. Because normalisation applies only to NoSQL systems
7. Where does hierarchical data modelling still exist today?
Question 7A. In most new cloud-native enterprise systemsB. In legacy mainframes and directory services such as LDAP and Active DirectoryC. In data warehouses built as star schemasD. In graph databases for fraud detectionE. In event-streaming platforms
8. What is the key difference between Hierarchical Data Modelling and a taxonomy?
Question 8A. A taxonomy has no parent–child relationshipsB. A hierarchical model is drawn as a graph while a taxonomy is drawn as a treeC. A hierarchical model is a database storage model governing physical access, whereas a taxonomy is a conceptual classification of meaningD. A taxonomy is used only in mainframesE. They are the same thing under different names
9. Which example illustrates a taxonomy rather than a hierarchical database structure?
Question 9A. Bank → Branch → Loan → RepaymentB. Customer → Loan → Officer traversalC. Owner–member sets in IDMSD. Loan → Personal Loan → Student LoanE. LoanID → CustID → CustomerName
10. Which of the following is NOT listed as a strength of hierarchical data modelling?
Question 10A. High efficiency for predictable one-to-many queriesB. Simple, understandable structures when relationships are strictly nestedC. Strong performance in tightly controlled operational systems with fixed access patternsD. Deterministic navigation from parent to childE. Effective support for dynamic, ad-hoc analytical queries