NOSQL DATA MODELLING — Learn free

Self-check

Questions 1–10 of 10

1. What primarily drives NoSQL data modelling, in contrast to relational modelling?
Question 1A. Application access patterns and workload requirementsB. Normalisation theory and functional dependenciesC. Class hierarchies and inheritanceD. Physical pointer navigationE. Domain and key constraints
2. Which four database families does NoSQL data modelling cover?
Question 2A. Hierarchical, network, relational and object-orientedB. Document stores, key–value stores, wide-column databases and graph databasesC. Star, snowflake, data vault and anchorD. OLTP, OLAP, HTAP and streamingE. JSON, XML, CSV and Parquet
3. Why are NoSQL models often intentionally denormalised or embedded?
Question 3A. To satisfy Boyce–Codd Normal FormB. To enforce global consistency rulesC. To minimise joins and reduce cross-node communication in distributed environmentsD. To make schemas rigid and predictableE. To support relational algebra
4. Which questions guide NoSQL design decisions?
Question 4A. Which attributes depend on part of the composite key?B. Is every determinant a superkey?C. Which entities share a transitive dependency?D. What are the most frequent queries, and how can this data be retrieved in a single read?E. Which constraints can be expressed as domains or keys?
5. In a document database such as MongoDB, how might the loan approval domain be modelled?
Question 5A. With LoanID as a key and a JSON blob as the valueB. With data partitioned by CustomerID across columnsC. With Customer, Loan and Transaction as nodes connected by edgesD. With separate normalised Customer, Loan and Repayment tablesE. With a Customer document embedding Loan Applications and their Repayments in one JSON structure
6. In a key–value database such as Redis or DynamoDB, what would the loan example use as key and value?
Question 6A. LoanID as the key and a JSON blob of all loan details as the valueB. CustomerID as the partition and loans as columnsC. A node for each loan and an edge for each repaymentD. A composite key of LoanID and RepayDateE. A surrogate key and a normalised row
7. Which NoSQL family is described as partitioning data by CustomerID to support high write throughput and distributed scalability?
Question 7A. Document databases such as MongoDBB. Wide-column databases such as Cassandra or BigtableC. Graph databases such as Neo4jD. Key–value databases such as RedisE. Object databases such as ObjectStore
8. Why does strict normalisation become a problem in massively distributed systems?
Question 8A. Because normalised tables cannot store JSONB. Because normalisation forbids replicationC. Because joins and cross-node coordination can introduce performance bottlenecksD. Because normalised schemas cannot be indexedE. Because normalisation requires a single server
9. Which of the following is NOT a claim made about the relationship between NoSQL and relational systems?
Question 9A. NoSQL complements relational modelling rather than replacing itB. Relational systems remain the best choice for strong consistency and complex transactionsC. Relational and NoSQL systems coexist in modern enterprisesD. NoSQL makes relational theory obsoleteE. There is no one-size-fits-all model
10. In the example of a single organisation using several database types, which workload is matched with a graph database?
Question 10A. Financial transactionsB. Customer profilesC. CachingD. Regulatory reportingE. Fraud detection