Exam PL-400 topic 2 question 26 discussion

DFH is the answer

C, F, and D are the actions that should be performed to meet the requirements. Create an intersect entity named ContactRegion and create 1:N relationships to Contact and Region. This will allow multiple contacts to have a relationship to multiple regions and also track the date of the visit. Create the Region entity. This will store the different regions that the company tracks. On the main form for ContactRegion, add a date field for the visit date. This will allow the company to track the date the client traveled to the region. Option H suggests creating an intersect entity named ContactRegion and creating N:1 relationships to Contact and Region. This would not be appropriate in this scenario because it would not allow multiple regions to be associated with a single contact, which is a requirement of the problem statement.

If D is selected as an option, then H should be selected instead of C, because Lookup fields represent N:1 relationships, so it is not possible to have lookup fields for Contact and Region in the "ContactRegion" table if the relationships that were created to those tables were "1:N"

not H: The intersect entity ContactRegion should have 1:N relationships to Contact and Region, not N:1 relationships.

Answer is CDF how can you create lookup without creating an intersect entity named ContactRegion mentioned in step D hence C is first step, then D and F

BASICALLY D IS THE SAME AS H, LOOKUPS ARE N;1 RELATIONSHIPS.

Should N-1 instead of 1-N, so the answer is DFH

DFH is the ans

In exam 09/23/2023

The correct three actions are C, D, and F. Explanation: Here are the steps on how to create the entities and relationships to meet the requirements: 1. Create the Contact entity. 2. Create the Region entity. 3. Create an intersect entity named ContactRegion and create 1:N relationships to Contact and Region. 4. On the main form for ContactRegion, add lookup fields for Contact and Region, and a date field for the visit date.

1.Create the Region entity. 2. Create an intersect entity named ContactRegion and create N:1 relationships to Contact and Region. 3. On the main form for ContactRegion, add lookup fields for Contact and Region, and a date field for the visitdate

absolutely DFH. F - Create the Region entity. H. Create an intersect entity named ContactRegion and create N:1 relationships to Contact and Region. D. On the main form for ContactRegion, add lookup fields for Contact and Region, and a date field for the visit date.

Order should be F, H and D https://carldesouza.com/understanding-intersect-entities-and-nn-relationships-in-dynamics-365/

- Region table needs to be created. - Contact is a system table. - Creating an interception table N:1 manually named ContactRegion. Sample: Contact A -> 2 ContactRegion (2 visits for a country on 2 different dates) > 1 Region. 1:N does not allow this.

This question was on my 4/7/23 exam

ContactRegion -- N:1 -- Region => A record of ContactRegion has only one Region. A Region could be in many records of ContactRegion ContactRegion -- N:1 -- Contact

It's DFH, we are creating two lookups inside the ContactRegion to the Contact and Region, and not vice versa.