Free Salesforce OmniStudio-Consultant Practice Exam with Questions & Answers | Set: 6

The consultant should design the OmniScript solution using the Save property to allow the user to stop and resume a process at a later time. The Save property is a property that determines whether an OmniScript can be saved as a draft and resumed later from where it was left off. The consultant can enable the Save property on an OmniScript to allow the user to stop and resume a process at a later time, without losing any data or progress.

Millions of read-only historical transaction records are a large-data-volume archival pattern, not a normal transactional custom-object pattern. Big Objects are designed to store and manage massive amounts of data on the Salesforce platform, especially historical or archive-style datasets. External Objects are also valid when the data remains in an external system and Salesforce needs to surface it without fully storing it in core object storage. A standard custom object may create storage, indexing, and performance problems at this scale unless heavily architected. A long text field is completely inappropriate because it destroys record structure, filtering, indexing, and security granularity. Avoiding storage does not meet the requirement to display the records. The FlexCard can display the summarized data, but the underlying object strategy must support high-volume access.

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

Rank (A) – The Expression Set with the highest rank is selected by the Calculation Engine when multiple active Expression Sets exist for the same date.

This ensures that the most relevant pricing rule is applied based on the company’s prioritization strategy.

B. Date modified – The modification date does not determine priority for execution.

C. Date created – The system does not use the creation date to prioritize which Expression Set to execute.

D. Sequence – Sequence applies within an Expression Set but does not control selection between multiple active Expression Sets.

Comprehensive and Detailed In-Depth Explanation:Why not the other options?? Salesforce OmniStudio Reference:

Expression Sets in Calculation Procedures

OmniStudio Calculation Engine Overview

 To create a new quote estimation process that involves multiple steps and a variable number of rows of data, the consultant should recommend the following OmniScript elements:

Edit Block: This is an element that allows the user to add, edit, or delete multiple rows of data in a table-like format. It can be used to capture the service category, number of hours, and hourly rate for each row.

Formula: This is an element that allows the user to perform calculations on data using mathematical expressions. It can be used to calculate the total for each row by multiplying the number of hours with the hourly rate.

Input Block: This is an element that allows the user to enter data using various input types, such as text, number, date, picklist, etc. It can be used to display the formula result for each row and the final price for the quote.

The elements that are not suitable for this scenario are:

Multi-select: This is an element that allows the user to select multiple options from a list. It is not relevant for this scenario, as the user needs to enter data in each row, not select from predefined options.

Step: This is an element that organizes the OmniScript into one or more pages. It is not relevant for this scenario, as it does not capture or display any data.

The Data Mapper Load must resolve the related Contact record before it can populate the Case ContactId lookup field. Mapping the Contact Name directly into ContactId is invalid because ContactId expects a Salesforce record ID, not a text name. A formula cannot reliably convert a name string into a Salesforce ID. " Auto-Link " is not the correct Data Mapper Load mechanism. The proper approach is to define a lookup mapping that searches the Contact object using the available field value, then uses the resolved Contact record ID for the Case relationship. Salesforce Data Mapper Load documentation confirms that Loads write data to Salesforce objects, and related-object/link mapping patterns are used to populate lookup relationships between records. In a real project, a unique field is safer than Name because names may not be unique.

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