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 foreign key field must be placed on the object on the "many" side (Account) and point to the "one" side (Global Address). A lookup relationship is the most appropriate choice. It creates a loosely coupled relationship, allowing Account and Global Address records to have separate owners and sharing settings. This prevents unintended consequences, such as deleting an address causing the deletion of all associated accounts.

A. Add a master-detail field on the Global Address object to the Account object. This creates the inverse relationship (one Account to many Global Addresses), which does not allow sharing a single address across multiple accounts.
B. Add a lookup field on the Global Address object to the Account object. Similar to option A, this models the relationship in the wrong direction and does not meet the requirement for sharing an address.
D. Add a master-detail field on the Account object to the Global Address object. This option is not possible. A standard object, such as Account, cannot be the detail object in a master-detail relationship with a custom object.

1. Salesforce Help, "Create Object Relationships": This document outlines the types of relationships. It explains that to create a many-to-one relationship, you create the lookup or master-detail field on the object that will be the "many" side. In this case, Account is the "many" side.

2. Salesforce Help, "Considerations for Relationships", Section: "Master-Detail Relationship Considerations": This official documentation explicitly states, "You can't create a master-detail relationship in which a standard object is the detail." This rule makes option D technically impossible to implement.

3. Salesforce Platform Developer I Certification Guide, "Data Modeling and Management" section: This guide emphasizes understanding the implications of relationship types. A lookup is described as a link between two objects that does not affect deletion, ownership, or security, which is the most efficient and logical model for sharing a common address record without creating dependencies that could lead to data loss.