Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce CRT-403 Exam - Topic 1 Question 25 Discussion

Posted by Yvonne on Jul 08, 2023 at 09:19 PM

Cloud Kicks (CK) wants to simultaneously delete a Supplier's record and all Supplier ltem__c records if a

partnership ends with a supplier.

What solution could an app builder use to meet the requirement?

Suggested Answer: B

Get Premium CRT-403 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
48 comments · newest first
LY
Lynelle 11 months ago
Many-to-many won't work for this requirement, right?
CO
Coleen 11 months ago
Indirect lookup seems off for this scenario.
CA
Carin 12 months ago
Wait, can you really delete all related records like that?
JO
Jovita 12 months ago
Totally agree, D is the best option here.
OL
Olive 12 months ago
Master-detail is the way to go for cascading deletes!
MI
Millie 1 year ago
Hierarchical relationships seem more for user records, right? I doubt that's what they want for suppliers.
AN
Angella 1 year ago
I practiced a similar question where we had to delete related records, and I think the master-detail option was the answer there as well.
GL
Glory 1 year ago
I'm not entirely sure, but I feel like indirect lookup could be relevant here too, especially if we're dealing with external objects.
RE
Renea 1 year ago
I remember studying about relationships in Salesforce, and I think a master-detail relationship might be the right choice since it allows for cascading deletes.
TH
Thomasena 1 year ago
The project statement of work is definitely the right answer. It's the key document that outlines the deliverables and scope of the project.
LU
Luz 1 year ago
I remember a practice question that involved different types of nav elements, and I think Utility makes the most sense here.
DO
Dorian 1 year ago
Hmm, I'm a bit unsure about this one. The options seem similar, so I'll need to review my notes on the rules of evidence to make sure I understand the differences.
SH
Shelton 1 year ago
D. Master-detail is the correct answer, no doubt about it. Now, if only I could remember the difference between a lookup and a master-detail relationship...
SH
Shawn 1 year ago
↳ replying to Shelton
Lookup relationships are used when you don't want to cascade delete related records.
CO
Colton 1 year ago
↳ replying to Shelton
Master-detail relationships are used when you want to cascade delete related records.
TO
Tony 1 year ago
↳ replying to Shelton
D) Master-detail
DO
Domitila 1 year ago
↳ replying to Shelton
C) Hierarchical
RA
Raina 1 year ago
↳ replying to Shelton
B) Indirect lookup
DO
Donte 1 year ago
↳ replying to Shelton
A) Many-to-many
KR
Krystina 1 year ago
Haha, I bet the exam writer is really hoping we don't choose A. Many-to-many. That would just be a mess to try and delete everything at once!
ME
Melodie 1 year ago
↳ replying to Krystina
User 3: Definitely not A) Many-to-many, that would be a nightmare to manage.
CE
Celia 1 year ago
↳ replying to Krystina
User 2: Yeah, that makes sense. It would allow for cascading deletes.
EA
Earleen 1 year ago
↳ replying to Krystina
User 1: I think the best solution would be D) Master-detail.
KA
Kate 1 year ago
Hmm, I was considering B. Indirect lookup, but I guess that wouldn't work since we need to delete the records simultaneously. D. Master-detail is the way to go.
LU
Luisa 1 year ago
↳ replying to Kate
Yes, Master-detail relationship allows for cascading deletes which is perfect for this requirement.
DE
Deandrea 1 year ago
↳ replying to Kate
I agree, with Master-detail relationship, we can easily delete the related records at the same time.
JA
Janine 1 year ago
↳ replying to Kate
I think D. Master-detail is the best solution for this scenario.
SA
Salome 2 years ago
I think the answer is D. Master-detail. It makes sense to use this relationship type to delete the Supplier and all Supplier Item records together.
EL
Eliseo 1 year ago
↳ replying to Salome
I think D) Master-detail is the most suitable relationship type for this requirement.
EL
Eladia 1 year ago
↳ replying to Salome
Yes, D) Master-detail is the best option for this scenario.
FE
Felicidad 1 year ago
↳ replying to Salome
I agree, D) Master-detail is the correct choice.
GL
Gladys 1 year ago
↳ replying to Salome
D) Master-detail
LE
Lenna 1 year ago
↳ replying to Salome
C) Hierarchical
DA
Daniel 1 year ago
↳ replying to Salome
B) Indirect lookup
NG
Nguyet 1 year ago
↳ replying to Salome
A) Many-to-many
MA
Mammie 1 year ago
↳ replying to Salome
That makes sense, D) Master-detail is the best option for this requirement.
HO
Hollis 1 year ago
↳ replying to Salome
Yes, D) Master-detail ensures that all related records are deleted when the parent record is deleted.
CR
Cristy 1 year ago
↳ replying to Salome
I agree, D) Master-detail is the correct choice.
LE
Leslee 1 year ago
↳ replying to Salome
D) Master-detail
AP
Apolonia 1 year ago
↳ replying to Salome
C) Hierarchical
TE
Tegan 1 year ago
↳ replying to Salome
B) Indirect lookup
RO
Robt 1 year ago
↳ replying to Salome
A) Many-to-many
DA
Dahlia 2 years ago
I'm not sure, but I think A) Many-to-many could also work if we set up a junction object to link the Supplier and Supplier Item records.
TR
Truman 2 years ago
I agree with Marion, because with Master-detail relationship, when the parent record is deleted, all related child records are also deleted.
MA
Marion 2 years ago
I think the answer is D) Master-detail.
LA
Lashawna 2 years ago
I'm not sure, but I think A) Many-to-many could also work because it allows for deletion of related records.
DA
Dana 2 years ago
I agree with Lisbeth, because with Master-detail relationship, when the parent record is deleted, all related child records are also deleted.
LI
Lisbeth 2 years ago
I think the answer is D) Master-detail.
0/2000 characters

Save Cancel