Available in 1, 3, 6 and 12 Months Free Updates Plans
PDF: $15 $60

Test Engine: $20 $80

PDF + Engine: $25 $99

OmniStudio-Developer Practice Test


Page 5 out of 24 Pages

A developer needs to display the following information together on oneFlexCard:

* Account name, address, phone number, website

* Primary contact first name, contact name, address, phone number, email

The account information must always be visible, and the contact information should only be visible as needed by the user.

What approach should the developer use to display the contact information on the card?


A. Use aData tableelement


B. Set the class’’ collapsible’’ on the block element


C. Set the collapsible property on the block element


D. Use a conditional FlexCard State





C.
  Set the collapsible property on the block element

Explanation:

Setting the collapsible property on the block element allows the user to expand or collapse the block as needed. Using a Data table element is not suitable for displaying contact information. Setting the class’’ collapsible’’ on the block element has no effect. Using a conditional FlexCard State requires a condition to be met, not a user choice.

When launching an OmniScript from an action on a FlexCard, the OmniScript displays, but no Salesforce data is populated:

Which two errors could cause this behavior?

Choose 2 answers


A. The Id Field for Actions in the FlexCard is blank.


B. There is no active version of the Data Raptor Extract.


C. There isnonactive version of the OmniScript


D. In the DataRaptor Extract Action, the Input Parameters Filter Value is misspelled.





A.
  The Id Field for Actions in the FlexCard is blank.

D.
  In the DataRaptor Extract Action, the Input Parameters Filter Value is misspelled.

Explanation:

The Id Field for Actions in the FlexCard specifies which field from the FlexCard data source will be used as the record ID for the OmniScript. If this field is blank, the OmniScript will not receive any record ID and will not be able to retrieve any Salesforce data. In the DataRaptor Extract Action, the Input Parameters Filter Value determines how to filter the data based on the record ID. If this value is misspelled, the DataRaptor Extract will not be able to match the record ID and will not return any data.

A developer creates an Integration Procedure with a Set Values and a DataRaptor Extract Action that requires AccountId as a key. When the developer previews the Integration Procedure, thedeveloper enters the AccountId correctly and execute the Preview. The developer sees the data extract by the DataRaptor in the Debug Log, but the response is empty. What is the likely cause of this issue?


A. The DataRaptor Action did not have the add response Ro Response JSON property set to true.


B. The Response cannot be previewed directly.


C. A Response Action was not added to the integration Procedure.


D. The AccountId used for the preview is invalid.





C.
  A Response Action was not added to the integration Procedure.

Explanation:

According to the OmniStudio Developer Guide, “To return a response from an Integration Procedure, add a Response action as the last action in your Integration Procedure.” Therefore, the correct answer is C.

A developer needs to configure a DataRaptor to retrieve data from a singleobject. Thestructure of the output data does not need to be changed. Following best practices, which type of DataRaptor should the developer use?


A. DataRaptor Transform


B. DataRaptor Extract


C. DataRaptor Load


D. DataRaptor Turbo Extract





D.
  DataRaptor Turbo Extract

Explanation:

A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is suitable for this scenario because the developer does not need to transform or load the data

A developer needs tocreateDataRaptor to retrieve the name of an account for a contact. Following best practices, how should a developer configure the extraction steps?


A. Define an extraction step for the Contact object and set the Extract JSON Path to Contact Account.Name


B. Define extraction steps for the Contact and the Account objects, and set the Extract JSON Path to Contact Account.Name


C. Define extraction steps for the Contact and the Account objects, and set the Extract 3SON Path to Account.Name


D. Define an extractionstep for the Account object, and set the Extract JSON Path to AccountContact.Name





A.
  Define an extraction step for the Contact object and set the Extract JSON Path to Contact Account.Name

Explanation:

A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths. However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.


Page 5 out of 24 Pages
Previous