MENU
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?
Suggested Answer: B
Get Premium DEX-450 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
ST
Stanford
11 months ago
Master-detail won't fit since it's not a strict parent-child relationship.
TA
Tamekia
11 months ago
Wait, can bugs really be reported by multiple companies? Sounds odd!
AL
Alonzo
12 months ago
A lookup field wouldn't work for this, right?
VA
Vannessa
12 months ago
Totally agree, option B is the way to go!
RO
Rosann
1 year ago
You need a junction object for many-to-many relationships.
JE
Jerry
1 year ago
I thought roll-up summary fields were for one-to-many relationships only? So, I don't think option A would work here. I’m leaning towards the junction object as well.
DE
Devon
1 year ago
I practiced a similar question where a junction object was necessary. I feel like that's the best option here too, especially since we want to track multiple relationships.
GA
Gail
1 year ago
I'm not entirely sure, but I remember something about lookup fields. Could a lookup field on Bug__c to Account work? It seems simpler, but I’m not confident it would allow for the reporting we need.
DE
Della
1 year ago
I think we need a junction object since companies can report multiple bugs and bugs can be reported by multiple companies. It feels like the right approach for many-to-many relationships.
EL
Elden
1 year ago
Okay, let me see if I've got this straight. We need to be able to report on which companies have reported which bugs, and each company can report multiple bugs, and each bug can be reported by multiple companies. I think the junction object (option B) is probably the way to go, but I'll double-check the other options just to be sure.
KA
Kayleigh
1 year ago
The key here is that each company can report multiple bugs, and each bug can be reported by multiple companies. That means we need a way to link the two objects together. I'm pretty confident that the junction object approach (option B) is the right solution for this scenario.
EV
Evangelina
1 year ago
Hmm, I'm a bit unsure about this one. I'm trying to think through the different options, but I'm not 100% sure which one is the best solution. I might need to review the concepts around junction objects and lookup/master-detail relationships again.
DO
Dortha
1 year ago
This looks like a classic many-to-many relationship between Accounts and Bugs. I think the junction object approach (option B) is the way to go here.
TY
Tyra
1 year ago
I'm not entirely sure about this one. The options seem to be describing different types of obligations or accounting entries. I'll need to re-read the question and the options carefully to try to determine the best answer.
CH
Cherry
2 years ago
As a professional bug catcher, I can tell you that junctions are the only way to wrangle all these bugs back into their accounts. Simple as that.
AL
Aliza
2 years ago
Let's get started on setting up the junction object in Salesforce.
ME
Melynda
2 years ago
I agree, it will make reporting on bugs much easier.
LE
Leota
2 years ago
That makes sense, it will allow us to track which companies reported which bugs.
LE
Leandro
2 years ago
We need to create a junction object to link companies and bugs.
FE
Felice
2 years ago
Bugs and Accounts sitting in a tree, J-U-N-C-T-I-O-N. Yep, that's the answer alright.
CL
Clare
2 years ago
Wait, is this a trick question? I feel like they're trying to confuse us with all these fancy Salesforce terms. Junction object is the way, no doubt.
VA
Valene
2 years ago
Exactly, a junction object will allow for a many-to-many relationship between companies and bugs, enabling the reporting needed for process improvement.
BR
Brock
2 years ago
That's correct. By creating a junction object, you can track which companies have reported which bugs and vice versa.
SO
Soledad
2 years ago
Yes, you're right! A junction object is needed to create a many-to-many relationship between the Account and Bug__c objects.
LI
Lillian
2 years ago
I'm not sure, but I think a lookup field on Bug__c to Account could also work.
DE
Delmy
2 years ago
I agree with Merilyn, a junction object would be the best option for this scenario.
ME
Merilyn
2 years ago
I think we need a junction object between Bug__c and Account.
LA
Lai
2 years ago
Oooh, junction objects! My favorite way to connect unrelated objects. This is the way to go for sure.
AM
Amber
2 years ago
Definitely need a junction object here. Reporting on bugs by company is just too complex for a lookup or roll-up.
KE
Keva
2 years ago
Yes, a junction object will allow for a many-to-many relationship between bugs and companies.
MA
Mari
2 years ago
I agree, a junction object is the best option for this scenario.
LI
Linn
2 years ago
D) Master-detail field on Bug__c to Account
NI
Nickole
2 years ago
C) Lookup field on Bug__c to Account
KI
Kimberlie
2 years ago
B) Junction object between Bug__c and Account
AR
Arminda
2 years ago
A) Roll-up summary field of Bug__c on Account