Which type of relationship should you create?

You plan to create a country entity that contains one record for each country in the world.
You need to track which countries a contact visited. No additional data will be tracked.
Which type of relationship should you create?
A. a many-to-many (N:N) relationship from the contact to the country
B. a one-to-many (1 :N) relationship from the country to the contact
C. a many-to-many (N:N) relationship from the contact to the country that has a relationship behavior type of Parental
D. a one-to-many (1 :N) relationship from the contact to the country

microsoft-exams

6 thoughts on “Which type of relationship should you create?

  1. The answer is A. The first sentence states the country entity will have one entry for each country. If you do a 1:N The country ‘Australia’ could only be linked to one contact. The statement that no additional data needs to be tracked also tells you that its ok to use a N:N which creates an intersect entity for which you cannot add custom attributes.
    Its not C as you can’t apply parental behaviour to an N:N relationship and you wouldn’t want to anyway as deletion or deactivation of the contact would lead to te same occuring to the country making it not accessble to the other records.

  2. Answer is: D
    last statement in question is: “No additional data will be tracked”

    Reference: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/customize-entity-relationship-metadata#BKMK_ManyToManyRelationships

    Creating a many-to-many entity relationship creates a new intersect entity where the EntityMetadata.IsIntersect property is true. Records for this entity track each individual many-to-many relationship. You cannot add custom attributes to intersect entities.

    1. The answer is A. The first sentence states the country entity will have one entry for each country. If you do a 1:N The country ‘Australia’ could only be linked to one contact. The statement that no additional data needs to be tracked also tells you that its ok to use a N:N which creates an intersect entity for which you cannot add custom attributes.
      Its not C as you can’t apply parental behaviour to an N:N relationship and you wouldn’t want to anyway as deletion or deactivation of the contact would lead to te same occuring to the country making it not accessble to the other records.

  3. Correct answer is: D.
    with this link, the question is answered enough, no need additional data to track.
    The question here focus on ‘You need to track which countries a contact visited”, not reverse back, as the last statement say: “No additional data will be tracked.”, it means no need to reverse back the link.

  4. “A”. It must be N:N relationship, because each country can be visited by different contacts, and each contact can visit different countries

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.