Ursa Major Solar wants to create a relationship between the standard Contact object and a custom Solar Project object. Contact s can potentially be related to multiple Solar Project objects, and a Solar Project can have multiple Contacts associated with it.
How should an app builder configure the data model?
To create a many-to-many relationship between standard Contact objects and custom Solar Project objects, a junction object is necessary. The correct approach is to create a new custom junction object that will have two Lookup relationships: one pointing to the Contact object and the other to the Solar Project object. This establishes the necessary connections without the constraints of Master-detail relationships, particularly since Master-detail relationships involving standard objects as the parent are not feasible in this instance.
Two MD relationship is required on the child obj (new custom obj) to its two parent objs (Contact, Solar Project) to achieve M-M relationship.
Junction object is needed
Agree: https://www.salesforceben.com/what-is-a-junction-object-in-salesforce/
Shouldn't the Ans be D beacause Master detail relationships are allowed only in the following scenarios: - Standard Object to Custom Object - Custom Object to Custom Object Therefore Solar Project can have multiple Contacts is Custom to Standard so MD relationship not allowed