Maybe B would work if the key thing is tracking each agency as a totally new record, but is "historical accuracy" about seeing all past relationships or just most recent? If they need history of every agency a contractor was with, D changes everything.
Q: 12
AW Computing (AWC) occasionally works with independent contractors, who the company
stores as Contacts in Salesforce. Contractors often change agencies, and AWC wants to maintain the
historical accuracy of the record.
What should AWC use to track Contacts?
Options
Discussion
Makes sense to use D. Contacts to multiple Accounts lets you keep one Contact and see all their agency links over time.
C , junction object handles many-to-many and could track history per agency.
D or C? Contacts to multiple Accounts sounds right for tracking history but junction object could work too if they want custom fields on the relationship. Not 100 percent sure, just feels like D is more standard for Salesforce.
Nah, B would just create duplicates and make reporting messy. D lets you keep the historical links between one contractor and all their agencies over time. Pretty sure that's what they're after, unless I'm missing something.
B tbh. If every agency change is a new Contact, history is simple to track per agency.
Be respectful. No spam.
Question 12 of 30