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 Plat-Arch-201 Exam - Topic 5 Question 11 Discussion

Posted by Deeann on Aug 18, 2026 at 05:11 PM

A large automobile manufacturer has decided to use Salesforce as its CRM. It needs to maintain the following dealer types in their CRM:

Local dealers

Regional distributor

State distributor

Service dealer

The attributes are different for each of the customer types. The CRM users should be allowed to enter only attributes related to the customer types. The processes and business rules for each of the customer types could be different.

How should the different dealers be maintained in Salesforce?

Suggested Answer: A

According to Trailhead2, record types are a feature that allows administrators to create different business processes, page layouts, and picklist values for different types of records within an object. Record types can be used to maintain different dealer types in Salesforce by creating record types for each of the dealer types and assigning them appropriate attributes, processes, and rules. Option A is the correct answer because it suggests using Accounts for dealers, and creating record types for each of the dealer types. Option B is incorrect because creating dealers as Accounts, and building custom views for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option C is incorrect because using Accounts for dealers and custom picklist field for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option D is incorrect because creating Custom objects for each dealer types and custom fields for dealer attributes can be unnecessary and complex, as it requires creating multiple objects and relationships instead of using the standard Account object.


Get Premium Plat-Arch-201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
14 comments · newest first
AL
Alecia 23 hours ago
D sounds complicated, not sure if that's necessary for just dealers.
LI
Lizette 6 days ago
Wait, why not just use custom objects for everything? Seems simpler!
LE
Leanna 11 days ago
B could work too, but it might get messy with too many views.
CE
Celeste 16 days ago
Totally agree, record types make it easy to customize!
BR
Brock 22 days ago
I think A is the best option for managing different dealer types.
SA
Salena 27 days ago
A is solid, but I wonder if it complicates reporting later on.
JO
Jonelle 1 month ago
Wait, can Salesforce really handle all those different attributes?
DE
Deeanna 1 month ago
Custom objects for each type? Sounds like overkill to me.
MA
Marylin 1 month ago
I disagree, B seems more flexible with custom views.
DO
Dorothy 2 months ago
I think A is the best option for managing different dealer types.
AZ
Azzie 2 months ago
I vaguely recall something about using picklists for categorizing accounts. C might be too limiting since it doesn't allow for unique attributes per dealer type.
MO
Mose 2 months ago
I feel like we practiced a similar question where we had to decide between record types and custom fields. I think B could work too, but I’m leaning towards A.
MA
Margurite 2 months ago
I'm not entirely sure, but I think creating custom objects might be overkill. D seems like it could complicate things more than necessary.
AL
Aleisha 2 months ago
I remember we discussed using record types for different account types in class. It seems like A could be the right choice since it allows for different attributes.
0/2000 characters

Save Cancel