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…

Question

Options

• AAdd a custom master-detail field for shoe designs on the Product object,
• BCreate a custom object for shoe designs.
• CUse the standard object for designs.
• DConfigure a custom lookup field for shoe designs on the Product object.

• A
  14% (9)
• B
  78% (49)
• D
  8% (5)

Explanation

Note: The listed correct answer (B, C) appears to contain an error. Option C - "Use the standard object for designs" - is incorrect because Salesforce has no standard "Designs" object. The actual correct answers are B and D.

B (Create a custom object for shoe designs) is required because no standard Salesforce object exists for tracking shoe designs. A custom object lets you define the fields, stages, and behavior needed for this use case, supporting multiple design records per product.

D (Configure a custom lookup field for shoe designs on the Product object) is the right relationship type because a lookup relationship allows shoe design records to exist independently - they are not cascade-deleted if the parent Product is deleted. This satisfies the "unable to be deleted" requirement.

Why A is wrong: A master-detail relationship triggers cascade delete - if the Product (master) is deleted, all linked shoe designs (detail records) are automatically deleted too, violating the deletion restriction.

Why C is wrong: There is no standard Salesforce object called "Designs." This distractor tests whether you know standard vs. custom object availability.

Memory tip: Think "Lookup = loose coupling = lives on." When a child record must survive independently (not be deleted with the parent), choose a lookup. When you want the child tied to the master's fate, choose master-detail.

No community discussion yet for this question.