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 Exam PDI Topic 11 Question 84 Discussion

Actual exam question for Salesforce's Platform Developer I exam
Question #: 84
Topic #: 11
[All Platform Developer I 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 t

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: B

Contribute your Thoughts:

Corinne
2 months ago
Yes, that's what I would choose on the exam
upvoted 0 times
...
Darnell
2 months ago
A) Roll-up summary field? Really? That's not going to work for a many-to-many relationship. B) Junction object is the only way to fly. Now if only I could squash all these bugs in my code...
upvoted 0 times
...
Georgiana
3 months ago
So, the answer is B) Junction object between Bug__c and Account
upvoted 0 times
...
Dylan
3 months ago
D) Master-detail field on Bug__c to Account seems too restrictive. You want companies to be able to report multiple bugs, so a junction object is the way to go. This question is bugging me, but I think I got it!
upvoted 0 times
Walker
2 months ago
B) Junction object between Bug__c and Account
upvoted 0 times
...
Sherron
2 months ago
A) Roll-up summary field of Bug__c on Account
upvoted 0 times
...
...
Devorah
3 months ago
I agree, a lookup field would not allow for multiple bugs to be reported by multiple companies
upvoted 0 times
...
Sherell
3 months ago
With a junction object, we can easily report on which companies have reported which bugs
upvoted 0 times
...
Mitsue
3 months ago
Why a junction object instead of a lookup field on Bug__c to Account?
upvoted 0 times
...
Paola
3 months ago
Hmm, I was thinking C) Lookup field on Bug__c to Account, but now that I think about it, a junction object is probably the way to go. Gotta love those many-to-many relationships!
upvoted 0 times
Willard
2 months ago
Yeah, a lookup field might not be enough to handle the complexity of reporting on multiple bugs reported by multiple companies.
upvoted 0 times
...
Rosamond
3 months ago
I agree, a junction object would be the best way to handle many-to-many relationships.
upvoted 0 times
...
Jeannine
3 months ago
Yeah, a lookup field might not be enough for this scenario. Junction object is the way to go.
upvoted 0 times
...
Rebecka
3 months ago
I agree, a junction object would be the best way to handle many-to-many relationships.
upvoted 0 times
...
...
Gracia
3 months ago
I think we need a junction object between Bug__c and Account
upvoted 0 times
...
Shoshana
3 months ago
I think the correct answer is B) Junction object between Bug__c and Account. That makes the most sense to me for tracking the many-to-many relationship between companies and bugs.
upvoted 0 times
Belen
3 months ago
I think a roll-up summary field could work too, but a junction object seems more flexible.
upvoted 0 times
...
Ettie
3 months ago
I agree, a junction object would be the best way to track the relationship between companies and bugs.
upvoted 0 times
...
...
Amalia
4 months ago
I believe a Roll-up summary field of Bug__c on Account would be more efficient for reporting purposes.
upvoted 0 times
...
Judy
4 months ago
But wouldn't a Lookup field on Bug__c to Account also work for tracking which companies reported which bugs?
upvoted 0 times
...
Elsa
4 months ago
I agree with Elfrieda, a Junction object would allow for multiple bugs to be reported by multiple companies.
upvoted 0 times
...
Elfrieda
4 months ago
I think we need a Junction object between Bug__c and Account.
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