OmniStudio-Developer Exam Questions With Explanations

The best OmniStudio-Developer practice exam questions with research based explanations of each question will help you Prepare & Pass the exam!

Start Practice Free
Over 15K Students have given a five star review to SalesforceKing

Why choose our Practice Test

By familiarizing yourself with the OmniStudio-Developer exam format and question types, you can reduce test-day anxiety and improve your overall performance.

Up-to-date Content

Ensure you're studying with the latest exam objectives and content.

Unlimited Retakes

We offer unlimited retakes, ensuring you'll prepare each questions properly.

Realistic Exam Questions

Experience exam-like questions designed to mirror the actual OmniStudio-Developer test.

Targeted Learning

Detailed explanations help you understand the reasoning behind correct and incorrect answers.

Increased Confidence

The more you practice, the more confident you will become in your knowledge to pass the exam.

Study whenever you want, from any place in the world.

Salesforce OmniStudio-Developer Exam Sample Questions 2026

Start practicing today and take the fast track to becoming Salesforce OmniStudio-Developer certified.

2944 already prepared
Salesforce 2026 Release
94 Questions
4.9/5.0

A developer needs to display read-only contact information in a OmniScript. The developer will format the information as a table, using merge codes to dynamically include first name, last name, street address, state, postal, code, and country from the data JSON.
Which OmniScript element should the developer use to meet this requirement?

A. Rich text Area

B. Text area

C. Text Block

D. Edit Block

C.   Text Block

Summary
The requirement is to display formatted, read-only information in a table-like structure using merge codes to pull dynamic data. The element must support rich text formatting (like HTML tables) and merge fields, while preventing user editing. This calls for a display element that can render structured content without providing input capabilities.

Correct Option

C. Text Block
This is the correct element for this requirement. The Text Block element allows developers to enter formatted text using HTML, including creating tables with , , and

tags. It fully supports merge codes (e.g., %FirstName%, %Address_Street%) to dynamically insert data from the OmniScript's JSON. Most importantly, it is read-only by nature, making it perfect for displaying information that should not be edited by the user.

Incorrect Option

A. Rich text Area
A Rich Text Area is an input element that allows users to enter and format text. While it supports rich formatting, it is designed for user input, not for displaying read-only information. Using it for display would be incorrect and could allow users to modify the contact information.

B. Text area
A Text Area is a plain-text input field. It does not support rich text formatting (like tables) or HTML rendering. It is designed for multi-line user input and cannot be used to create a formatted table layout.

D. Edit Block
An Edit Block is an interactive element that allows users to edit, add, and delete multiple records in a table-like structure. It is fundamentally an input component for managing collections of data, not for displaying static, read-only information in a formatted layout.

Reference
Salesforce OmniStudio Developer Guide: Text Block Element

A developer is creating a FlexCard and needs to display additional information using a Flyout. Which two types of components can the developer embed in the flyout?
(Choose 2 answer)

A. An OmniScript

B. An Integration Procedure

C. A DataRaptor

D. A Child FlexCard

A.   An OmniScript
D.   A Child FlexCard

Summary
A Flyout is a UI component in OmniStudio that appears dynamically (e.g., on hover or click) to display additional information without navigating away from the main screen. It acts as a container for other interactive components. The elements that can be embedded within a Flyout are those that provide a user interface or visual representation, allowing for a rich and interactive user experience directly from the FlexCard.

Correct Option

A. An OmniScript
An OmniScript can be embedded within a Flyout. This allows the Flyout to present a multi-step, guided form for tasks like updating information or submitting a request without requiring the user to leave the context of the FlexCard. The OmniScript provides a structured user interface and logic flow.

D. A Child FlexCard
A Child FlexCard can be embedded within a Flyout. This is a common pattern for displaying related records or more detailed information in a structured card format. The Child FlexCard can have its own data source and design, providing a modular way to show additional data.

Incorrect Option

B. An Integration Procedure
An Integration Procedure is a headless, server-side component used for data processing and orchestration. It does not have a visual interface and therefore cannot be displayed or embedded directly within a Flyout. An Integration Procedure can be called by an OmniScript or FlexCard within the Flyout, but it is not the embedded component itself.

C. A DataRaptor
A DataRaptor is a data manipulation tool used for extracting, transforming, or loading data. Like an Integration Procedure, it is a headless component with no user interface. It cannot be embedded in a Flyout. A DataRaptor is used as a data source for a FlexCard or OmniScript that is embedded in the Flyout.

Reference
Salesforce OmniStudio Developer Guide: Configure a Flyout

Refer to the exhibit below. A developer has configured an integration Procedure element with Additional input.
Alternatively, how could the developer configure SEND/RESPONSE TRNSFORMATION to send exactly the same data? Assume the developer has un-checked Send Only Additional input.

A. Option A

B. Option B

C. Option C

D. Option D

A.   Option A

Summary:
This question evaluates how to configure SEND/RESPONSE TRANSFORMATIONS in an Integration Procedure element to replicate the data sent via Additional Input (key "SecondaryAccount" with value "#{DRExtractAction:Account}"), with "Send Only Additional Input" unchecked. The configuration should use Send JSON Path and Send JSON Node to match the original data structure.

Correct Option:

A. Option A
Option A correctly sets the Send JSON Path to "DRExtractAction:Account" and the Send JSON Node to "SecondaryAccount". This configuration extracts the data from DRExtractAction:Account and assigns it to the SecondaryAccount node, matching the Additional Input setup when "Send Only Additional Input" is unchecked.

