Practice Free OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Exam Questions Answers With Explanation

 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 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.

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

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.

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

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

Cloning an Integration Procedure creates a copy of it that can be modified and used independently from the original one. This is useful when the new Integration Procedure has a different purpose or functionality than the original one

 The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom. The Additional input parameter is not needed in this case, as it is already included in the Send JSON Path.

In OmniStudio, the Invoke Mode: Fire and Forget setting allows an OmniScript to call an Integration Procedure asynchronously, meaning it does not wait for the response to complete before continuing user interaction.

C. Invoke Mode Fire and Forget – This is the correct setting. It’s designed specifically for use cases where the user experience should not be blocked by backend processing.

Incorrect Options:

A. Use Future is not a valid OmniScript configuration option.

B. Invoke Mode Non-Blocking is not an official setting in OmniStudio terminology.

D. Toast Completion is a UI notification setting and does not impact execution behavior.

OmniStudio Developer Guide ? Integration Procedure Actions in OmniScripts

The wording of this question is imperfect. Official Salesforce documentation identifies the OmniStudio Build Tool, formerly Vlocity Build Tool, as the Node.js command-line automation tool designed to package, export, and deploy OmniStudio DataPacks in a source-control-friendly format. Since “OmniStudio Build Tool” is not one of the listed choices, the only command-line deployment option given is Salesforce Command-Line Interface. Visual Studio Code Integrated Terminal is merely a shell host, not a migration tool. Metadata API is a deployment API, not the OmniStudio-specific CLI named in the documentation. Change Data Capture is an event-streaming feature and has nothing to do with OmniStudio component migration. So D is the only usable answer from the provided options, but the technically precise tool name is OmniStudio Build Tool/Vlocity Build Tool.

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

The correct declarative design is to use a Data Mapper Transform after the HTTP Action. The HTTP Action performs the REST call and returns the response to the Integration Procedure. If that response must be converted from JSON into a required XML structure, the transformation layer should be a Data Mapper Transform, because transforms are built to map input paths to different output structures and formats without writing Apex. XMLStreamReader is for reading XML, not building the target XML payload from JSON. XMLStreamWriter could be used in custom Apex, but the OmniStudio-native answer avoids unnecessary code. A Data Mapper Extract reads Salesforce data, so it is not the right tool for restructuring an HTTP response.

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

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:

A. “The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript.”This is a common configuration issue. If the paths between the OmniScript ' s structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.

B. “The fields that are not updated are read-only in Salesforce.”If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.

Incorrect Options:

C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.

D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.

Salesforce OmniStudio Developer Guide ? DataRaptor Load ? Troubleshooting

Salesforce Help Documentation: OmniStudio DataRaptor Best Practices

 The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is %DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

 According to the OmniStudio Developer Guide, “To upsert a record, select the Upsert Key checkbox for the field that contains the unique identifier for the record. If you want to create a new record when no match is found, select Is Required for Upsert.” Therefore, the correct answer is B.

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

According to the DataRaptor Load Overview page, a Linked Mapping is used to “create or update multiple records in different objects that are related by lookup fields”.

The correct approach is to use the responsive sizing properties available in the element Display configuration, such as Extra Small, Small, Medium, and Large. These settings align the element with the responsive grid model instead of forcing custom widths. Newport Design System styling is intended to provide consistent visual behavior across OmniScripts and FlexCards, so using framework-supported sizing is cleaner than hard-coding CSS. Option B can add utility classes, but it is not the primary standard grid-sizing property for the input element. Option D is weaker because custom CSS makes the layout harder to maintain. Option A is unrelated because Repeat CSS is not the standard way to control horizontal grid width.

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

OmniScript is the correct tool because the scenario describes an end-to-end guided business process: collecting property details, applying conditional steps, calling calculation logic, and submitting the final application. Integration Procedures are excellent for server-side orchestration, integrations, and calculations behind the scenes, but they do not provide the user-facing guided interaction by themselves. Data Mappers retrieve, transform, or save data; they are not the process UI. FlexCards display contextual information and actions but are not designed as the primary multi-step application workflow. Salesforce describes OmniScripts as guided, interactive processes that help users complete business tasks and collect data across channels. Therefore, the core component controlling this process is an OmniScript.

