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

According to the OmniStudio Developer Guide, “DataRaptor Transform actions can convert JSON to XML and vice versa.” Therefore, the correct answer is C.

The Id Field for Actions in the FlexCard specifies which field from the FlexCard data source will be used as the record ID for the OmniScript. If this field is blank, the OmniScript will not receive any record ID and will not be able to retrieve any Salesforce data. In the DataRaptor Extract Action, the Input Parameters Filter Value determines how to filter the data based on the record ID. If this value is misspelled, the DataRaptor Extract will not be able to match the record ID and will not return any data.

According to the Transform External Data Unit, the Expected Output JSON should match the Output Path of the DataRaptor Transform. In option D, the Output Path is Current:CityState, which matches the Expected Output JSON. The other options have different Output Paths that do not match the Expected Output JSON. Therefore, the correct answer is D.

According to the Integration Procedure Actions page, “To pass data from a Set Values action to a DataRaptor action, add the Set Values action name to the Additional Input field of the DataRaptor action.” 

The Node field for the parent FlexCard should be set to {Records}, which is an array of all the records retrieved by the parent FlexCard data source. This will allow the child FlexCard to access the records and display them in a DataTable.

According to the OmniScript Action Elements page, a DataRaptor Extract Action can be used to “get data from one or more Salesforce records” and an HTTP Action can be used to “get, save, or delete data through a web application programming interface (API)”. 

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).

A. Use an Edit Block element configured with Remote Actions – Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents). The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.

Incorrect Options:

B. Text Block is for display purposes and cannot manage data input or backend actions.

C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.

D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.

Salesforce OmniStudio Guide → OmniScript Edit Block Element

OmniStudio Best Practices → CRUD Operations in OmniScripts

The Upsert Key checkbox indicates that the field is used as a key for upserting records. The Is Required for Upsert checkbox indicates that the field is mandatory for upserting records. The developer needs to check both checkboxes on the Account Id field to update the Account status only if the Account record already exists. Otherwise, a new account will be created.

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 six elements: ContactName, ContactPhone, ContactEmail, CaseNumber, CaseSubject, and CaseStatus. The DRGetContactDetails action is a DataRaptor Extract action that retrieves data from the Contact and Case objects in Salesforce. The BlkCases element is a Repeat Block that displays a list of cases related to the contact. Therefore, the JSON from the DRGetContactDetails action that would display all six values correctly shown is option A, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown.