Salesforce OmniStudio Consultant Salesforce Certified OmniStudio Consultant Exam Practice Test

Answer : B

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 . Design the parent card to launch a child card when the specific action is taken: While this is conceptually correct, it's vague and lacks specificity. ''Launch a child card'' isn't a defined OmniStudio action---Flyout Action is the actual mechanism to achieve this. Thus, B is the more precise answer, as it names the tool explicitly supported by FlexCards.

C . Design the parent card to launch a new DataRaptor when the specific action is taken: A DataRaptor (e.g., DataRaptor Extract) retrieves or manipulates data, not displays a UI like a child card. While a DataRaptor might fetch data for the child card, it doesn't ''launch'' anything visible to the agent, making this option irrelevant to the UI requirement.

D . Design the parent card to launch a new OmniScript when the specific action is taken: An OmniScript could be launched via a FlexCard action (e.g., an ''OmniScript'' action type), but it's a guided process, not a ''child card.'' The requirement specifies a child card (implying another FlexCard), not a multi-step script, so a Flyout Action with a child FlexCard is more appropriate than an OmniScript.

Salesforce OmniStudio Documentation: FlexCard Actions -- Details the Flyout Action for launching child cards or content.

Salesforce OmniStudio Developer Guide: Flyouts in FlexCards -- Explains configuring flyouts with child FlexCards.

Answer : A

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

Answer : B, D, E

The three elements that the consultant should recommend to meet these requirements using an OmniScript are: Messaging, DataRaptor Post Action, and Steps. A Messaging element is an element that can display a text message with an icon and a color, such as blue for information or yellow for warning. The consultant can use a Messaging element to display the user's details on a page. A DataRaptor Post Action is an action that can write data to a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post Action to save the case details to Salesforce. A Step element is an element that can group related fields and elements in an OmniScript, and display them in a page or a section. The consultant can use multiple Step elements to organize the OmniScript into logical steps, such as entering employee id, displaying user details, and entering case details.

Answer : B

The OmniStudio tools that should be recommended to meet these requirements are single OmniStudio Action that invokes separate Omniscripts. OmniStudio Action can be used to conditionally launch different Omniscripts based on the record type of the contact. Omniscripts can be used to implement the verification processes for each type of contact. Specific FlexCards with Actions for each type of Contact would require creating redundant FlexCards and Actions for each record type. Multiple OmniStudio Actions that invoke separate Omniscripts would require creating redundant Actions for each record type. Single FlexCard with an Action to invoke an Omniscript would not allow for different verification processes based on the record type.

Answer : C, D, E

The three elements that the consultant should include in the OmniScript design solution are: Telephone, Line Break, and Text. A Telephone element can display a field for the user to enter a phone number, with validation and formatting options. A Line Break element can insert a line break between two elements, making them display on separate lines.A Text element can display a field for the user to enter text, such as a website URL

Answer : D

The consultant should design the FlexCard solution using card filter and multiple FlexCards to meet these requirements. A card filter is a property that determines which records are displayed in a FlexCard based on certain criteria. The consultant can use card filter to display only the cases with a specific status, such as Open, Awaiting Closure, or Closed. A FlexCard is a tool that can display data and actions in a card format. The consultant can create multiple FlexCards for each case status, and customize the fields and actions accordingly.The consultant can also use custom style to apply different borders for each case status

Answer : A, B, E

Based on the user analysis exhibit, the three actions that should appear on the card are: verify a transaction, request higher limit, and make a payment. These actions have the highest frequency and importance scores among the six actions listed.The other actions, such as view credit score history, view statements, and view rewards, have lower frequency and importance scores, and can be accessed through other means