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

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.

 Setting the element to require if true allows the developer to configure a Disclosure element to require user input only if a condition is met. In this case, the condition is that the user already checked a Non-Disclosure Agreement Checkbox. The other options are either incorrect or irrelevant for this requirement.

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript. Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

A DocuSign Envelope Action can be used to create and send a document for signature using a DocuSign template. The developer can specify the template ID, recipient details, and prefill data in the action configuration

Checking the Enable Cancel checkbox in the Setup tab under Cancel Options allows the developer to enable the cancel functionality for all steps in the OmniScript. The user can cancel the OmniScript at any time by clicking the Cancel button in the top right corner of the OmniScript. Adding a navigation Action inside each step is not necessary and would clutter the OmniScript design. Setting the Component name or Element Name to ‘’Cancel’’ has no effect on enabling the cancel functionality.

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

Salesforce OmniStudio Developer Guide → OmniScript Formula Element

 Deleting a row in Version 3 will only affect that version, not any previous or future versions. The row that contains the Code CA-SF will remain in Versions 1 and 2, as well as any versions created after Version 3. The other options are incorrect because they imply that deleting a row in one version will affect other versions as well.

The best practice for configuring the Input JSON for a DataRaptor Load is to copy the Input JSON from the OmniScript {Data} modal. This ensures that the Input JSON matches the data structure and format of the OmniScript data. The DataRaptor Action Debug node may not have the same data as the OmniScript data, and building the Input JSON node by node in an editor or in the DataRaptor Designer may introduce errors or inconsistencies.

The Target property in publishing Options determines where the FlexCard will be displayed. Setting it to the Community page will make the FlexCard available in the community

the calculation procedure version that would execute on 2/15/2020 at 12:00 PM is the one that has the start date time and end date time that include that date and time, and also has the highest priority among the enabled versions. In this case, only version number 4 meets these criteria, as it has a start date time of 2/1/2020 12:00 AM, an end date time of 4/1/2020 12:00 AM, a priority of 1, and is enabled. The other versions either have a different start or end date time, a lower priority, or are not enabled.

 Using the LIMIT filter on the Extract definition allows the developer to specify the maximum number of results to return from the DataRaptor Extract. Defining a formula with the Filter function is used to filter the results based on a condition. Using a Custom Output Type when creating the DataRaptor is used to define the structure of the output data. Setting the Limit Property on the Action that calls the DataRaptor Extract has no effect on limiting the results.

The Additional Input property allows the developer to specify additional input parameters to be sent to the Integration Procedure element. The input parameters can be specified as a JSON object or as a list of key-value pairs. If the developer checked Send Only Additional Input, then only the input parameters specified in Additional Input are sent, and the SEND/RESPONSE TRANSFORMATIONS are ignored. Therefore, the developer needs to specify the same input parameters as in the SEND/RESPONSE TRANSFORMATIONS in Additional Input. Option C shows how to do this using a JSON object with two properties: “DBExtractAction:Account” and “DBExtractAction:SecondaryAccount”. The values of these properties are the same as in the SEND/RESPONSE TRANSFORMATIONS. 

 Setting the collapsible property on the block element allows the user to expand or collapse the block as needed. Using a Data table element is not suitable for displaying contact information. Setting the class’’ collapsible’’ on the block element has no effect. Using a conditional FlexCard State requires a condition to be met, not a user choice.

The Expression Set component in OmniStudio allows developers to perform calculations using steps such as Aggregation, Calculation, and Sub Expression.

C. Add an Aggregation Step as SUM(BasePrice) – This is correct. Aggregation steps are specifically designed to perform functions like SUM, AVG, COUNT, MIN, MAX over collections (arrays) of data. In this use case, summing the entire BasePrice array is best handled using an Aggregation Step.

Incorrect Options:

A. Sub Expression Step is used to combine or manipulate previously calculated values, not to aggregate across an array.

B. Calculation Step is used for row-level calculations, not aggregation across multiple rows.

Salesforce OmniStudio Documentation → Expression Sets → Aggregation Step

A formula element allows the developer to define formulas using functions and operators to manipulate data in an OmniScript. The output of the formula element can be displayed to the user immediately in the current step using a display element. The CONTIF function counts how many times a value appears in a list1. A Calculation Action element executes a calculation procedure and returns the output as a JSON object. A Set Values element assigns values to variables or fields in an OmniScript. A Range element defines a range of values for a variable or field in an OmniScript1. Based on best practice, a formula element is the most suitable element to use the CONTIF function in this scenario.

According to Salesforce OmniStudio Integration Procedures documentation, when working with deeply nested JSON, Integration Procedures are ideal. They allow developers to flatten and manipulate JSON data, especially when handling external responses.

C. Integration Procedure – This is correct. IPs provide Response Transformers, DataRaptor Transforms, and Response Actions to reshape and simplify nested data structures for consumption by front-end components.

Incorrect Options:

A. DataRaptor Transform is used inside IPs but cannot directly handle external HTTP calls or manage complex orchestration.

B. HTTP Action Element is used inside an Integration Procedure, but by itself, it does not process or simplify the data.

D. Guided Workflow is not a recognized OmniStudio component for data transformation.

OmniStudio Integration Procedures Guide → Handling Nested JSON

The correct syntax for merge codes in OmniScript is %%sNodeName%%, where NodeName is the name of the JSON node in the data source. The other options are either missing the s or using incorrect symbols.

 The Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact’s postal code in the child FlexCard.