Salesforce OmniStudio Consultant Practice Exams
Last updated on Oct 22,2026- Exam Code: OmniStudio Consultant
- Exam Name: Salesforce Certified OmniStudio Consultant Exam
- Certification Provider: Salesforce
- Latest update: Oct 22,2026
A consultant is working with a client who wants to create guided interactions using data from their Salesforce org and external sources.
Which Omnistudio tool should the consultant recommend for creating these guided interactions?
- A . Flexcards
- B . Integration Procedures
- C . Omniseripts
- D . Data Mappers
C
Explanation:
The requirement is to create "guided interactions" that utilize data from both a Salesforce org and external sources. In Salesforce OmniStudio, OmniScripts is the tool specifically designed for building interactive, guided processes that lead users through a series of steps, integrating and displaying data from multiple sources, including Salesforce and external systems.
Here’s why
C. OmniScripts is the correct answer:
Purpose of OmniScripts: OmniScripts are a core OmniStudio component used to create structured, step-by-step user experiences (guided interactions) that can incorporate data from Salesforce objects and external systems. They enable consultants to design dynamic, interactive interfaces with elements like text inputs, picklists, and buttons, guiding users through processes such as filling out forms, updating records, or completing workflows. OmniScripts support integration with other OmniStudio tools (e.g., DataRaptors and Integration Procedures) to fetch and manipulate data, making them ideal for this scenario.
Handling Data from Multiple Sources:
Salesforce Data: OmniScripts can use DataRaptors to extract or update data from Salesforce objects (e.g., retrieving Account details or updating a Case).
External Sources: OmniScripts can leverage Integration Procedures to call external APIs or systems (e.g., pulling customer data from an ERP system) and then display or process that data within the script.For example, an OmniScript could guide a user to input customer information, fetch related Salesforce records using a DataRaptor Extract, and retrieve payment history from an external API via an Integration Procedure―all within a single, cohesive interaction.
Guided Interaction Features: OmniScripts offer a drag-and-drop designer with elements like Steps, Inputs, and Actions, allowing consultants to craft a logical flow. Features like conditional visibility, validation rules, and navigation controls ensure the interaction is guided and user-friendly, meeting the client’s need for a structured experience.
Now, let’s examine why the other options are incorrect:
A consultant is working with a client who wants to use a Flexcard to display data from a specific
Salesforce object. The client is unsure which data source
What advice should the consultant give to the client?
- A . The client should choose a data source based on the speed of data retrieval
- B . The client should choose the data source that retrieves the most data.
- C . The client should choose a data source based on the number of records it can retrieve.
- D . The client should choose a data source that can retrieve data from the specific Salesforce object.
D
Explanation:
A FlexCard retrieves data from a Salesforce object using a data source such as DataRaptor Extract, Integration Procedure, or a direct Salesforce Object Query.
The correct approach is to choose a data source that specifically retrieves data from the required Salesforce object (D).
This ensures relevant data is fetched efficiently while maintaining performance and scalability.
A company has account Information that they want to display to agents in a summarized view. For each account they want to display icons that allow the user to launch guided processes for frequent tasks. The processes a reused in other parts of the business.
Which three OmniStudio tools are needed to meet these requirements? Choose 3 answers
- A . FlexCards
- B . Flyouts
- C . OmniStudio Actions
- D . Navigate Actions
- E . Omni Script
A,C,E
Explanation:
The three OmniStudio tools that are needed to meet these requirements are: FlexCards, OmniStudio Actions, and OmniScript. A FlexCard is a tool that can display data and actions in a card format. The consultant can use a FlexCard to display the account information and icons for each action. An OmniStudio Action is a button that can invoke an OmniScript or an Integration Procedure from a FlexCard. The consultant can use OmniStudio Actions to launch guided processes for frequent tasks, such as change of plan, new sale, or loyalty. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use OmniScripts to create the guided processes for each task
A business is creating a new OmniScript that will allow agents to launch a guided selling process from an account detail page.
The consultant reviews the initial design proposed for the OmniScript and sees that the process the following steps:
• Step 1: Enter account name to retrieve account information
• Step 2: Review and edit account information
• Step 3: Select products
• Step 4: Enter payment information
Following best practices, what suggestion should the consultant make to improve the design?
- A . Remove Step 1 and prefill the account information automatically.
- B . Divide Step 2 into two steps, so each task is distinct.
- C . Use an Edit Block in Step 4 to enter payment information.
- D . Use Multi-select elements in Step 3 for the product list.
A
Explanation:
The consultant should suggest removing Step 1 and prefilling the account information automatically to improve the design. Since the OmniScript will be launched from an account detail page, there is no need to ask the user to enter the account name again. The consultant can use an Input Parameter element to pass the account ID from the page to the OmniScript, and then use a DataRaptor Extract Action element to retrieve the account information and display it in Step 2. This will save time and avoid errors
Service agents must confirm customer contact information in the first step of a payment OmniScript. Contact information includes name, telephone number, mobile number, and email. None of the contact information on first step is required.
On the last step, after taking payment, the agent can optionally email the receipt to the customer. If the customer says yes, the agent selects a checkbox. If the agent selects the box but the email address field is empty, the process must require the user to return to the first step and enter the customer’s email address.
What should the consultant recommend to meet this requirement?
- A . Add a Set Errors element
- B . Add a DataRaptor to retrieve the email address
- C . Add a Validation Rule to the Contact object
- D . Add a Conditional View to the last step
A
Explanation:
The consultant should recommend adding a Set Errors element to meet this requirement. A Set Errors element can display an error message and prevent the OmniScript from proceeding if certain conditions are not met. The consultant can use a Set Errors element to check if the email address field is empty when the agent selects the checkbox to email the receipt. If it is empty, the Set Errors element can show an error message and direct the user to return to the first step and enter the customer’s email address
Which element retrieves data from a Salesforce picklist in an org?
- A . DataRaptor Extract Action
- B . Lookup
- C . Select
- D . Calculation Action
- E . Mark this item for later review.
C
Explanation:
In Salesforce OmniStudio, the Select element within an OmniScript is specifically designed to retrieve
and display picklist values from a Salesforce object field, allowing users to choose from a predefined list of options. This element is used to create a dropdown or picklist interface in an OmniScript, enabling users to interact with Salesforce data by selecting a single value from the available options.
Here’s why Select is the correct answer:
The Select element in OmniScript supports multiple methods to populate its options, including retrieving values directly from a Salesforce picklist field. According to the official Salesforce OmniStudio documentation, you can configure the Select element’s “Option Source” to “SObject,” which allows it to fetch picklist values from a specified Salesforce object and field. For example, if you have a picklist field like Industry on the Account object, the Select element can retrieve all active picklist values (e.g., "Technology," "Healthcare," etc.) and present them as a dropdown to the user. The Select element is highly flexible and supports three option source types: Manual: Manually defined label-value pairs.
SObject: Retrieves options from a Salesforce object field (such as a picklist).
Custom: Uses an Apex controller for more complex logic.When set to “SObject,” it directly queries the Salesforce schema to pull the picklist metadata, ensuring the values reflect what’s defined in the org.
Now, let’s examine why the other options are incorrect:
A consultant is designing a FlexCard for a client. The client wants the FlexCard to launch a child card with additional information and actions related to the parent card when the agent clicks on a button.
How should the consultant design the FlexCard to meet the client’s requirements?
- A . Design the parent card to launch a child card when the specific action is taken.
- B . Design the parent card to launch a child card through a Flyout Action.
- C . Design the parent card to launch a new DataRaptor when the specific action is taken.
- D . Design the parent card to launch a new OmniScript when the specific action is taken.
B
Explanation:
Comprehensive and Detailed In-Depth The requirement is for a FlexCard (parent card) to launch a child card with additional information and actions when an agent clicks a button. In Salesforce OmniStudio, the Flyout Action is the specific mechanism designed within FlexCards to achieve this, making B the most precise and correct answer.
Here’s why
B. Design the parent card to launch a child card through a Flyout Action is the correct answer:
Flyout Action Overview: A Flyout Action in FlexCards is an interactive feature that displays a pop-up panel (flyout) when triggered, typically by a button or link. This flyout can contain a child FlexCard, OmniScript, or custom content, showing additional details or enabling actions related to the parent card’s data.
Meeting the Requirement:
Child Card Launch: The Flyout Action can embed a child FlexCard, which displays supplemental information (e.g., related records or details) and includes actions (e.g., buttons to update data). Button Trigger: In the FlexCard Designer, the consultant can add a Button element to the parent card, configure its action type as “Flyout,” and link it to a child FlexCard. When the agent clicks the button, the flyout appears with the child card.
Contextual Data: The parent card’s data (e.g., a record ID) can be passed to the child card via the Flyout Action’s context parameters, ensuring the child card shows relevant information. Example: If the parent card displays a customer’s summary (name, account number), clicking the button could launch a child card in a flyout showing order history and a button to initiate a return, all tied to the parent card’s account ID.
Now, let’s examine why the other options are incorrect or less optimal:
A company needs to generate invoices when contracts reach an approved status. Users should initiate the invoice generation process from the contract page, but the option should not appear until the contract reaches the approved status. After the invoice is generated, it should be sent to the customer for signature.
What three tools should be used in the solution the consultant recommends to meet these requirements? Choose 3 answers
- A . OmniScript
- B . Interaction Launcher
- C . FlexCards
- D . OmniStudio Action
- E . DataRaptor
A,D,E
Explanation:
The three tools that should be used in the solution are OmniScript, OmniStudio Action, and DataRaptor. OmniScript can be used to create a user interface for generating invoices from contracts. OmniStudio Action can be used to conditionally display the invoice generation option on the contract page based on the contract status. DataRaptor can be used to read, transform, and write data between Salesforce and external systems. Interaction Launcher is not needed for this scenario, as it is used to launch interactions from other applications. FlexCards are not relevant for this scenario, as they are used to display contextual data on record pages.
When a customer calls to add a new primary contact to their account, call center agents need to complete a I contact form. The agent enters the new contact information using an OmniScript and then needs to generate PDF with the contact information pre-filled that can be shared with the customer.
Which OmniStudio tool should the consultant recommend to generate the pre-filled PDF?
- A . OmniStudio Action
- B . Integration Procedure
- C . Data Maptor
- D . Calculation Procedure
C
Explanation:
The OmniStudio tool that the consultant should recommend to generate the pre-filled PDF is DataRaptor. A DataRaptor is a tool that can read, transform, and write data from Salesforce objects or JSON objects. A DataRaptor Load can write data to a PDF template using a PDF mapping file, and generate a PDF document with the contact information pre-filled. The PDF document can be stored as an attachment or a content document in Salesforce
In an Integration Procedure, what group element will control whether an individual action executes?
- A . Conditional Block
- B . Cache Block
- C . Try-Catch Block
- D . Loop Block
A
Explanation:
The group element that will control whether an individual action executes in an Integration Procedure is Conditional Block. Conditional Block allows the designer to specify a condition that determines whether the actions inside the block will run or not. Cache Block is used to store data in memory for later use. Try-Catch Block is used to handle errors and exceptions. Loop Block is used to iterate over a collection of data.