Correct Answer: C
Dataverse defines the two basic types of relationships between tables: One-to-Many (1:N) and Many-to-Many (N:N).
A One-to-Many relationship is a Parent-Child relationship, like between a company and multiple products that it supplies or one building blueprint that can be used for multiple cases. It is a One-to-Many relationship for a Blueprints record. For the related Cases record, this relation is Many-to-One. When you create such a relationship between tables, the Dataverse automatically adds a Lookup column in a child or related table (Cases).
Option A is incorrect because Dataverse does not support the One-to-One (1:1) relationship between tables. It provides only One-to-Many (1:N), Many-to-One (N:1), and Many-to-Many (N:N).
Option B is incorrect because the relationship is Many-to-One (N:1) from the Cases table side, and One-to-Many (1:N) relationship is from the Blueprints side.
Option D is incorrect because the Cases and Blueprints tables` relationship is Many-to-One (N:1) but not Many-to-Many (N:N).
For more information about the Dataverse types of table relationship, please visit the below URLs: