Salesforce Updated OmniStudio-Consultant Exam Questions and Answers by iga

The correct OmniStudio tools to design a solution that meets these requirements are OmniScript, Calculation Procedures and Matrices, and OmniStudio Action. OmniScript can be used to create a user interface for capturing customer information and displaying suggested products. Calculation Procedures and Matrices can be used to compute the discount percentage per product based on the customer data provided. OmniStudio Action can be used to save the list of suggested products including discounts to Salesforce or an external system. Integration Procedures are not needed for this scenario, as there is no data integration involved. FlexCard is not relevant for this scenario, as it is used to display contextual data on record pages.

The two OmniStudio tools that should be recommended to meet these requirements are Calculation Procedure and Calculation Matrix. Calculation Procedure allows the designer to define a multi-step calculation process that can use data from various sources. Calculation Matrix allows the designer to define a table of values that can be used as inputs or outputs for calculations. In this case, a Calculation Matrix can be used to store the discount thresholds based on region and customer lifetime score, and a Calculation Procedure can be used to apply them to the orders. OmniStudio Action is not needed for this scenario, as there is no interaction involved. DataRaptor Transform is not suitable for this scenario, as it is used to transform data from one format to another.

Sorting by a formula field can be expensive because formula values are calculated rather than stored like normal indexed fields. If the formula is not indexed, Salesforce may need to calculate values across many candidate records before sorting or filtering them, increasing query processing time. The issue is not primarily JSON parsing memory, session CPU from OmniStudio itself, or cache bypassing. The database query plan is the real bottleneck. Salesforce large-data-volume guidance is clear that selective filters and usable indexes are central to query performance, and Salesforce notes that only certain deterministic formula fields can be custom-indexed. Therefore, sorting/filtering on non-indexed calculated values is a poor performance design for high-volume Data Mapper operations.

================

The two pieces of data that the consultant should recommend displaying using FlexCards are: Policies including type, issue date, amount and Customer name, title, phone, email. A FlexCard is a tool that can display data and actions in a card format. The consultant can use FlexCards to show important and summary information about the customer and their policies, such as name, title, phone, email, type, issue date, and amount. These pieces of data are suitable for FlexCards because they are concise and relevant for the agents