You create a parent entity and a child entity.

Parental relationship behavior is required because ownership changes on the parent must cascade to all related child rows. In a one-to-many Dataverse relationship, Parental behavior treats the child records as dependent on the parent for supported cascading operations. When the Assign action changes the owner of the parent row, the related child rows are assigned to that new owner as part of the platform operation. Referential behavior preserves the link but does not provide the required assign cascade. Referential, Restrict Delete changes deletion behavior and still does not cause child ownership to follow the parent. “Restrict” by itself is not the relationship behavior option that implements the assignment requirement. Before applying Parental behavior, the designer should confirm that cascading other actions—especially delete, share, unshare, and reparent—matches the business rules, because Parental establishes a broader dependent-record model. If only selected actions should cascade, a configurable cascading relationship is preferable. Under the options supplied, Parental is the only complete answer. The Study Guide specifically measures the ability to “configure table relationships,” which includes selecting cascade behavior based on ownership and lifecycle requirements.

Study Guide reference/topic: “Build data models — Configure table relationships.” AB-410 Study Guide | Microsoft Learn technical reference