Ursa Major Solar wants to create a relationship between the standard Contact object and a custom Solar Project object Contacts potentially be related…

The scenario requires a many-to-many relationship, where one Contact can be associated with multiple Solar Projects, and one Solar Project can be associated with multiple Contacts. The standard and most robust method to model this in Salesforce is by creating a third custom object, known as a junction object. This junction object should have two master-detail relationships: one to the Contact object and one to the Solar Project object. This configuration creates the strongest-typed relationship, enables cascading record deletion, inherits security from parent records, and allows for roll-up summary fields on both master objects.

A. One Master-detail relationship on Contact and one Master-detail relationship on Solar Project: This configuration does not create a junction object and cannot model a many-to-many relationship. It describes two separate, unrelated one-to-many relationships.

B. Two Lookup relationships on a new custom object: While this also creates a many-to-many relationship, it is a loosely coupled version. The master-detail relationship (Option D) is the standard, recommended pattern unless specific requirements (like separate ownership or preventing cascading deletes) exist.

C. One Lookup relationship on Contact and one Lookup relationship on Solar Project: This model fails to meet the requirement. A lookup field on the Contact object would only allow each Contact to relate to a single Solar Project, which contradicts the scenario.

1. Salesforce Help, "Create Object Relationships": This document outlines the different relationship types. For many-to-many, it states, "To create a many-to-many relationship, you simply create a custom junction object... Then, on the junction object, you create two master-detail relationships." This directly supports creating a new object with two master-detail relationships.

2. Salesforce Help, "Object Relationships Overview": Under the "Master-Detail" section, it explains, "Use a master-detail relationship to model a many-to-many relationship between any two objects." It then describes the use of a junction object with two master-detail fields as the method for implementation.

3. Trailhead, "Data Modeling" Module, "Create Object Relationships" Unit: This official training module explicitly teaches the creation of a many-to-many relationship using a junction object that contains two master-detail relationship fields, one for each object being related.