Cloud Kicks wants to track shoe designs by products. Shoe designs should be unable to be deleted, and there can be multiple designs for one product across various stages. Which two steps should the…

Creating a custom object for "Shoe Designs" provides a dedicated entity to store all relevant information about each design, fulfilling the requirement to track them independently and with multiple stages.

Establishing a master-detail relationship where Product is the master and Shoe Design is the detail ensures that Shoe Design records are tightly coupled to Product records, supporting multiple designs per product. This relationship type enforces strong data integrity, where the deletion of a product would cascade to its designs, thus preventing orphaned records and signifying a higher level of data dependency than a lookup.

A custom lookup field would allow Shoe Designs to be linked to Products but would permit deletion of Shoe Design records independently, even if related to a Product, which offers looser data coupling and does not align as strongly with the requirement for designs to be "unable to be deleted" as a master-detail relationship.

Using a standard object for designs is generally not feasible unless an existing standard object can be repurposed without conflicting with its original use and data model, which is unlikely for a specific concept like "shoe designs."