Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce CRT-403 Exam - Topic 5 Question 65 Discussion

An app builder is creating a custom object called Testimonial__c and wants toconnect Testimonial__c records with both the submitter'sContact record and Account record. If the Account is deleted, the Testimonial__c should also be deleted. If the Contact is deleted, but theAccount remains, the Testimonial__c should remain.How should this be accomplished?
B) Create a master-detail relationship from Testimonial__c to Accountand a lookup relationship from Testimonial__c to Contact.
A) Make both the Contact and Account fields required on the Testimonial__c object and create lookup relationships fromTestimonial__c to Contact and to Account.
C) Make Testimonial__c a junction object between Account and Contact using master-detail relationships.
D) Create a lookup relationship from Testimonial__c to Account and a master-detail relationship from Testimonial__c to Contact.

Salesforce CRT-403 Exam - Topic 5 Question 65 Discussion

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

An app builder is creating a custom object called Testimonial__c and wants toconnect Testimonial__c records with both the submitter's

Contact record and Account record. If the Account is deleted, the Testimonial__c should also be deleted. If the Contact is deleted, but the

Account remains, the Testimonial__c should remain.

How should this be accomplished?

Show Suggested Answer Hide Answer
Suggested Answer: B

To connect Testimonial__c records with both the submitter's Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another.Source


by Christiane at Apr 30, 2025, 04:15 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Maurine
5 months ago
I’m not sure about C, it sounds too complicated for this scenario.
upvoted 0 times
...
Christiane
6 months ago
I disagree, I think option A is better for required fields.
upvoted 0 times
...
Kristeen
6 months ago
Option B seems right, master-detail for Account is key!
upvoted 0 times
...
Nana
6 months ago
Definitely B, that way the Testimonial__c will be deleted with the Account.
upvoted 0 times
...
Belen
6 months ago
I’m surprised this is even a question, it’s pretty straightforward!
upvoted 0 times
...
Lynelle
6 months ago
I’m a bit confused about the junction object idea in option C. I don’t think we need that for just connecting these two records, right?
upvoted 0 times
...
Lashandra
7 months ago
I practiced a similar question where we had to decide between lookup and master-detail, and I feel like option B is the right choice here too.
upvoted 0 times
...
Jina
7 months ago
I'm not entirely sure, but I think a lookup relationship for Contact would mean the Testimonial__c stays even if the Contact is deleted.
upvoted 0 times
...
Jean
7 months ago
I remember that master-detail relationships allow for cascading deletes, so I think option B makes sense for the Account part.
upvoted 0 times
...
Jamal
7 months ago
I think I've got it! Option B is the way to go. Master-detail to Account for the delete behavior, and lookup to Contact to keep the Testimonial if just the Contact is deleted.
upvoted 0 times
...
Shaun
8 months ago
I'm a bit confused on the differences between lookup and master-detail here. I'll need to review those relationship types again before deciding.
upvoted 0 times
...
Dick
8 months ago
Okay, let me walk through the options. I'm leaning towards B - a master-detail to Account and a lookup to Contact. That should give us the right delete behavior.
upvoted 0 times
...
Tony
8 months ago
Hmm, I think the key is understanding the delete behavior we want. If the Account is deleted, the Testimonial should go too, but not if just the Contact is deleted.
upvoted 0 times
...
Meaghan
8 months ago
This seems like a tricky one. I'll need to think through the relationship requirements carefully.
upvoted 0 times
...
Ivette
12 months ago
I think option D makes the most sense, as it specifies the relationships clearly.
upvoted 0 times
...
Alonzo
1 year ago
I'm leaning towards option C because it involves a junction object.
upvoted 0 times
...
Darrin
1 year ago
Gotta love these tricky Salesforce questions. It's like they're trying to trip us up with all these relationship types. Where's the 'Throw the whole thing out and start over' option?
upvoted 0 times
Joesph
11 months ago
D) Create a lookup relationship from Testimonial__c to Account and a master-detail relationship from Testimonial__c to Contact.
upvoted 0 times
...
Keneth
11 months ago
C) Make Testimonial__c a junction object between Account and Contact using master-detail relationships.
upvoted 0 times
...
Jennifer
11 months ago
B) Create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.
upvoted 0 times
...
Elin
11 months ago
A) Make both the Contact and Account fields required on the Testimonial__c object and create lookup relationships from Testimonial__c to Contact and to Account.
upvoted 0 times
...
...
Alisha
1 year ago
I disagree, I believe option B is more appropriate.
upvoted 0 times
...
Trina
1 year ago
I think option A is the best choice.
upvoted 0 times
...
Charolette
1 year ago
This is a classic 'keep the good stuff, delete the bad stuff' scenario. Option B is the clear winner here.
upvoted 0 times
Raylene
1 year ago
That way, if the Account is deleted, the Testimonial__c record will also be deleted.
upvoted 0 times
...
Raelene
1 year ago
I agree, creating a master-detail relationship with Account makes sense.
upvoted 0 times
...
Audra
1 year ago
I think option B is the best choice.
upvoted 0 times
...
...
Martina
1 year ago
Wait, is this question asking us to build an app about testimonials for a dating site? 'Cause if so, I have some ideas...
upvoted 0 times
...
Dannie
1 year ago
Option B seems like the way to go. That way, if the Account gets deleted, the Testimonial__c goes with it, but if the Contact gets deleted, the Testimonial__c sticks around.
upvoted 0 times
Alberta
1 year ago
Having a master-detail relationship to the Account will ensure the Testimonial__c record is deleted if the Account is deleted.
upvoted 0 times
...
Lezlie
1 year ago
It's important to make sure the Testimonial__c record stays connected to the Account.
upvoted 0 times
...
Barbra
1 year ago
I agree, option B is the best choice for this scenario.
upvoted 0 times
...
...

Save Cancel