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, drag the appropriate relationship types to the correct requirements. Each relationship type 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.
| Entity | Requirements |
|--------|--------------|
| LoanApplicant | This entity represents a person who is applying for a loan. The entity must contain an attribute named Email. This attribute must provide look-up for the name of the applicant. |
| Loan | This entity represents a loan application. Loan applicants may apply for one loan per application. Loan applicants may have more than one active application. |
| Property | This entity represents the property that the applicant intends to purchase. |
Explanation
Email look-up to the contact: N:1. The LoanApplicant table gets a lookup column to Contact; many loan applicants can point to one contact, which is a many-to-one relationship seen from LoanApplicant.
One type of loan per application, more than one application per applicant: N:N. Applicants and loan applications/types relate in both directions (an applicant can have many applications, and a loan type can be applied for by many applicants), which needs a many-to-many relationship.
Loans applied for a single property: N:1. Each loan has a lookup to exactly one property, while one property can be referenced by many loans, so the relationship from Loan to Property is many-to-one.
