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:
Access Data-Architect Dumps Premium Version
(260 Q&As Dumps, 35%OFF Special Discount Code: freecram)
<< Prev Question Next Question >>
Question 8/86
Universal Containers (UC) is implementing Salesforce Sales Cloud and Service Cloud. As part of their implementation, they are planning to create a new custom object (Shipments), which will have a lookup relationship to Opportunities. When creating shipment records, Salesforce users need to manually input a customer reference, which is provided by customers, and will be stored in the Customer_Reference__c text custom field. Support agents will likely use this customer reference to search for Shipment records when resolving shipping issues. UC is expecting to have around 5 million shipment records created per year. What is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records?
Recent Comments (The most recent comments are at the top.)
C. Set Customer_Reference__c as an External ID (non-unique).
Here's why this option is the best choice:
External ID Fields and Search Performance: Setting the Customer_Reference__c field as an External ID can improve the efficiency of search operations. External ID fields are indexed, which means that Salesforce can search through them more quickly compared to non-indexed fields. This indexing helps in speeding up the search process, making it easier and faster for support agents to locate specific shipment records using the customer reference.
Non-unique Requirement: Given the scenario, the customer reference provided by customers may not be unique. Customers could, potentially, use the same reference for different shipments. Therefore, setting the field as a non-unique External ID allows UC to accommodate potential duplicate references across different shipment records without violating the database constraints that would come with marking it as unique.
Global Search and Reporting: Indexed fields, such as those marked as External IDs, are more efficiently searched by Salesforce's global search. This means that when support agents search for a customer reference, Salesforce can quickly retrieve and display relevant shipment records, thereby improving the user experience and efficiency in resolving shipping issues....
C. Set Customer_Reference__c as an External ID (non-unique).
Here's why this option is the best choice:
External ID Fields and Search Performance: Setting the Customer_Reference__c field as an External ID can improve the efficiency of search operations. External ID fields are indexed, which means that Salesforce can search through them more quickly compared to non-indexed fields. This indexing helps in speeding up the search process, making it easier and faster for support agents to locate specific shipment records using the customer reference.
Non-unique Requirement: Given the scenario, the customer reference provided by customers may not be unique. Customers could, potentially, use the same reference for different shipments. Therefore, setting the field as a non-unique External ID allows UC to accommodate potential duplicate references across different shipment records without violating the database constraints that would come with marking it as unique.
Global Search and Reporting: Indexed fields, such as those marked as External IDs, are more efficiently searched by Salesforce's global search. This means that when support agents search for a customer reference, Salesforce can quickly retrieve and display relevant shipment records, thereby improving the user experience and efficiency in resolving shipping issues....