A Text Block element allows the developer to display read-only text in a table format, using merge codes to dynamically include data from the data JSON. A Rich Text Area element is used to display formatted text with images and links. A Text Area element is used to display editable text in a single line or multiple lines. An Edit Block element is used to display editable fields in a form layout.

The correct answer is A. In a parent-child FlexCard design, attributes are passed from the parent FlexCard to the child FlexCard and referenced in the child using the Parent context variable. Salesforce documentation states that the Parent context variable is used to reference attributes from the parent FlexCard on the child FlexCard, and child FlexCard properties allow passing data from the parent by creating attributes and assigning data merge field values. Therefore, when the postal code is passed as a parent attribute, the child FlexCard should reference it as {Parent.postalcode}. {Params.postalcode} is used for URL or runtime parameters, {postalcode} references local data only, and {attr.postalcode} is not the correct OmniStudio parent context syntax.

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

Formula variables should be named clearly and descriptively because the formula result path becomes a reusable JSON key within the Data Mapper. A vague name such as “Value1” or “Temp” makes later mapping, troubleshooting, and maintenance harder, especially when formulas are reused by other formulas or mappings. Using the exact API name of the target field is not always correct because the formula result may be an intermediate value rather than a Salesforce field. The shortest name is not best practice because it sacrifices readability. Generic names are also weak because they hide business meaning. Salesforce’s Data Mapper documentation explains that formula results are stored as key-value pairs and can be reused in mappings, which makes descriptive result names important.

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

The correct syntax for merge codes in Integration Procedure is {(NodeName)}, where NodeName is the name of the JSON node in the data source. The other options are either missing the parentheses or using incorrect symbols.

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.

A. OmniScript Action – This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.

Incorrect Options:

B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.

C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.

OmniStudio Developer Guide ? OmniScript Actions

In Expression Sets, for any intermediate step (like Calculation) to be referenced in subsequent steps, such as Aggregation, the value must be made available via Output.

B. It must be included in the output – Correct. Each step has an " Include in Output " checkbox. If not checked, its result is not accessible to following steps like Aggregation or Sub Expression.

Incorrect Options:

A. Constants are global but do not affect step dependency.

C. It does not have to be a Calculation Step; any previous step’s output can be used if exposed.

Salesforce OmniStudio ? Expression Sets - Step Configuration

 According to the OmniStudio Developer Guide, “If multiple states have true conditions, the state that is closest to the top of the FlexCard canvas displays.” Therefore, the correct answer is A.

The required SOQL behavior has two separate parts: ORDER BY and LIMIT. Ordering controls the sort sequence, such as sorting Tasks by CreatedDate descending so the newest Tasks appear first. Limit restricts how many records are returned, so setting the limit to five produces only the five most recent records. Filter is used to define matching criteria, such as records related to a specific Contact, but it does not create a LIMIT clause. Output Path controls where returned data appears in the JSON structure, not the query ordering or row count. Therefore, the necessary properties are Limit and Ordering. Salesforce’s Data Mapper configuration guidance confirms that Extracts read Salesforce data, can filter/select returned fields, and support extract configuration properties for returned records.

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

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

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)”. 

The correct Output JSON Path is input:BasePrice. The required JSON places BasePrice inside the lowercase input node, so the path must preserve both the correct parent node and the exact field name casing. Option A is wrong because it uses dot notation and incorrectly lowercases BasePrice as baseprice. Option B is wrong because it uses Input with an uppercase I, while the JSON node is input. In JSON-based mappings, path and field names must match the expected output structure. Salesforce’s Data Mapper Transform documentation states that the Output JSON Path defines the desired output path and that path levels are separated using colon syntax, for example Contact:LastName. Therefore, C is the only mapping that correctly targets the BasePrice node under input.

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

