Salesforce Certified Omnistudio Consultant — Practice Exam Set 1

Question 1

What is Salesforce OmniStudio?

Accepted Answer

OmniStudio (originally Vlocity) is Salesforce's suite of industry-specific, declarative digital engagement tools: OmniScripts (guided user interactions), DataRaptors (data mapping), FlexCards (contextual UI components), and Integration Procedures (server-side orchestration). It is primarily used in industries like Communications, Insurance, Healthcare, and Financial Services for complex guided selling, service, and onboarding processes.

Question 2

Which OmniStudio tool is used to build a guided, multi-step digital interaction for users (such as a quote wizard or service request form)?

Accepted Answer

OmniScript is the OmniStudio tool for building guided, multi-step digital interactions — wizards, forms, and processes that walk users (or customers in self-service portals) through complex workflows step by step. OmniScripts can include conditional logic, data lookups, validation, and integration calls. They render as responsive HTML UI components.

Question 3

OmniStudio tools work together to deliver guided processes. Which two OmniStudio components can be called from within an OmniScript? (Choose 2)

Accepted Answer

Within an OmniScript, you can invoke: DataRaptors (using the DataRaptor Extract/Transform/Load action elements) to read and write Salesforce data; Integration Procedures (using the Integration Procedure action element) to run complex server-side orchestrations involving multiple data sources. FlexCards are standalone UI components embedded in Lightning pages, not called within OmniScript steps. Salesforce Reports are not callable from OmniScript.

Question 4

OmniStudio uses a JSON data model internally. What does this mean for data passed between OmniScript steps?

Accepted Answer

OmniStudio uses a centralized JSON object (often called DataJSON or the OmniScript data store) that persists throughout the entire OmniScript session. User inputs, DataRaptor outputs, and Integration Procedure responses all accumulate in this JSON structure. Later steps can reference values from earlier steps using JSON path notation (e.g., `%SomeStep:fieldName%`). This unified JSON model makes data flow between steps seamless.

Question 5

Which Salesforce product introduced OmniStudio capabilities to the Salesforce platform?

Accepted Answer

OmniStudio originated as a product called Vlocity, which was built on Salesforce and specialized in industry-specific cloud applications (Communications, Insurance, Healthcare, Government). Salesforce acquired Vlocity in 2020 and rebranded its toolset as OmniStudio, incorporating it into Salesforce Industries products. Today OmniStudio is available across multiple Salesforce Industries clouds.

Question 6

What is a 'Step' in an OmniScript?

Accepted Answer

A Step in OmniScript represents one page or screen in the guided interaction. Each Step groups related input elements (text fields, dropdowns, checkboxes, lookups) and is presented to the user as a distinct stage in the process wizard. Steps can have conditional visibility and navigation logic. A typical OmniScript might have steps like 'Customer Information', 'Product Selection', 'Review', and 'Confirmation'.

Question 7

In an OmniScript, which element type allows the user to select from a list of options that are dynamically fetched from a Salesforce object?

Accepted Answer

The Lookup element in OmniScript provides a dynamic search field that queries Salesforce records (or custom DataRaptor extracts) as the user types, displaying matching results. It is equivalent to a Salesforce lookup field and allows selecting related records (e.g., selecting an Account when creating a Case in an OmniScript). The Type Ahead element also provides search but works with locally cached or pre-fetched options.

Question 8

An OmniScript Step should only appear when the user selects 'Yes' to a Yes/No question on a previous Step. Which feature implements this?

Accepted Answer

OmniScript Steps and Elements support Condition Rules (also called Conditional View) — declarative rules that show or hide a step/element based on the current value of another element in the DataJSON. For example, a Condition Rule on Step 2 can check: 'Show when `%Step1:eligibleForUpgrade%` equals true'. This enables conditional navigation without code. Note: Steps shown/hidden via conditions may still appear in the step indicator unless navigation conditions are also configured.

Question 9

An OmniScript needs to pre-populate a field with the current Account's Name when launched from an Account record page. Which two configurations achieve this? (Choose 2)

Accepted Answer

