Cloud Kicks has a custom object called Shipments.

When relating two objects where the child records must persist even if the parent record is deleted, a Lookup Relationship is the correct choice18. In this scenario, the Shipment object should have a lookup field pointing to the Account. Unlike a Master-Detail relationship (Option B), which automatically deletes child records (cascade delete) when the master is deleted, a Lookup relationship allows the child record to remain in the system, either by clearing the lookup field or simply leaving it as is. Option A and D are architecturally incorrect because the relationship field is always created on the "child" or "many" side of the relationship (Shipments) to point to the "parent" (Account). Using a Lookup relationship ensures data retention for historical shipment tracking while still allowing the shipment items to be visible via a related list on the Account page.