We need to do a lot of things here, so it’s better to avoid wasting time by introducing the whole Data Model concept as well as the various meanings of these two words. The experienced reader, as well as the seasoned developer, will be most likely aware of all the relevant stuff. We’ll just say that when we are talking about a Data Model, we don’t mean anything more or anything less than a lightweight, definitely-typed set of entity classes representing persistent, code-driven Data Structures that we can use as resources within our Web API code.

The word persistent has been used for a reason; we want our data structure to be stored in a Database. That's rather obvious for any application based on data. Our TestMakerFree app won’t be an exception, since we want it to act as a collection--or a repository--of user made quizzes. More than requiring a Database, our Single-Page Application aims to be a web-brows able Database by itself.