Valid Data-Architect Dumps shared by ExamDiscuss.com for Helping Passing Data-Architect Exam! ExamDiscuss.com now offer the newest Data-Architect exam dumps, the ExamDiscuss.com Data-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Data-Architect dumps with Test Engine here:
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?
Correct 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.