The strongest listed choice is a Try-Catch Block, but the real implementation must also use Rollback On Error in the Integration Procedure configuration. Salesforce’s OmniStudio training states that Rollback On Error commits database changes only if the entire transaction completes successfully; otherwise, intermediate database changes are rolled back. A Try-Catch Block is used to run steps and catch failures, and with failure handling configured correctly, the failed block can return a controlled error response. A generic Group element only organizes or conditionally runs steps; it does not provide rollback by itself. Chainable processing intentionally splits work into separate transactions, which is the opposite of the requirement. Continue on Error only addresses Data Mapper behavior, not full transaction integrity.

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

In OmniStudio Integration Procedures, when you want to reference the output of an element in a nested block (e.g., for use in a Remote Action or another step), you must use dot notation that mirrors the block structure hierarchy.

In the exhibit:

Action1 is nested inside:

BlockB, which is nested inside:

BlockA

Therefore, the correct Send JSON Path to access the result of Action1 is:

CopyEdit

BlockA.BlockB.Action1

This format complies with the standard output reference syntax in Integration Procedures, which follows the pattern:

php-template

CopyEdit

< ParentBlock > . < ChildBlock > . < ActionElement >

Incorrect Options:

B. BlockA:BlockB:Action1 – Uses colons instead of dots. This is invalid syntax in JSON path resolution within Integration Procedures.

C. Action1:BlockB:BlockA – Incorrect order and invalid separators.

D. Action1.BlockB.BlockA – Incorrect order (reversed path).

The requirement is only to show or hide a section based on a value already present in the OmniScript data JSON. That is exactly what Conditional View is designed for. It evaluates client-side conditions and controls whether a step, block, or element is displayed, editable, or required. Using an Integration Procedure would add unnecessary server-side processing because the required VIP value is already available in the OmniScript. A Data Mapper Transform is also unnecessary because there is no structural transformation requirement. Creating a new version may be part of the deployment process, but it is not the functional configuration that controls visibility. The best implementation is to place the special offers section in the script and configure Conditional View logic against the VIP member value.

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

The correct configuration is to disable Save for Later through the OmniScript setup configuration, not by hiding it with CSS or deleting a nonexistent structural element. Save for Later is a framework-level OmniScript capability controlled by Save Options, so the proper approach is a configuration setting in the Setup tab. Conditional View is used for OmniScript elements, but Save for Later is not a normal element placed in the script structure. Custom CSS would only hide the button visually and would be a poor, fragile workaround. Salesforce documentation describes Save and Resume behavior as an OmniScript Save Options feature and confirms that Save for Later can be enabled or disabled through configuration rather than custom UI manipulation.

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

 An OS Action is the most efficient way to configure the action that invokes the OmniScript, as it allows the developer to reuse the same OmniScript across multiple FlexCards without creating separate actions for each one. A Custom Action is used to invoke a custom Apex class or Lightning web component. An OmniStudio Action is used to invoke an Integration Procedure or a Calculation Procedure. A Lightning Action is used to invoke a Lightning component or a Visualforce page.

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

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

For off-platform use, OmniStudio uses OmniOut so LWC OmniScripts and FlexCards can run on third-party websites. Salesforce documentation explains that an activated OmniScript can be downloaded as an Off-Platform LWC and then added to the OmniOut project for integration into the external application. This makes option B correct because the external site embeds the OmniScript as a Lightning Web Component artifact, not as a Visualforce page. Visualforce is Salesforce-hosted legacy UI technology and is not the primary external embedding model. A REST API could call backend logic, but it would not render the OmniScript user interface. An Integration Procedure call only executes server-side logic; it does not embed the guided OmniScript experience.

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

