Certified OmniStudio Developer

Here you have the best Salesforce Certified OmniStudio Developer practice exam questions

  • You have 77 total questions to study from
  • Each page has 5 questions, making a total of 16 pages
  • You can navigate through the pages using the buttons at the bottom
  • This questions were last updated on November 12, 2024
Question 1 of 77

A developer is creating an OmniScript that provisions trial orgs to their customers. The following text block in the OmniScript uses a merge code to display the ID for the new trial org:

Welcome to Salesforce!

Your ID is %Details:Customer|0:ID%

During testing, the developer notices that the ID does not display. The data JSON is structured as shown below.

How should the developer correct the merge code in order for the ID to display?

    Correct Answer: B

    The correct merge code syntax for referencing a field in OmniScript is to use a dollar sign ($) followed by the merge code. The JSON data provided shows that 'Customer' is an array with the ID located at index 0. Therefore, the correct merge code to display the ID should be '$Details:Customer|0:ID$'. This correctly references the first element of the Customer array and the ID field.

Question 2 of 77

A developer is building an OmniScript and needs to retrieve data from many fields in a Salesforce record.

Which OmniScript element does this?

    Correct Answer: D

    The OmniScript element that allows a developer to retrieve data from many fields in a Salesforce record is the DataRaptor Extract Action. This element is designed to retrieve data from Salesforce, allowing the specification of objects and fields to be pulled into the OmniScript. This makes it suitable for retrieving extensive data efficiently from Salesforce records.

Question 3 of 77

A developer creates an OmniScript to display FirstName, LastName, and BirthDate of a contact using a Type Ahead Block. The DataRaptor used in the Type Ahead has been tested and fetches the correct data.

When previewing the OmniScript, the developer enters a name in the Type Ahead and makes a selection of a contact from the list. However, the text fields FirstName, LastName. and BirthDate are not getting populated with the data.

Refer to the exhibit below.

What is the reason that the fields fail to display the fetched data?

    Correct Answer: A

    The issue lies in the configuration of the Type Ahead Block. For the fields to display the fetched data, the option 'Use Data JSON' needs to be selected in the properties of the Type Ahead Block. This setting allows the fetched data to be populated in the specified fields. Without selecting 'Use Data JSON', the fetched data will not be transferred to the fields FirstName, LastName, and BirthDate, thus failing to display the information even if the data is fetched correctly by the DataRaptor.

Question 4 of 77

An OmniScript displays data from an API using an Integration Procedure, but all of the data is missing. What two errors could cause this? (Choose two.)

    Correct Answer: A, B

    There are two potential errors that could cause an OmniScript to display no data from an API using an Integration Procedure. First, the API URL might not be allowlisted in Salesforce, which would block any communication with the API. Second, if the JSON sent from the Integration Procedure Action does not match any of the Original Input for the Integration Procedure, the data retrieval process would fail, resulting in no data being displayed.

Question 5 of 77

An Integration Procedure uses an HTTP action to make a REST API call. The response from the REST API must be converted into a specific XML structure before sending it as an input to another external web service.

How should the developer configure the Integration Procedure to meet this requirement?

    Correct Answer: A

    The appropriate action to take is to use a DataRaptor Transform to convert JSON to XML. DataRaptor Transforms are specifically designed to transform data from one format to another, including JSON to XML. This makes it straightforward to convert the response of a REST API call into the required XML structure before sending it as an input to another external web service.