Drag and Drop Question You are designing an app for a bank. You must create entities for the app and configure relationships between entities: Which relationship types should you use? To answer…

Question

Exhibit

Answer Area

Explanation

This question tests the understanding of entity relationship types (1:N, N:N, N:1) in the context of designing an application for a bank, specifically within platforms like Microsoft Dataverse or Dynamics 365.

Approach. The correct approach involves analyzing each requirement to determine the cardinality of the relationship between the implied entities.

1. Requirement 1: 'The email attribute of the Loan Applicant entity must provide a look-up to the contact name and email.'

   • This describes a lookup field. In Dataverse (and similar systems), a lookup field on an entity (e.g., LoanApplicant) that points to another entity (e.g., a Contact or master Email record) represents a Many-to-One (N:1) relationship. Many LoanApplicant records (N) can refer to a single Contact or EmailMaster record (1).
   • Correct selection: N : 1

2. Requirement 2: 'Loan applicants can apply for one type of loan per application. Applicants can have more than one application.'

   • Let's analyze the relationship between LoanApplicant and Loan entities.
   • 'Applicants can have more than one application': This indicates that one LoanApplicant (1) can be associated with many Loan applications (N).
   • 'Loan applicants can apply for one type of loan per application': This sentence, especially if 'Loan applicants' is interpreted as plural in the context of a single application, suggests that a single Loan application could potentially involve multiple LoanApplicants (e.g., co-applicants). If one Loan (N) can have many LoanApplicants (N), combined with the previous point, it forms a Many-to-Many (N:N) relationship between LoanApplicant and Loan.
   • Correct selection: N : N

3. Requirement 3: 'Loans must be applied for for a single property.'

   • This describes the relationship between the Loan entity and the Property entity.
   • 'Loans must be applied for for a single property': This means that one Loan application (N) is associated with only one Property (1).
   • Conversely, a single Property can be associated with multiple Loan applications (e.g., refinancing, different applicants for the same property). Therefore, many Loans (N) relate to one Property (1).
   • Correct selection: N : 1

Common mistakes.

• common_mistake. A common mistake is misinterpreting the direction or cardinality of the relationship. For example:
• Confusing 1:N with N:1: For 'Loans must be applied for for a single property', selecting '1:N' would imply one Loan can be for many Propertys, which contradicts the requirement. Similarly, for the email lookup, selecting '1:N' would imply one LoanApplicant has many email lookup records, which is not how lookups typically function to a single master record.
• Misinterpreting N:N: For 'Loan applicants and applications', some might assume a simple '1:N' (one applicant, many loans). However, the phrasing 'Loan applicants can apply for one type of loan per application' hints at the possibility of multiple applicants per loan application, leading to an N:N relationship when combined with an applicant having multiple applications.
• Ignoring lookup field implications: For the first requirement, some might overlook that a lookup field itself implies an N:1 relationship from the referencing entity (many) to the referenced entity (one).

Concept tested. Entity Relationship Modeling (ERM), specifically understanding one-to-many (1:N), many-to-one (N:1), and many-to-many (N:N) relationship types and their application in data modeling for business applications, often in the context of platforms like Microsoft Dataverse or Dynamics 365.

No community discussion yet for this question.