Incorrect Option:

B. Option B
Option B reverses the Send JSON Path and Send JSON Node, setting Send JSON Path to "#SecondaryAccount#" and Send JSON Node to "DRExtractAction:Account". This incorrectly treats SecondaryAccount as a path and DRExtractAction:Account as a node, leading to mismatched data mapping.

C. Option C
Option C sets Send JSON Path to "SecondaryAccount" and Send JSON Node to "DRExtractAction:Account". This configuration attempts to use SecondaryAccount as a path, which is invalid since it should be the node, not the source data path.

D. Option D
Option D sets Send JSON Path to "DRExtractAction:Account" and Send JSON Node to "SecondaryAccount", but includes an erroneous space in "Secondary Account". This inconsistency in naming may cause the integration to fail to recognize the node correctly.

Reference:
Salesforce Help: Integration Procedures

Which two fields in an Integration Procedure can use a function like CONCAT or DATEDIFF?
(Choose 2 answers)

A. In Procedure Configuration, ina TrackingCustom Data value field.

B. In a Remote Action, in a Remote Options value field.

C. In a Remote Action, in an Additional Output value field.

D. In a Response Action, in an Additional input value field.

C.   In a Remote Action, in an Additional Output value field.
D.   In a Response Action, in an Additional input value field.

Summary
OmniStudio functions like CONCAT or DATEDIFF are used to dynamically transform or calculate values within the Integration Procedure's data pipeline. They can be applied in fields that map data within the procedure's execution flow. Specifically, they are used to create new, calculated output values or to structure the final response, not for static configuration or external API settings.

Correct Option

C. In a Remote Action, in an Additional Output value field.
The "Additional Output" section of a Remote Action is used to define new fields derived from the action's results. Here, you can use functions like CONCAT to combine values from the remote response or DATEDIFF to calculate time spans, creating new data points in the pipeline for subsequent actions to use.

D. In a Response Action, in an Additional Input value field.
The "Additional Input" section of a Response Action allows you to add new fields to the final JSON response. You can use functions here to perform final transformations on the data from the pipeline before it is sent back. For example, using CONCAT to format a full name or DATEDIFF to calculate an age just before the response is returned.

Incorrect Option

A. In Procedure Configuration, in a Tracking Custom Data value field.
The Tracking Custom Data fields in the Procedure Configuration are for attaching static, high-level metadata to the entire procedure for analytics or logging purposes. They are not part of the dynamic data pipeline and do not support the use of real-time calculation functions like CONCAT or DATEDIFF.

B. In a Remote Action, in a Remote Options value field.
The "Remote Options" section is used to configure the HTTP request to the external system (e.g., headers, endpoint parameters). These values are typically static strings or simple pipeline references ({...}). They do not support the evaluation of OmniStudio formula functions, as these functions are executed by the OmniStudio runtime, not the external service.

Reference
Salesforce OmniStudio Developer Guide: Formula Functions

A developer writes an OmniScript that includes a DataRaptor that updates the Account status based on information provided from the OmniScript. The information must be updated only if the Account record already exists. Otherwise, a new account must be created. How should the developer accomplish this task?

A. Check the Upsert Key checkbox on the Account Status field

B. Check the Upsert Key and Is Required for Upsert check boxes on the Account Id field

C. Populate the Lookup Object and Lookup Fields

D. Check Overwrite Target for All Null Inputs checkbox on the Account Id field

B.   Check the Upsert Key and Is Required for Upsert check boxes on the Account Id field

Summary
The requirement is to update an existing Account if it exists, or create a new one if it does not. This is the definition of an "upsert" operation. In a DataRaptor Load, an upsert requires specifying a unique field to match on (the Upsert Key). The Account Id (the Salesforce record ID) is the standard field for this, as it uniquely identifies an existing record. If provided, the record is updated; if not, a new one is created.

Correct Option

B. Check the Upsert Key and Is Required for Upsert checkboxes on the Account Id field
This is the correct configuration. Checking Upsert Key on the Account Id field tells the DataRaptor to use this field to find an existing record. Checking Is Required for Upsert ensures the upsert logic is dependent on this field. If the OmniScript provides an Account Id, the existing record is updated. If the Account Id is null/empty, the DataRaptor will create a new Account record, fulfilling the requirement.

Incorrect Option

A. Check the Upsert Key checkbox on the Account Status field
Using the "Account Status" field as the Upsert Key is incorrect. The upsert key must be a unique identifier for the record, like the Id or a custom external ID field. "Account Status" is a data field that is not unique, so using it as a key would cause errors or update the wrong record if multiple accounts shared the same status.

C. Populate the Lookup Object and Lookup Fields
The Lookup fields in a DataRaptor are used to populate a relationship field on the record being saved (e.g., looking up a Contact to set the AccountId on an Opportunity). They are not used to determine whether to update an existing record or create a new one. This is unrelated to the upsert operation.

D. Check Overwrite Target for All Null Inputs checkbox on the Account Id field
This setting controls how null values from the input are handled during an update. If checked, a null input would overwrite an existing value on the target record with null. It has no bearing on the core logic of deciding between an insert or an update (upsert).

Reference
Salesforce OmniStudio Developer Guide: Configure a DataRaptor Load

Prep Smart, Pass Easy Your Success Starts Here!

Transform Your Test Prep with Realistic OmniStudio-Developer Exam Questions That Build Confidence and Drive Success!