Free Salesforce OmniStudio-Developer Practice Exam with Questions & Answers | Set: 3

From the OmniStudio OmniScript Documentation:

A Repeat Block (like BlkContacts) expects an array of objects.

Each item in the array must contain fields that exactly match the UI elements inside the block.

The parent JSON must include any top-level values used by individual input fields (like AccountName, AccountPhone).

Why the Other Options Are Incorrect:

B. Uses Contacts instead of BlkContacts, and is incomplete/malformed.

C. Repeats keys at the same level instead of using an array structure. This causes the data to overwrite and fail to display properly.

D. Uses incorrect keys like " Name " and " Phone " instead of expected " ContactName " and " ContactPhone " , breaking field binding.

 According to the FlexCard Designer Overview page, one possible cause of a field showing only the label is that “the field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name”. 

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:

A. “The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript.”This is a common configuration issue. If the paths between the OmniScript ' s structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.

B. “The fields that are not updated are read-only in Salesforce.”If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.

Incorrect Options:

C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.

D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.

Salesforce OmniStudio Developer Guide → DataRaptor Load → Troubleshooting

Salesforce Help Documentation: OmniStudio DataRaptor Best Practices

An OmniScript and a Child FlexCard are both valid components that can be embedded in a flyout. An Integration Procedure and a DataRaptor are not components, but actions that can be performed within an OmniScript or a FlexCard.

The correct answer is JSON. Vlocity Build Tool, also called the OmniStudio Build Tool in newer documentation, exports and deploys OmniStudio/Vlocity DataPacks in a source-control-friendly structure. A Data Mapper, FlexCard, OmniScript, or Integration Procedure is represented as DataPack metadata, and the component definition is stored in JSON-based files, while job or manifest configuration can use YAML. DOCX is a document format and has no role in OmniStudio deployment metadata. CSV can hold tabular data, not a full component definition. XML is used in some Salesforce metadata contexts, but DataPacks for OmniStudio deployment are not typically represented as XML component files. Therefore, JSON is the correct deployment metadata format.

================

The correct declarative design is to use a Data Mapper Transform after the HTTP Action. The HTTP Action performs the REST call and returns the response to the Integration Procedure. If that response must be converted from JSON into a required XML structure, the transformation layer should be a Data Mapper Transform, because transforms are built to map input paths to different output structures and formats without writing Apex. XMLStreamReader is for reading XML, not building the target XML payload from JSON. XMLStreamWriter could be used in custom Apex, but the OmniStudio-native answer avoids unnecessary code. A Data Mapper Extract reads Salesforce data, so it is not the right tool for restructuring an HTTP response.

================

The requirement is only to show or hide a section based on a value already present in the OmniScript data JSON. That is exactly what Conditional View is designed for. It evaluates client-side conditions and controls whether a step, block, or element is displayed, editable, or required. Using an Integration Procedure would add unnecessary server-side processing because the required VIP value is already available in the OmniScript. A Data Mapper Transform is also unnecessary because there is no structural transformation requirement. Creating a new version may be part of the deployment process, but it is not the functional configuration that controls visibility. The best implementation is to place the special offers section in the script and configure Conditional View logic against the VIP member value.

================

According to the Calculation Matrix Overview page, a Calculation Matrix is “a lookup table that takes an input and returns an output”. In this case, the input is the ProductCode and the output is the Price. The exhibit shows a Calculation Matrix with four rows, each with a different ProductCode and Price. The input given is ProductCode: HRA3320, which matches the second row of the matrix. Therefore, the output is Price: 13.99, which is the value in the same row. 

For off-platform use, OmniStudio uses OmniOut so LWC OmniScripts and FlexCards can run on third-party websites. Salesforce documentation explains that an activated OmniScript can be downloaded as an Off-Platform LWC and then added to the OmniOut project for integration into the external application. This makes option B correct because the external site embeds the OmniScript as a Lightning Web Component artifact, not as a Visualforce page. Visualforce is Salesforce-hosted legacy UI technology and is not the primary external embedding model. A REST API could call backend logic, but it would not render the OmniScript user interface. An Integration Procedure call only executes server-side logic; it does not embed the guided OmniScript experience.

================

 A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(‘Hello’, ‘World’)}} or {{DATEDIFF(‘2021-01-01’, ‘2021-01-31’)}}.