OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Free Practice Exam Questions (2026 Updated)

The LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript

Multi-language OmniScripts use Salesforce translation infrastructure and custom labels. In normal Salesforce runtime usage, the language shown to the user is driven by the user’s Salesforce language setting, not simply by the browser language or by a random session variable. The default OmniScript language is only the fallback/base design language; it does not decide which translated bundle is displayed for each user when translations exist. Option A is wrong because a global Session Variable is not the standard translation selector. Option B is also wrong in this context because OmniScript translations are tied to Salesforce language and Translation Workbench/custom-label behavior. Therefore, the user’s Salesforce language setting is the correct controlling source for displayed translations.

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

According to the Integration Procedure Actions page, a Calculation Action can be used to “call a Calculation Procedure that performs calculations on input data” and a Matrix Action can be used to “call a Calculation Matrix that performs calculations on input data”. 

Functions like CONCAT, DATEDIFF, and IF are supported in value fields where expressions can be parsed at runtime.

B. In a Set Values Action in a Value field – Correct. The Set Values element supports expression functions in its Value field, allowing for real-time evaluation during IP execution.

C. In a Data Mapper Action in an Input Parameters value field – Correct. Input Parameters to DataRaptors in Integration Procedures can use expression logic to dynamically compute and pass values.

Incorrect Options:

A. Output JSON Path in DataRaptor is for structural mapping, not function execution.

D. Remote Action Output fields typically receive data, not compute it.

Salesforce OmniStudio Developer Guide → Expression Functions in Integration Procedures

The correct parameter is ContextId. When an OmniScript is launched from a Lightning Record page, Salesforce passes the current record ID into the OmniScript as a context ID. The OmniScript can then use ContextId to query related data through Data Mapper Extracts, Integration Procedures, or other actions. Using AccountId might work only if the developer manually maps that value, but it is not the standard automatic page-context parameter. recordId is common in Lightning Web Components, but OmniScript’s record-page launch behavior uses ContextId. CurrentRecord is not the standard OmniStudio parameter. Salesforce documentation explicitly states that, by default, the record ID on a Lightning Record page passes into the OmniScript as a context ID.

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

The intended answer is C, but the wording is sloppy. A true HTTP 401 normally comes from the external service and usually means authentication headers, tokens, or credentials are rejected. However, OmniStudio/Salesforce outbound HTTP calls also require the target endpoint to be allowed through Remote Site Settings or an equivalent named credential setup. If the API key is confirmed correct and the available choices focus on Salesforce configuration, the most probable platform-side cause is that the external URL is not trusted in Remote Site Settings. API Access permission on the user profile does not authorize an external endpoint. Chainable execution does not cause endpoint authorization failure. Missing Set Values would affect input construction, not Salesforce’s permission to call the URL.

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

Navigation button labels such as Next are controlled through OmniScript setup-level label mapping/custom label configuration, not by editing each Step element or creating Navigate Actions. The Next button is part of the OmniScript framework navigation, so changing it globally for the script belongs in the setup configuration where element names and labels can be mapped. A Navigate Action is used to navigate to another page or component; it is not the framework Next button. LWC Component Override is for replacing component rendering behavior with a custom LWC, which is excessive and incorrect for a simple label change. Salesforce documentation describes OmniScript setup configuration and custom label references for OmniScript properties, supporting the setup-label approach.

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.

This scenario relates to FlexCard preview behavior and data mapping issues.

B. There is no Salesforce record for the FlexCard based on the RecordId in the layout ' s Test Data Source Settings – If the test record does not exist, the FlexCard will not display any data during preview. This is a common setup mistake.

C. The Data Node field for the FlexCard is empty – The Data Node field must be set correctly to match the JSON node where the expected data resides. If it is empty or incorrect, the FlexCard won’t bind data to UI elements.

Incorrect Options:

A. Even if the RecordId is from a different record type, as long as the data structure aligns, it would still render; it’s not a definitive reason for the card failing to display.

D. Attributes are not required to display field values directly; they are used for passing data between cards or from context, not for direct field rendering.

Salesforce OmniStudio → FlexCard Data Source Setup & Troubleshooting

The FlexCard Player component is used to display FlexCards in a community page. The developer needs to add the FlexCard’s API name to the FlexCard Player component to configure the FlexCard for deployment in a community.

 According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel shown is option C, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

The merge code syntax for accessing an array element is %%Details:Customer|1:ID%%, where 1 is the index of the element. The index starts from 1, not 0, so the first element is Customer|1. The % sign is used for single-value merge codes, not array merge codes. The $ sign is used for variables, not merge codes.

The element name for the missing data must match the JSON node key in the Integration Procedure Response, otherwise the data will not be mapped correctly. The JSON sent from the Integration Procedure Action must match one of the Original Input for the Integration Procedure, otherwise the Integration Procedure will not execute properly. The Integration Procedure Preview Input Parameters and the Response JSON Path have no effect on displaying data in OmniScript.