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

Salesforce DEX-450 Exam - Topic 8 Question 122 Discussion

Actual exam question for Salesforce's DEX-450 exam
Question #: 122
Topic #: 8
[All DEX-450 Questions]

A software company is using Salesforce to track the companies they sell their software to in the Account object. They also use Salesforce to track bugs in their software with a custom object, Bug__c.

As part of a process improvement initiative, they want to be able to report on which companies have reported which bugs. Each company should be able to report multiple bugs and bugs can also be reported by multiple companies.

What is needed to allow this reporting?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Harley
5 days ago
D sounds interesting, but isn't that overcomplicating things?
upvoted 0 times
...
Reita
10 days ago
A roll-up summary wouldn't work here since it's not a master-detail relationship.
upvoted 0 times
...
Filiberto
15 days ago
Definitely need a way to link them, but surprised there's no built-in feature for this.
upvoted 0 times
...
Kimbery
20 days ago
I think B is better. Master-detail gives more control.
upvoted 0 times
...
Bong
25 days ago
C is the way to go! Lookup field makes sense.
upvoted 0 times
...
Kirby
1 month ago
B is the clear winner here. Master-detail is the secret sauce for this problem.
upvoted 0 times
...
Ivette
1 month ago
Hmm, I'm leaning towards A. Roll-up summary fields are so hot right now.
upvoted 0 times
...
Katina
2 months ago
D sounds like a good idea, but it's probably overkill for this use case.
upvoted 0 times
...
Gerry
2 months ago
I'm pretty sure C is the correct answer here. Lookup field is the way to go.
upvoted 0 times
...
Stefany
2 months ago
Option B is the way to go. Master-detail all the way!
upvoted 0 times
...
Pamella
2 months ago
I’m confused about the roll-up summary option; I don’t think it applies here since we need a many-to-many relationship, right?
upvoted 0 times
...
Whitley
3 months ago
I practiced a similar question where we had to connect two objects, and I feel like a lookup might be the best fit since it allows for multiple associations.
upvoted 0 times
...
Stephen
3 months ago
I'm not entirely sure, but I remember something about master-detail relationships being useful for reporting. Could that be the right choice here?
upvoted 0 times
...
Allene
3 months ago
I think we need a way to link multiple bugs to each company, so maybe a lookup field on Bug__c to Account?
upvoted 0 times
...
Edelmira
3 months ago
I'm pretty confident that option B, a master-detail field, is the right solution here. That's going to give them the reporting capabilities they need while also allowing for the many-to-many relationship between bugs and accounts.
upvoted 0 times
...
Nieves
3 months ago
Option D, a function object, seems like overkill for this use case. I'd go with either B or C, depending on whether they need a strict master-detail relationship or just a more flexible lookup.
upvoted 0 times
...
Margret
3 months ago
The question is a bit confusing to me. I'm not sure if a function object is really necessary here. I'd probably start by looking at options B and C and trying to figure out which one best meets the requirements.
upvoted 0 times
...
Selma
4 months ago
Hmm, I'm not sure. I'm leaning towards option C, a lookup field on Bug__c to Account. That seems like it would give us the flexibility they need to connect bugs to multiple accounts.
upvoted 0 times
...
Nathalie
4 months ago
I think option B is the way to go here. We need a master-detail relationship between the Bug__c and Account objects to allow for the reporting they want.
upvoted 0 times
...

Save Cancel