Q: 1
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 administrator configure to meet this requirement?
Choose 2 answers
Options
Discussion
That's B and D. Custom object is needed, and lookup prevents the cascade delete issue from master-detail relationships.
Its B and D. C's a distractor since there's no standard design object, and A (master-detail) would break the "can't be deleted" part by allowing cascades. Pretty sure this is how it's covered in the latest official material.
I think it's B and C. You'd need a custom object for shoe designs, but if there's a standard object for designs you can leverage that too. Not 100% on this since product relationships might complicate it. Agree?
Did anyone else notice the answer key lists B and C, but there isn't a standard object for shoe designs? Seems like it should be B and D because custom object plus lookup avoids cascade deletes. Thoughts?
C tbh. I thought you could use the standard object for designs if it's just tracking, and relate it to products accordingly. Maybe check the official study guide or play in a practice org to confirm.
B/D? C is tempting but no standard object for designs so I think that's just there as a trap.
B and D tbh. Custom object lets you track shoe designs since there's no standard object for that, and a lookup field avoids the cascade delete problem with master-detail. I've seen official practice questions highlight this logic. If you want to double check, the official admin study guide spells it out pretty clearly. Agree?
Probably B and D. B for the custom object is a must since there's no standard shoe design object, and D (lookup) avoids the cascade delete you'd get from A (master-detail). C feels like a trap since 'designs' isn't a standard object. Pretty sure that's what they test for in similar questions, but let me know if you see it differently.
B D, official guide covers these. Custom object for shoe designs and lookup field stops unwanted deletes, just like in practice tests.
Probably B and D. Custom object is needed since there's no standard one for designs, and lookup field avoids auto-deletion if the product is deleted. Saw this setup in exam reports, seems right unless there's more info I'm missing.
Be respectful. No spam.
