DEX-403 practice question 12 of 35

Universal Containers (UC) has several large customers that sell their products through dealers. UC identifies and works with a single individual at…

Full set: 291 questions
Universal Containers (UC) has several large customers that sell their products through dealers. UC identifies and works with a single individual at each customer and at each dealer. Separate bills are sent to each customer and each dealer. These details need to be stored in a format that clearly displays the business entities and their appropriate representatives. How should an app builder Implement these regalements?
Answer options
A: Create a single parent record, add each rep as a contact to the parent account and add each dealer as a child record.
B: Create both customer and dealer as accounts, create account teams on each account and associate the dealer records with the parent account.
C: Create a single account record, add each rep as a contact and create a custom dealer object.
D: Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy. Correct answer
Correct Answer:
D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.
Explanation

This solution correctly utilizes standard Salesforce objects and features. Both customers and dealers are distinct business entities that require separate billing, making the Account object the appropriate choice for each. The individual representatives for each entity should be stored as Contacts related to their respective Account. The relationship between the parent customer and its dealers is best represented using the standard Account Hierarchy feature. This is achieved by populating the 'Parent Account' field on the dealer's Account record with the customer's Account, creating a clear, reportable parent-child structure.

Why Incorrect

A: This approach improperly combines distinct business entities and their contacts under a single parent record, which complicates billing and relationship tracking. B: Account Teams are designed for collaborative selling and access control, not for representing a single, primary representative. The Contact object is the correct choice for this. C: Creating a custom object for dealers is unnecessary as the standard Account object is designed for this purpose. Using a single account record fails to separate the distinct customer and dealer entities.

References

1. Salesforce Help; Accounts; "Guidelines for Using Accounts": This document establishes that an Account is an organization, company, or consumer you want to track. Both customers and dealers fit this definition, justifying creating separate account records for each.

2. Salesforce Help; Contacts; "Guidelines for Using Contacts": This source clarifies that Contacts are the individuals associated with your accounts. This directly supports creating Contact records for the representatives at each customer and dealer account.

3. Salesforce Help; Set Up an Account Hierarchy: "To create a parent-child relationship between two accounts, open the child account’s record and fill in the Parent Account field." This official documentation confirms that the Account Hierarchy is the standard method for modeling the relationship between a customer (parent) and its dealers (children).

Scroll to Top