EVENT-DRIVEN DATA MODELLING — Learn free

Self-check

Questions 1–10 of 10

1. What is the primary unit of design in Event-Driven Data Modelling?
Question 1A. The event, a discrete occurrence capturing something that has happenedB. The static entity such as Customer or LoanC. The fact tableD. The partition keyE. The class with its methods
2. What two properties characterise events in an event-driven model?
Question 2A. Normalised and indexedB. Immutable and append-onlyC. Mutable and versionedD. Cached and volatileE. Hierarchical and nested
3. Which of the following is an example event from the loan approval domain?
Question 3A. LoanCollateralB. CustomerProfileC. LoanApplicationSubmittedD. InterestRateDimensionE. RepaymentSchedule
4. How is the current state of a loan determined in an event-driven system?
Question 4A. It is stored directly in a Loan tableB. It is cached in a key–value store as the source of truthC. It is looked up from a dimension tableD. It is derived by replaying the sequence of eventsE. It is computed by joining fact and dimension tables
5. Which platform is named as an event streaming implementation for a loan approval system?
Question 5A. Neo4jB. MongoDBC. CassandraD. RedisE. Apache Kafka
6. In the event-driven loan example, what happens after the underwriting service consumes a LoanApplicationSubmitted event?
Question 6A. It processes the application and emits a LoanApplicationApproved or LoanApplicationRejected eventB. It updates the original event with the decisionC. It deletes the submitted eventD. It writes the decision to a dimension tableE. It locks the customer record
7. Which teams can subscribe to the same loan event streams in real time without interfering with operational systems?
Question 7A. Only the underwriting serviceB. Fraud detection, compliance monitoring and analytics teamsC. Only the mobile applicationD. Only the database administratorsE. Only the regulator
8. Which of the following is NOT listed as a strength of event-driven data modelling?
Question 8A. Real-time responsiveness and reactive architecturesB. A built-in audit trail because every change is an immutable eventC. Simple infrastructure with no need for streaming platformsD. Replayability to rebuild projections or generate analytics retrospectivelyE. Support for audit, compliance, debugging, simulation and machine learning training
9. Which challenge is named as part of the complexity of event-driven modelling?
Question 9A. Eliminating transitive dependenciesB. Choosing a partition keyC. Defining class inheritanceD. Managing event schema versioning rigorously as systems evolveE. Avoiding Cartesian explosion
10. Why do normalisation forms not directly apply to event-driven modelling?
Question 10A. Because events are always stored in 6NFB. Because events have no timestampsC. Because events are stored as graph edgesD. Because event stores enforce domain–key constraintsE. Because events are append-only records centred on temporal sequencing rather than relational dependency theory