To pre-populate an OmniScript with record context: (1) Configure the OmniScript launch to receive the record ID as an input parameter (e.g., via FlexCard action, Quick Action, or Experience Site); (2) At the start of the OmniScript, add a DataRaptor Extract action that uses the received Account ID to query the Account Name and other fields, pre-populating the relevant elements. OmniScripts do not automatically inherit page record data — it must be explicitly passed.

Question 10

In an OmniScript, what is the purpose of the 'Set Values' element?

Accepted Answer

The Set Values element in OmniScript is used to programmatically assign values to data nodes in the DataJSON without requiring user input. This is useful for setting default values, computing derived values, transforming data formats, or copying values between different nodes in the JSON. It runs as an action (server-side or client-side) and does not display anything to the user.

Question 11

An OmniScript needs to repeat a group of elements (like line items in an order) for a variable number of entries. Which element supports this repeatable section?

Accepted Answer

The Repeat (or Group and Repeat) element in OmniScript creates a dynamic, user-expandable group of elements — similar to an editable row in a table. Users can add new rows (instances of the element group) or remove existing ones. The data is stored as a JSON array. This is the standard way to handle variable-length collections (order line items, contacts to add, products selected) in an OmniScript without knowing the count in advance.

Question 12

What are the four types of DataRaptor?

Accepted Answer

The four DataRaptor types are: Extract (reads data from Salesforce objects using SOQL-like configuration), Transform (transforms data between JSON structures without Salesforce I/O), Load (writes data to Salesforce objects — insert, update, upsert, or delete), and Turbo Extract (a faster, read-only extract that directly queries Salesforce for simple data retrieval without the full DataRaptor engine overhead).

Question 13

When would you use a DataRaptor Turbo Extract instead of a regular DataRaptor Extract?

Accepted Answer

DataRaptor Turbo Extract is optimized for speed on simple read operations. It directly executes SOQL and returns results with minimal processing, making it significantly faster than a full DataRaptor Extract for straightforward record retrieval use cases. Use Turbo Extract for read-only operations where you don't need complex field mapping or data transformation. Use regular Extract when you need to traverse relationships, apply transformations, or map fields to a different JSON structure.

Question 14

A DataRaptor Load is being configured to create a new Case and related CaseComment in a single operation. Which two features of DataRaptor Load support writing to multiple related objects? (Choose 2)

Accepted Answer

DataRaptor Load supports multiple Output Objects in a single configuration for writing to parent and child objects in sequence. The child object's Output Object configuration can reference the parent object's generated record ID using a special key reference. The Save Action on each Output Object (Insert, Update, Upsert, or Delete) determines the DML operation. This allows a single DataRaptor Load to create the Case and its related CaseComment in one execution.

Question 15

A DataRaptor Transform is used to:

Accepted Answer

DataRaptor Transform operates purely on JSON data — it takes input JSON (from an OmniScript DataJSON, Integration Procedure output, or other source) and maps/transforms it to a different output JSON structure. It performs NO Salesforce DML or SOQL. Common uses include restructuring API response data before displaying it, reformatting OmniScript data before calling a DataRaptor Load, or aggregating data from multiple sources into a single structured output.

Question 16

A DataRaptor Extract is configured with a filter on the Account object: 'Id = :recordId'. The `:recordId` notation means:

Accepted Answer

In DataRaptor Extract filter conditions, the `:parameterName` notation (colon prefix) indicates a runtime input parameter. The actual value is passed to the DataRaptor when it is called from an OmniScript action, Integration Procedure, or FlexCard. For example, an OmniScript passes `recordId` from its context (or input parameters) to the DataRaptor, which uses it to filter records. This parameterization makes DataRaptors reusable across different contexts.

Question 17

A consultant is designing an OmniScript that saves data to multiple Salesforce objects on the final step. Which two approaches minimize the number of DML operations and improve performance? (Choose 2)

Accepted Answer

Performance best practices for multi-object writes: (1) A single DataRaptor Load can write to multiple objects (parent-child) in one call, reducing round trips; (2) An Integration Procedure orchestrates multiple server-side operations (DataRaptor Loads, Apex calls) in a single server call from the client OmniScript, dramatically reducing client-server round trips compared to sequential client-side action elements. Multiple sequential DataRaptor Loads from OmniScript steps make multiple round trips. Direct Apex calls are available but bypass OmniStudio's declarative model.

