[{"id":"neo4jbeginner-001","courseId":"neo4j-beginner","domain":"graph-modeling","topic":"Nouns as nodes","prompt":"You are designing a model for a movie app. Its questions include 'Which people acted in a movie?' and 'How many users rated a movie?'. Which elements should become nodes?","hint":"Sort the words in the questions into things and actions.","explain":"A use case keeps naming the things it cares about and the actions that link them. Model those two kinds of word differently, and decide which kind each word in the questions belongs to.","source":"https://neo4j.com/docs/getting-started/data-modeling/guide-data-modeling/","interaction":{"type":"single"},"options":[{"id":"a","text":"acted, rated and directed: the verbs the questions use","whyNot":"Verbs describe how entities connect, so they become relationships rather than nodes."},{"id":"b","text":"Each field of a source table, so every column gets a node","whyNot":"Fields are better kept as properties on a node; a column is not an entity in its own right."},{"id":"c","text":"Person, Movie and User: the nouns the questions ask about","why":"The dominant nouns in a use case are represented as nodes and can be used as labels."},{"id":"d","text":"Only Movie, with people and users stored as movie properties","whyNot":"People and users are dominant nouns of their own, so each one gets its own node."}],"answer":"c","explanation":"Dominant nouns in a use case become node labels; the verbs that connect them become relationships.","concept":"Dominant nouns in a use case become node labels; the verbs that connect them become relationships.","rev":1,"updatedAt":"2026-10-27","kind":"scenario","takeaways":["Nouns in a use case usually become nodes; verbs usually become relationships."]},{"id":"neo4jbeginner-002","courseId":"neo4j-beginner","domain":"graph-modeling","topic":"Node labels","prompt":"In Neo4j, every node must carry at least one label.","hint":"Consider the smallest number of labels a node is allowed to have.","explain":"Labels group nodes into sets, so that operations can target one kind of node at a time. A label is a classification attached to a node, and a node's classifications can be changed.","source":"https://neo4j.com/docs/getting-started/appendix/graphdb-concepts/","interaction":{"type":"true-false"},"options":[{"id":"a","text":"True","whyNot":"A node can have zero to many labels, so a node with no label at all is allowed."},{"id":"b","text":"False","why":"Zero labels is a valid count, so a node is not required to carry one."}],"answer":"b","explanation":"A node can have zero to many labels; labels classify nodes and can be added and removed at runtime.","concept":"A node can have zero to many labels; labels classify nodes and can be added and removed at runtime.","rev":1,"updatedAt":"2026-10-27","kind":"scenario","takeaways":["A node may carry no labels at all, one label, or several."]},{"id":"neo4jbeginner-003","courseId":"neo4j-beginner","domain":"graph-modeling","topic":"Multiple labels per node","prompt":"A node in your graph should count as both a Person and an Actor. Which TWO of these statements about node labels are correct?","hint":"Compare what a label does with what a property does.","explain":"A label places a node into a group, which is a different job from storing data on it. The memberships a node holds are not capped at one, and they can shift as the data changes.","source":"https://neo4j.com/docs/getting-started/appendix/graphdb-concepts/","interaction":{"type":"multiple","tellCount":true},"options":[{"id":"a","text":"A node can carry several labels at once, such as Person and Actor.","why":"A node can have zero to many labels, so one node can hold both Person and Actor."},{"id":"b","text":"A node can have only one label; a second label needs a second node.","whyNot":"Nodes can have zero to many labels, so one node can hold both labels."},{"id":"c","text":"A node must have at least one label to be stored in the graph.","whyNot":"A node may have zero labels, so a label-free node is valid."},{"id":"d","text":"Labels are fixed when the node is created and can never change.","whyNot":"Labels can be added and removed during runtime."},{"id":"e","text":"A label can be removed from a node while the database is running.","why":"Labels can be added and removed at runtime, so a node's classification can change later."},{"id":"f","text":"Labels hold a node's property values, such as name and born.","whyNot":"Properties store the values; labels only classify the node."}],"answer":"ae","explanation":"A node can have zero to many labels, which classify it; labels can be added and removed at runtime, while properties store values.","concept":"A node can have zero to many labels, which classify it; labels can be added and removed at runtime, while properties store values.","rev":1,"updatedAt":"2026-10-27","kind":"scenario","takeaways":["Labels classify nodes; properties store their values."]},{"id":"neo4jbeginner-004","courseId":"neo4j-beginner","domain":"graph-modeling","topic":"Single type per relationship","prompt":"A teammate creates one relationship with two types, ACTED_IN and DIRECTED, to record both roles in one link. What does the model say about relationship types?","hint":"Think about how many kinds a single connection can belong to.","explain":"A connection in the graph is classified by a name, and that name tells a search which links it may follow. Consider what happens when a single connection is given several names.","source":"https://neo4j.com/docs/getting-started/appendix/graphdb-concepts/","interaction":{"type":"single"},"options":[{"id":"a","text":"A relationship can carry as many types as the data needs.","whyNot":"A type classifies the relationship, and the model allows only one type per relationship."},{"id":"b","text":"A relationship can skip its type when it has properties.","whyNot":"Every relationship needs a type, whether or not it has properties."},{"id":"c","text":"Types must be written as a list, so both names fit in one value.","whyNot":"A type is a single name, not a list of names."},{"id":"d","text":"Each relationship must have exactly one relationship type.","why":"The model requires exactly one type, so the two roles need two separate relationships."}],"answer":"d","explanation":"A relationship must have exactly one relationship type, which classifies what kind of connection it is.","concept":"A relationship must have exactly one relationship type, which classifies what kind of connection it is.","rev":1,"updatedAt":"2026-10-27","kind":"scenario","takeaways":["Two roles on one pair of nodes need two relationships, each with its own type."]},{"id":"neo4jbeginner-005","courseId":"neo4j-beginner","domain":"graph-modeling","topic":"Relationship type naming","prompt":"Your graph connects every person to every movie with one generic type, CONNECTED_TO. What does the data-modeling guide recommend instead?","hint":"Think about what a generic name hides from a search.","explain":"A search can only tell links apart by what their names reveal. Think about how much a single shared name for every link hides from the search.","source":"https://neo4j.com/docs/getting-started/data-modeling/guide-data-modeling/","interaction":{"type":"single"},"options":[{"id":"a","text":"Specific types that name the link, such as ACTED_IN and DIRECTED","why":"Specific types let Neo4j traverse only the connections that are relevant to the question."},{"id":"b","text":"One type per movie, such as APOLLO_13, so each movie has its own link","whyNot":"Naming types after one movie ties the model to that movie instead of to how people connect."},{"id":"c","text":"Lowercase types such as acted_in, which are easier to type","whyNot":"The guide recommends all capital letters with an underscore as separator for relationship types."},{"id":"d","text":"Keep CONNECTED_TO, since one generic type makes the queries shorter","whyNot":"A generic type makes Neo4j traverse connections that are not relevant to the question."}],"answer":"a","explanation":"Relationship types should be specific and written in capitals with underscores, so Neo4j traverses only the connections that matter.","concept":"Relationship types should be specific and written in capitals with underscores, so Neo4j traverses only the connections that matter.","rev":1,"updatedAt":"2026-10-27","kind":"scenario","takeaways":["Name each relationship type after the way its two entities connect."]}]