Salesforce CRT-403 Exam - 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?

AMany-to-many

BIndirect lookup

CHierarchical

DMaster-detail

Show Suggested Answer

Suggested Answer: B

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

Limited Time Offer

25%

Off

Get Premium CRT-403 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lynelle

3 months ago

Many-to-many won't work for this requirement, right?

upvoted 0 times

...

Coleen

3 months ago

Indirect lookup seems off for this scenario.

upvoted 0 times

...

Carin

4 months ago

Wait, can you really delete all related records like that?

upvoted 0 times

...

Jovita

4 months ago

Totally agree, D is the best option here.

upvoted 0 times

...

Olive

4 months ago

Master-detail is the way to go for cascading deletes!

upvoted 0 times

...

Millie

4 months ago

Hierarchical relationships seem more for user records, right? I doubt that's what they want for suppliers.

upvoted 0 times

...

Angella

4 months 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.

upvoted 0 times

...

Glory

5 months 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.

upvoted 0 times

...

Renea

5 months 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.

upvoted 0 times

...

Thomasena

5 months 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.

upvoted 0 times

...

Luz

5 months ago

I remember a practice question that involved different types of nav elements, and I think Utility makes the most sense here.

upvoted 0 times

...

Dorian

5 months 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.

upvoted 0 times

...

Shelton

10 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

Shawn

8 months ago

Lookup relationships are used when you don't want to cascade delete related records.

upvoted 0 times

...

Colton

8 months ago

Master-detail relationships are used when you want to cascade delete related records.

upvoted 0 times

...

Tony

8 months ago

D) Master-detail

upvoted 0 times

...

Domitila

9 months ago

C) Hierarchical

upvoted 0 times

...

Raina

9 months ago

B) Indirect lookup

upvoted 0 times

...

Donte

9 months ago

A) Many-to-many

upvoted 0 times

...

Krystina

10 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

9 months ago

User 3: Definitely not A) Many-to-many, that would be a nightmare to manage.

upvoted 0 times

...

Celia

9 months ago

User 2: Yeah, that makes sense. It would allow for cascading deletes.

upvoted 0 times

...

Earleen

9 months ago

User 1: I think the best solution would be D) Master-detail.

upvoted 0 times

...

Kate

10 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

9 months ago

Yes, Master-detail relationship allows for cascading deletes which is perfect for this requirement.

upvoted 0 times

...

Deandrea

9 months ago

I agree, with Master-detail relationship, we can easily delete the related records at the same time.

upvoted 0 times

...

Janine

10 months ago

I think D. Master-detail is the best solution for this scenario.

upvoted 0 times

...

Salome

10 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

Eliseo

8 months ago

I think D) Master-detail is the most suitable relationship type for this requirement.

upvoted 0 times

...

Eladia

8 months ago

Yes, D) Master-detail is the best option for this scenario.

upvoted 0 times

...

Felicidad

8 months ago

I agree, D) Master-detail is the correct choice.

upvoted 0 times

...

Gladys

8 months ago

D) Master-detail

upvoted 0 times

...

Lenna

8 months ago

C) Hierarchical

upvoted 0 times

...

Daniel

8 months ago

B) Indirect lookup

upvoted 0 times

...

Nguyet

8 months ago

A) Many-to-many

upvoted 0 times

...

Mammie

8 months ago

That makes sense, D) Master-detail is the best option for this requirement.

upvoted 0 times

...

Hollis

8 months ago

Yes, D) Master-detail ensures that all related records are deleted when the parent record is deleted.

upvoted 0 times

...

Cristy

8 months ago

I agree, D) Master-detail is the correct choice.

upvoted 0 times

...

Leslee

8 months ago

D) Master-detail

upvoted 0 times

...

Apolonia

9 months ago

C) Hierarchical

upvoted 0 times

...

Tegan

9 months ago

B) Indirect lookup

upvoted 0 times

...

Robt

9 months ago

A) Many-to-many

upvoted 0 times

...

Dahlia

10 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

10 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

11 months ago

I think the answer is D) Master-detail.

upvoted 0 times

...

Lashawna

11 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

11 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

11 months ago

I think the answer is D) Master-detail.

upvoted 0 times

...