Universal Containers (UC) wants to lower its shipping cost while making the shipping process more efficient. The Distribution Officer advises UC to…

The business requirement is for multiple Account records to share a single Global Address record. This describes a many-to-one relationship, where Account is the "many" side and Global Address is the "one" side. To model this, the relationship field must be created on the "many" object (Account) and point to the "one" object (Global Address). A lookup relationship is the correct choice as it creates this association. A master-detail relationship is not possible because a standard object (Account) cannot be on the detail side of a relationship with a custom object (Global Address).

1. Salesforce Help

Object Relationships Overview: This document explains that to create a one-to-many relationship

you create a lookup or master-detail field on the object that is intended to be the "many" side. In this scenario

Account is the "many" side.

2. Salesforce Help

Create a Lookup Relationship: "You can use lookup fields to create one-to-many relationships... For example

you can create a one-to-many relationship between the account and case objects by creating a lookup field on the case object that looks up to the account object." This confirms the field placement on the "many" side (Account in our case).

3. Salesforce Help

Considerations for Relationships: Under the "Master-Detail Relationship" section

the documentation explicitly states: "You can create master-detail relationships between custom objects or between a custom object and a standard object. However

the standard object cannot be on the detail side of a relationship with a custom object." This rule directly invalidates option D.

4. Salesforce Developer Documentation

Relationships Among Objects: "In a one-to-many relationship

a single object is the “one” side

and many other objects are the “many” side... You can create this relationship by adding a lookup or master-detail relationship field to the objects on the “many” side." This reinforces that the field must be on the Account object.