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

Question

Options

• ACreate a Custom Object for shoe design.
• BConfigure a Custom Lookup Field for shoe design on the product object.
• CAdd a custom master detail field for shoe design on the Product Object.
• DUse the Standard Object for designs.

• A
  80% (37)
• B
  7% (3)
• D
  13% (6)

Explanation

Creating a Custom Object (A) for shoe designs is necessary because Salesforce has no standard object for this entity, giving administrators full control over fields, permissions, and behavior. Adding a Master-Detail field (C) on the Product object then ties each shoe design tightly to a product - the Master-Detail relationship enforces ownership so that designs cannot exist as orphaned records and their deletion is controlled through the parent's security model, satisfying the "unable to be deleted" requirement.

Option B is wrong because a Lookup field creates a loose, optional relationship - shoe designs could exist without a linked product and could be freely deleted, which violates the requirement. Option D is wrong because Salesforce has no built-in standard object for "designs"; using a standard object is not an option here, and even if it were, it wouldn't give the necessary relationship control.

Memory tip: Think "Master = Must" - a Master-Detail relationship must have a parent, locks the child's lifecycle to the parent, and pairs with a custom object when no standard object fits the business need.

No community discussion yet for this question.