Correct Answers: B and D
Dataverse identifies two types of relationships between tables: One-to-Many (1:N) and Many-to-Many (N:N).
A One-to-Many relationship is between a record in a primary (or parent) table and many records in the related (or child) table. This relationship type is also called the Parent-Child. A good example of this type is a relationship between a customer and the orders: each customer can have multiple orders.
A Many-to-Many relationship is when multiple records from one table have relationships with the multiple records in another table and vice versa. An example of this type is a relationship between students and classes: each student enrolls in multiple classes, and each class has multiple students enrolled.
When users create a Many-to-Many relationship, the Dataverse creates a specific hidden intersect matching table between the records in two tables. After you create a N:N relationship, you cannot edit both tables.
You can avoid this limitation by creating a new custom table and establish two One-to-Many relationships between a new table and each of the other tables. By introducing the third table, you will avoid the limitation mentioned above.
Another possible solution is connections. Connections are a particular case for the Many-to-Many relationships. They are flexible and don`t have the limitations of the N:N relationship.
All other options are incorrect.
For more information about Dataverse table relationships, please visit the below URLs:
https://docs.microsoft.com/en-us/learn/modules/create-relationship-between-cds-entities/4-many-to-many
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/configure-connection-roles