Exam PL-400 topic 2 question 10 discussion

DRAG DROP -
A company is creating a new system based on Microsoft Dataverse.
You need to select the features that meet the company's requirements.
Which options should you use? To answer, drag the appropriate options to the correct requirements. Each option may be used once, more than once, or not at all.
You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

Suggested Answer:
Box 1: one-to-many relationship -
Only one (1:N) self-referential relationship per table can be set as hierarchical. In a self-referential relationship the primary table and the related table must be of the same type.

Box 2: one-to-many relationship -
1:N (One-to-Many) - A table relationship where one table row for the Primary table can be associated to many other Related table rows because of a lookup column on the related table.
Note: The N:1 (many-to-one) relationship type exists in the user interface because the designer shows you a view grouped by tables. 1:N relationships actually exist between tables and refer to each table as either a Primary/Current table or Related table. The related table, sometimes called the child table, has a lookup column that allows storing a reference to a row from the primary table, sometimes called the parent table. A N:1 relationship is just a 1:N relationship viewed from the related table.
Box 3: many-to-many relationship
N:N (Many-to-Many) - A table relationship that depends on a special Relationship table, sometimes called an Intersect table, so that many rows of one table can be related to many rows of another table.
When viewing rows of either table in a N:N relationship you can see a list of any rows of the other table that are related to it.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-entity-relationships https://docs.microsoft.com/en-us/power-apps/maker/data-platform/visualize-hierarchical-data