Question 18

What is a FlexCard in OmniStudio?

Accepted Answer

A FlexCard is an OmniStudio UI component that displays contextual data for a record or set of records and provides quick action buttons. FlexCards can be stacked (child FlexCards within parent FlexCards), use DataRaptor or Integration Procedure data sources, and launch OmniScripts or other actions from their buttons. They are placed on Lightning record pages (or Experience Cloud sites) to give agents a contextual 360-degree view with actionable options.

Question 19

A FlexCard needs to display Account and related Contact data simultaneously. What is the recommended data source approach?

Accepted Answer

A DataRaptor Extract can traverse Salesforce relationships to retrieve fields from parent and child objects in a single query configuration. For a FlexCard showing Account and related Contact data, a single DataRaptor Extract that joins Account and Contact (using relationship traversal in the Field Mapping configuration) retrieves all needed data in one server call. This is more performant than two separate DataRaptor calls.

Question 20

A FlexCard is configured to show a list of related orders for an Account. Which two FlexCard features support displaying multiple records as a list? (Choose 2)

Accepted Answer

FlexCards support displaying collections of records in two primary patterns: (1) Child FlexCards — nested FlexCards that iterate over a collection from the parent's data source, rendering one card instance per record; (2) FlexCard states — one state can be configured as a Data Table (list/grid view) that renders the collection in tabular format with columns. State styling is for visual formatting of individual records, not collection display. Repeat sections are an OmniScript concept.

Question 21

A FlexCard action button should launch an OmniScript to capture additional information when clicked. Which action type on the FlexCard button supports this?

Accepted Answer

FlexCard action buttons have an 'OmniScript' action type that directly launches a specified OmniScript. The FlexCard automatically passes the current record's ID and other context as input parameters to the OmniScript. The OmniScript opens in a modal or slide-out panel (configurable). This is the native, no-code way to connect FlexCards to guided OmniScript interactions — no custom Apex or navigation configuration needed.

Question 22

What is the primary advantage of using an Integration Procedure instead of calling individual DataRaptors sequentially from an OmniScript?

Accepted Answer

Integration Procedures are server-side orchestration tools. When called from an OmniScript, all the Integration Procedure's steps (DataRaptor calls, Apex calls, HTTP actions, conditional logic) execute in a single server-side process with a single client-to-server round trip. In contrast, calling individual DataRaptors sequentially from an OmniScript client creates a round trip per action, introducing significant latency. This is the primary architectural advantage of Integration Procedures.

Question 23

Which Integration Procedure element is used to call an external REST API endpoint?

Accepted Answer

The HTTP Action element in Integration Procedures is used to make outbound HTTP calls to external REST APIs. It supports GET, POST, PUT, PATCH, DELETE methods and can pass input data as request body or URL parameters, and map the response JSON to the Integration Procedure's data context. Named Credentials can be used to manage authentication for the external endpoint. This enables OmniStudio to integrate with third-party APIs without custom Apex callouts.

Question 24

An Integration Procedure needs to retrieve Account data, call a pricing API, and save the result. If the pricing API call fails, the saved data should not be written. Which two features enable transactional control? (Choose 2)

Accepted Answer

Integration Procedures do NOT automatically rollback Salesforce DML if a step fails mid-execution. Transactional control requires explicit design: (1) Using a Conditional element to check the HTTP response status and branch to an error response path BEFORE executing the DataRaptor Load; (2) Configuring the HTTP Action to throw an error on non-200 responses, which stops execution of subsequent steps (including the DataRaptor Load). Both approaches prevent the write from occurring after an API failure.

Question 25

An Integration Procedure needs to call an Apex class for custom business logic that cannot be performed with DataRaptors or HTTP Actions. Which element type enables this?

Accepted Answer

The Apex Remote element in Integration Procedures (and OmniScript action elements) allows calling Apex class methods decorated with @InvocableMethod or @AuraEnabled directly from within the Integration Procedure's execution. This provides an escape hatch for complex custom logic that exceeds the capabilities of DataRaptors and HTTP Actions. The Apex method receives input from the Integration Procedure's data context and returns results back into the context.

Plat-Con-201 — Salesforce Certified OmniStudio Consultant