OBJECT-ORIENTED DATA MODELLING — Learn free

Self-check

Questions 1–10 of 10

1. How does Object-Oriented Data Modelling represent data?
Question 1A. As objects that combine attributes (data) and methods (behaviour)B. As rows and columns governed by functional dependenciesC. As owner–member sets linked by pointersD. As immutable events in an append-only logE. As key–value pairs optimised for lookup
2. What was the original goal of object-oriented data modelling?
Question 2A. To maximise analytical query performanceB. To align persistent storage directly with object-oriented application design, removing the need to transform objects into relational tablesC. To enforce Third Normal Form in application codeD. To support horizontal scale-out across distributed nodesE. To provide a semantic layer for reasoning
3. In an object-oriented model, which method might a LoanApplication class define?
Question 3A. calculateRisk()B. normalise()C. partitionByCustomer()D. approve()E. traverseSet()
4. How are relationships between entities expressed in object-oriented data modelling?
Question 4A. Through foreign keysB. Through owner–member setsC. Through object referencesD. Through shared partition keysE. Through fact-table joins
5. Which products are named as Object-Oriented Database Management Systems from the late 1980s and 1990s?
Question 5A. Hibernate, Entity Framework and SpringB. MongoDB, Couchbase and RedisC. IMS, IDMS and DB2D. Neo4j, Cassandra and BigtableE. ObjectStore, GemStone and Versant
6. What largely overtook pure object databases by the early 2000s?
Question 6A. Relational databases combined with Object-Relational Mapping frameworks such as Hibernate and Entity FrameworkB. Hierarchical mainframe databasesC. Graph databasesD. Wide-column storesE. Event-streaming platforms
7. In the loan approval scenario, when do the limitations of an object database become evident?
Question 7A. When storing a single LoanApplication objectB. When the organisation needs large-scale reporting, regulatory analytics or cross-portfolio aggregationC. When adding a new attribute to the Customer classD. When invoking the approve() methodE. When defining inheritance between loan types
8. Why do normalisation forms not directly apply to object-oriented data modelling?
Question 8A. Because object databases store only unstructured dataB. Because objects are always stored in 6NFC. Because objects are not structured as relational tables governed by functional dependencies; design is driven by class hierarchies and behaviour encapsulationD. Because object databases forbid primary keysE. Because object databases only support analytical workloads
9. Which of the following is NOT listed as a challenge of object-oriented data modelling?
Question 9A. Query capabilities that are more procedural and less flexible than SQLB. Difficulty supporting analytical use cases efficientlyC. Limited interoperability across systems compared with relational standardsD. Inability to express inheritance between classesE. Being largely obsolete as a standalone database paradigm
10. Where does the influence of object-oriented data modelling persist today?
Question 10A. In hierarchical directory servicesB. In CODASYL network databasesC. In Domain–Key Normal FormD. In star schema fact tablesE. In document databases with nested JSON structures and in API payloads that mirror object models