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

For an active OmniScript, the correct practice is to create a new version, make the change in that new version, test it, and activate it only when it is ready. Editing the active version directly is risky because users can be affected immediately, and in-flight users may experience inconsistent behavior. Cloning creates a separate component and is useful when the new script must be independent, but it is not the best approach for a minor controlled change to the same OmniScript. Waiting for a Salesforce release is irrelevant because this is a configuration lifecycle issue, not a platform-release dependency. Salesforce’s OmniStudio versioning guidance supports using versions so changes can be validated before replacing the active version used by end users.

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

 The correct syntax for passing all of the parent FlexCard’s records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.

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.

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

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

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

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.

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

Two separate Group elements with mutually exclusive conditions provide the cleanest declarative control. One Group should execute only when updateBillingAddress is true and updateShippingAddress is false. The other Group should execute only when updateShippingAddress is true and updateBillingAddress is false. This enforces that only one address update path runs. A single OR condition would allow either or both flags to be true, so it cannot prevent simultaneous updates. A Try-Catch Block reacts after an error occurs; it is not the right way to express business-rule branching. An HTTP Action would add unnecessary external dependency. Integration Procedure blocks and groups are designed to run related steps conditionally, so mutually exclusive Group conditions are the correct structure.

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

The Remote Action node is identified by the element name configured in the Integration Procedure. Since the Remote Action is named FetchCart, the relevant Preview JSON node for that action is FetchCart. The debug-specific node, such as FetchCartDebug, is used for diagnostic details, not as the primary action node being evaluated in this question. ResponseCart and ResponseCartDebug belong to the Response Action, not the Remote Action. Salesforce documentation confirms that a Remote Action in an Integration Procedure calls the specified Apex class, method, or invocable action, and Integration Procedure actions are configured and executed as named elements in the procedure sequence.

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

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

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

The correct tool is the Test Data and Parameters panel in the FlexCard Designer. The requirement is specifically to test the FlexCard directly in its designer with different JSON inputs before deployment. The OmniScript Test Console is for OmniScript logic, not FlexCard data rendering. IDX Workbench is a migration/deployment tool, not the FlexCard’s built-in data-testing panel. A Data Mapper Turbo Extract preview only tests the Data Mapper query output; it does not validate how the FlexCard processes different JSON structures and renders states, fields, or conditional elements. Salesforce documentation for FlexCard testing describes adding test parameters in the FlexCard Designer and previewing/debugging the card using those values, which directly supports option C.

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

The Conditional View property on the Step elements is the correct client-side control. The branching depends on a value selected earlier in the OmniScript, and the constraint explicitly says not to use server-side logic. Conditional View can hide or show elements, blocks, or steps based on conditions in the OmniScript data JSON. Pub/Sub on FlexCard elements is unrelated because this is an OmniScript step-visibility problem, not inter-component messaging. An Integration Procedure conditional block would push the path decision to server-side logic, violating the requirement. A Data Mapper does not control UI step visibility. Salesforce documentation states that Conditional View hides an element or group of elements in a block or step based on specified conditions, which fits this scenario precisely.

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

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.

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

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

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.

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

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

The Repeatable Mode property on the data table elements allows the developer to display multiple records in a single data table. The Repeat Records feature on the FlexCard Setup tab is used to display multiple FlexCards for each record in a data source. The Record Looping feature on the data table elements is used to iterate over a list of records and perform actions on each record. The Overwrite Target for all Null input checkbox on the Account id field is used to overwrite the existing value in the target object with null if the input value is null.

The correct configuration is the Knowledge Articles property on the Step element. OmniScript supports Salesforce Knowledge integration through Knowledge Options configured on a Step. This lets the developer display or filter Knowledge content where the user needs it in the guided process, such as a complex product-information step. A Knowledge Action is not the standard OmniScript element used for step-level help article display. Messaging Framework is unrelated because it handles messaging behavior, not Knowledge article rendering. A custom LWC could be built, but that would be unnecessary custom development when OmniScript already provides Knowledge configuration on the step. The requirement is step-specific, context-sensitive article display, so the Step element’s Knowledge Articles configuration is the correct answer.

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