Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-403 Topic 1 Question 25 Discussion

Actual exam question for Salesforce's CRT-403 exam
Question #: 25
Topic #: 1
[All CRT-403 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Shelton
1 months 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...
upvoted 0 times
Colton
2 days ago
Master-detail relationships are used when you want to cascade delete related records.
upvoted 0 times
...
Tony
6 days ago
D) Master-detail
upvoted 0 times
...
Domitila
21 days ago
C) Hierarchical
upvoted 0 times
...
Raina
23 days ago
B) Indirect lookup
upvoted 0 times
...
Donte
24 days ago
A) Many-to-many
upvoted 0 times
...
...
Krystina
2 months 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!
upvoted 0 times
Melodie
15 days ago
User 3: Definitely not A) Many-to-many, that would be a nightmare to manage.
upvoted 0 times
...
Celia
29 days ago
User 2: Yeah, that makes sense. It would allow for cascading deletes.
upvoted 0 times
...
Earleen
1 months ago
User 1: I think the best solution would be D) Master-detail.
upvoted 0 times
...
...
Kate
2 months 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.
upvoted 0 times
Luisa
21 days ago
Yes, Master-detail relationship allows for cascading deletes which is perfect for this requirement.
upvoted 0 times
...
Deandrea
23 days ago
I agree, with Master-detail relationship, we can easily delete the related records at the same time.
upvoted 0 times
...
Janine
1 months ago
I think D. Master-detail is the best solution for this scenario.
upvoted 0 times
...
...
Salome
2 months 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.
upvoted 0 times
Nguyet
40 minutes ago
A) Many-to-many
upvoted 0 times
...
Mammie
1 days ago
That makes sense, D) Master-detail is the best option for this requirement.
upvoted 0 times
...
Hollis
2 days ago
Yes, D) Master-detail ensures that all related records are deleted when the parent record is deleted.
upvoted 0 times
...
Cristy
5 days ago
I agree, D) Master-detail is the correct choice.
upvoted 0 times
...
Leslee
6 days ago
D) Master-detail
upvoted 0 times
...
Apolonia
13 days ago
C) Hierarchical
upvoted 0 times
...
Tegan
18 days ago
B) Indirect lookup
upvoted 0 times
...
Robt
1 months ago
A) Many-to-many
upvoted 0 times
...
...
Dahlia
2 months 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.
upvoted 0 times
...
Truman
2 months ago
I agree with Marion, because with Master-detail relationship, when the parent record is deleted, all related child records are also deleted.
upvoted 0 times
...
Marion
2 months ago
I think the answer is D) Master-detail.
upvoted 0 times
...
Lashawna
3 months ago
I'm not sure, but I think A) Many-to-many could also work because it allows for deletion of related records.
upvoted 0 times
...
Dana
3 months ago
I agree with Lisbeth, because with Master-detail relationship, when the parent record is deleted, all related child records are also deleted.
upvoted 0 times
...
Lisbeth
3 months ago
I think the answer is D) Master-detail.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77