A Sub-Integration Procedure Action lets a parent Integration Procedure call another Integration Procedure, so shared logic can be built once and reused wherever needed. This improves maintainability because future changes are made in the child Integration Procedure instead of being copied manually across many parent procedures. It also supports cleaner modular design: one procedure can handle a specific reusable operation, while parent procedures orchestrate the overall flow. Option A is not the key advantage because asynchronous behavior depends on specific chainable or queueable configuration. Option B is wrong because exception handling may still be required. Option C is not guaranteed, especially when chainable execution is used. The central design benefit is reuse and modularity of server-side logic.

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

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.

In OmniStudio Integration Procedures, when referencing data from a prior step in the HTTP Action URL, the correct merge code syntax is:

%ElementName.PropertyName%

So, referencing a value called Date from a step named SetValues must be written as:

%SetValues.Date%

This is the format recognized by the OmniStudio Merge Language (OML) for dynamic value substitution in URLs or headers.

Incorrect Options:

A. Invalid syntax – not recognized by OmniStudio merge logic.

B. {{SetValues.Date}} is used in FlexCards, not in Integration Procedures.

D. %SetValues: Date% is incorrect merge syntax due to space and colon use.

Salesforce OmniStudio Documentation ? Merge Code Syntax for Integration Procedures

The AccountId is not the issue because the Debug Log already shows that the Data Mapper Extract retrieved data successfully. The failure is at the response-return stage of the Integration Procedure. In OmniStudio, a Response Action is used to end the Integration Procedure and return data to the caller. If the Data Mapper action runs but no Response Action is configured, the internal debug data can exist while the external response remains empty. Option A is weaker because the core requirement is not only adding data to an internal response JSON property; the Integration Procedure needs a Response Action to send the final output. Option C adds unnecessary and inaccurate wording about Send JSON Path. The clean verified cause is that no Response Action was added.

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

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

 A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(‘Hello’, ‘World’)}} or {{DATEDIFF(‘2021-01-01’, ‘2021-01-31’)}}.

To launch an OmniScript from a FlexCard, the Action element must identify the target OmniScript by its Type, SubType, and related configuration. Because the OmniScript requires the Case ID, the developer must explicitly pass the FlexCard data value, such as CaseId, through the action’s input mapping. Option D is unsafe because the OmniScript does not automatically know which Case ID to use unless the value is passed through context or input parameters. Option B confuses launching the OmniScript with saving Case data; the Data Mapper Load would be used later inside the OmniScript or Integration Procedure. Option C describes a more custom LWC-style configuration, not the standard OmniScript Action setup from a FlexCard.

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

The requirement is element-level visibility: only one Overdue status block must appear when Account Balance is greater than zero. The correct FlexCard configuration is a rendering condition directly on the Block element. FlexCard element conditions are designed to show relevant information based on field values from the card’s data source. Creating a separate Card State is excessive because the whole card layout does not need to change; only one block must be conditionally visible. A Setup tab filter controls data retrieval, not the display of a specific UI block after data is returned. A Flyout action is also unrelated because it opens additional content after user interaction. The verified implementation is to add a rendering condition to the Block element.

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

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.

 According to the FlexCard Designer Overview page, one possible cause of a field showing only the label is that “the field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name”. 

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.

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

he Aggregation Step in a calculation procedure allows the developer to perform aggregate functions such as SUM, COUNT, MIN, MAX, and AVG on the output of a previous step. The developer can use this step to calculate the sum of the entire base price by specifying the field name and the aggregation function

The verified answer is C. The selected answer in the PDF appears to be wrong. For OmniStudio managed package runtime, upgrades are package-based and can require installing the newer managed package version. Salesforce documentation for installing or upgrading the OmniStudio package says to install the latest OmniStudio managed package by going to OmniStudio Managed Package Releases and using the installation URL. That is different from standard runtime behavior, where functionality is more directly tied to Salesforce platform releases. Option D incorrectly treats managed package runtime as automatically upgraded only through seasonal Salesforce releases. Option A is wrong because a support case is not the normal upgrade mechanism. Option B overstates the process; deactivating all components is not the defining characteristic.

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