Free Salesforce OmniStudio-Developer Practice Exam with Questions & Answers | Set: 2

The Lookup element is used to retrieve data from a single field in a Salesforce record. The Lookup element allows the developer to specify the object, field, and filter criteria for the data retrieval. The Select element is used to display a list of options for the user to choose from. The HTTP Action element is used to send or receive data from an external system using HTTP methods. The DataRaptor Post Action element is used to create or update Salesforce records using a DataRaptor Transform.

A DataRaptor Transform can simplify nested data by transforming it into a flat structure. The developer can use JSON paths to map the input data to the output data and define the output structure.

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

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

According to the OmniStudio DataRaptor Extract documentation, if a developer wants to limit the number of records returned, the best way is to set the " Limit " property on the element or action that is calling the DataRaptor, such as in an Integration Procedure or OmniScript Action.

A. Set the Limit property on the action that calls the Data Mapper Extract – This is the correct method. The calling context (e.g., OmniScript Action or Integration Procedure) includes a property for setting the limit on query results, which is a recommended and clean method to ensure only one record is retrieved.

Incorrect Options:

B. There is no " LIMIT " clause within the DataRaptor Extract definition UI or JSON definition itself.

C. Custom Output Type controls the structure, not the quantity of output.

D. The Filter function applies conditional logic, not record count.

Salesforce OmniStudio Developer Guide → DataRaptor Extract Configuration

Margin controls spacing outside an element, so Margin Bottom is the correct property when the goal is to create or reduce space between the Text element and the Button below it. Padding controls internal spacing inside the boundaries of the selected element; it would move the text within its own box rather than primarily controlling the gap between two separate elements. Layout controls structural placement and responsiveness, not direct vertical spacing. Spacer can be used as a separate layout object, but it is not the property on the Text element itself. Salesforce’s FlexCard styling guidance separates dimensions, spacing, classes, and inline styles, and the spacing-around-element documentation specifically uses margin controls for external spacing.

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

The best answer is D because the requirement combines two constraints: the OmniScript must be embedded on a third-party website and it must be prefilled using URL-passed data. An Experience Cloud page can host the OmniScript, and the third-party website can embed that page in an iFrame while passing URL parameters. Salesforce documentation confirms that OmniScript URL parameters can prefill fields and must use the c__ prefix in URL query-string format. Option A describes the parameter style, but by itself it does not explain how the OmniScript is embedded on the third-party website. Option C is the standard off-platform LWC/OmniOut-style idea, but the question specifically emphasizes URL-based prefill, which fits the Experience Cloud/iFrame pattern more directly.

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

To retrieve (read) data from Salesforce objects:

A. Data Mapper Extract Action – Correct. A DataRaptor Extract is specifically used to retrieve data from Salesforce, based on input parameters or context.

C. Lookup Input Element – Correct. This is used within OmniScripts to look up a record by matching input data, essentially performing a read operation.

Incorrect Options:

B. DataRaptor Post is not a valid DataRaptor type.

D. DataRaptor Load Action is used for writing/updating data, not retrieving it.

Salesforce OmniStudio Guide → DataRaptor Types and Lookup Input Element Usage

The correct answer is D, but with one serious qualification: the Data Mapper must be configured with the proper security controls. Data Mapper Load is the OmniStudio component used to write JSON, XML, or custom input data to Salesforce objects. For secure storage, the save operation should rely on Salesforce object access, field-level security, sharing, and OmniStudio security settings rather than storing sensitive values in temporary session variables or assuming the UI framework handles everything automatically. Validation rules help data quality, not full access control. Session Variables are not the correct place to persist sensitive business data. Therefore, Data Mapper Load is the correct saving mechanism, supported by Salesforce security configuration.

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

The contact information should be available on demand while the account information stays visible. A collapsible Block element is the cleanest FlexCard design for this: place the contact fields in a separate Block and enable the collapsible property so the user can expand or collapse that section as needed. A CSS class named collapsible is not the supported declarative configuration. A conditional FlexCard State is excessive because the entire card does not need to switch state; only one information section needs to expand or collapse. A DataTable is better for tabular lists of repeated rows, not a small group of primary-contact fields. Salesforce FlexCard documentation confirms that Block elements can group content inside collapsible containers.

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

When testing a FlexCard data source in the designer, the developer must provide valid runtime values for context variables so the configured Integration Procedure can execute as it would at runtime. In this scenario, that means manually entering a valid Context ID, such as an Account record ID, in the Setup or Test Data Source settings and then viewing the returned data. Without a valid context value, the Integration Procedure may not receive the input required to query Account, Opportunity, and Case data. Option C is important inside the Integration Procedure design, but the question asks about testing the FlexCard’s data configuration in the designer. Option B is not generally required for SOQL. Option D is a design choice, not the key testing step.