Salesforce Certified Omnistudio Developer — Practice Exam Set 1

Question 1

An OmniScript developer wants to add custom JavaScript logic when a user clicks Next on a specific step. Which OmniScript customization approach is recommended?

Accepted Answer

OmniStudio supports extending OmniScripts with custom Lightning Web Components. A custom LWC can be registered and used as an element within an OmniScript step. The LWC implements the OmniScript LWC API (omniscriptBaseMixin) to access and update the DataJSON, handle navigation events, and execute custom JavaScript logic. This approach extends OmniScript declaratively without modifying generated files.

Question 2

To implement a custom LWC element in an OmniScript, which base mixin must the LWC extend?

Accepted Answer

Custom LWC elements used in OmniScripts must extend `OmniscriptBaseMixin(LightningElement)`, imported from `omnistudio/omniscriptUtils`. This mixin provides the LWC with access to the OmniScript's DataJSON, methods to update data nodes (`omniUpdateDataJson`), and integration with OmniScript navigation events. Without this mixin, the LWC has no connection to the OmniScript's data context.

Question 3

A developer is debugging an OmniScript that is not saving data correctly to Salesforce. Which two tools can help diagnose the issue? (Choose 2)

Accepted Answer

For OmniScript debugging: (1) The OmniScript Preview with JSON view shows the live DataJSON state at every step — developers can see exactly what data is being passed to DataRaptor Loads, helping identify mapping issues; (2) Salesforce Debug Logs capture DataRaptor and Integration Procedure execution details server-side, showing SOQL queries, DML operations, and any errors during the save process. Setup Audit Trail tracks configuration changes, not runtime behavior. Workbench verifies results but not the cause of issues.

Question 4

An OmniScript has a custom LWC element that needs to navigate to the next step programmatically after completing its internal logic. Which method from the OmniscriptBaseMixin is used?

Accepted Answer

The OmniscriptBaseMixin provides `this.omniNextStep()` as the method to programmatically navigate to the next step from within a custom LWC element. This triggers the OmniScript's navigation logic (including any configured validation) as if the user had clicked the Next button. `omniApply()` is used to update the DataJSON, not navigate. Dispatching a CustomEvent directly to the OmniScript navigation system is not a supported pattern.

Question 5

An OmniScript developer needs to validate user input in a custom LWC element and prevent the user from proceeding to the next step until the validation passes. Which two approaches implement this? (Choose 2)

Accepted Answer

To prevent OmniScript navigation from a custom LWC: (1) Implement `omniReturnResults()` in the LWC and return `false` when validation fails — OmniScript calls this method before navigating and cancels the navigation if it returns false; (2) Use `omniSetError()` (or the validity API) to mark the custom element as invalid, which the OmniScript checks during navigation validation. Throwing JavaScript errors creates unhandled exceptions rather than controlled validation feedback.

Question 6

An OmniScript is configured with 'Show Checkbox to Save Progress' enabled. What does this enable?

Accepted Answer

When 'Resume Save' is configured for an OmniScript, users can optionally save their progress at any step and return to the OmniScript later to resume from where they left off. The OmniScript state is saved to a Vlocity/OmniStudio OmniProcess record. This is critical for long multi-step processes where users may not complete them in a single session (e.g., insurance applications, enrollment forms).

Question 7

Which OmniScript element type displays read-only text computed from the DataJSON using a formula or expression?

Accepted Answer

The Display Text element in OmniScript displays static or dynamic read-only text to the user. It can include merge fields referencing DataJSON values using `%JSONPath%` notation to display computed or fetched values. For example, displaying 'Total Price: %orderSummary:totalPrice%' shows the value from the DataJSON path. The Text Block element also supports HTML content. Formula elements compute values but don't directly display them to users.

Question 8

An OmniScript needs to be embedded in an Experience Cloud site for customer self-service. Which two configurations are required? (Choose 2)

Accepted Answer

To embed an OmniScript in Experience Cloud: (1) Add the OmniStudio OmniScript Lightning component to the Experience Cloud page via Experience Builder, configuring the OmniScript Type and SubType to point to the correct OmniScript; (2) Ensure the appropriate security context — for authenticated users, they need OmniStudio user permissions; for guest access, configure the OmniScript and its DataRaptor/Integration Procedure actions to work within guest user access constraints. OmniScripts are not exported as standalone web components.

Question 9

In a DataRaptor Extract, what does the 'Field Level Filter' do compared to 'Object Level Filter'?

Accepted Answer

In DataRaptor Extract: Object Level Filters work like SOQL WHERE clauses — they filter which RECORDS are returned (e.g., WHERE Status = 'Active'). Field Level Filters work like SOQL field-level conditions that filter within relationship traversals or specific field conditions applied after the initial record retrieval. Understanding this distinction is important for designing DataRaptor Extracts that efficiently retrieve the correct data set.

Question 10

A DataRaptor Load is configured to upsert records using an External ID field. The upsert fails because the same External ID value appears in multiple source records. What is the most likely cause?

Accepted Answer

When using External ID fields for upsert operations, the External ID value must be unique in the input data. If multiple source records contain the same External ID value, the system cannot determine which one to upsert and the operation fails. This is a data quality issue in the source JSON — each record should have a distinct External ID. The DataRaptor Load does support upsert using External ID fields (when the field is marked as External ID in Salesforce).

Question 11

A DataRaptor Extract needs to retrieve Case records with their related Contact.Name and Account.Name in a single call. Which two configurations enable this relationship traversal? (Choose 2)

Accepted Answer

DataRaptor Extracts support relationship field traversal. To retrieve related fields from parent objects: (1) In the Input Object configuration, specify the base object (Case) and include related object fields using dot notation (Contact.Name, Account.Name) — DataRaptor generates the appropriate SOQL relationship query; (2) Map these traversed fields to output JSON keys in the Field Mapping. This retrieves all data in one SOQL query without separate DataRaptor calls.

Question 12

A DataRaptor Transform needs to convert a flat JSON input into a nested JSON structure (e.g., wrapping a list of products under a 'lineItems' key in an 'order' object). Which feature enables this structural transformation?

Accepted Answer

DataRaptor Transform uses JSON path expressions in the Output Path column of the Field Mapping to define the target structure of the output JSON. Using dot notation and array notation in the Output Path (e.g., `order:lineItems:0:productName`), the Transform can construct nested JSON objects and arrays from flat input data. This powerful path-based mapping allows arbitrary restructuring of JSON data without any code.

Question 13

In DataRaptor, the 'Bundle' feature is used to:

Accepted Answer

DataRaptor Bundles (also called Bundle Bundles or multi-object DataRaptor Loads) allow configuring a single DataRaptor to perform sequential DML operations on multiple related Salesforce objects. For example, a Bundle DataRaptor Load can Insert a parent Account record, then Insert multiple Contact records using the newly created Account ID as the foreign key, all in a single DataRaptor execution. This simplifies complex parent-child creation scenarios.

Question 14

A DataRaptor Load needs to process an array of line items (from OmniScript DataJSON) and insert each as a separate Salesforce record. Which two configurations achieve this? (Choose 2)

Accepted Answer

To process an array of items with a DataRaptor Load: (1) Set the Input Type to handle arrays by configuring the input path to reference the array in the DataJSON; (2) Enable the 'For Each' iteration setting that tells the DataRaptor Load to process each element in the input array as a separate Salesforce record insert. This allows a single DataRaptor Load call to bulk-process all line items. Calling the DataRaptor from an OmniScript loop makes multiple server round trips, which is less efficient.

Question 15

In an Integration Procedure, what does the 'Conditional' element do?

Accepted Answer

The Conditional element in Integration Procedures provides if/else branching. It evaluates a condition expression against the current data context and routes execution to either the 'true' branch or 'false' branch of child elements. This enables dynamic orchestration where different DataRaptor calls, HTTP actions, or Apex Remote calls are executed based on data values. It is the equivalent of an if/else statement in procedural code.

Question 16

An Integration Procedure needs to call multiple DataRaptor Extracts where each call is independent (no dependencies between them). Which element optimizes this for parallel execution?

Accepted Answer

Integration Procedures execute child elements that are at the same hierarchy level (siblings without parent-child nesting) in parallel. To parallelize independent DataRaptor Extracts, place them as sibling elements at the same level in the Integration Procedure structure (not nested within each other). This allows them to execute concurrently, reducing total execution time significantly compared to sequential execution. Nested elements execute sequentially.

Question 17

An Integration Procedure's HTTP Action needs to authenticate to an external API using OAuth 2.0. Which two configurations support this? (Choose 2)

Accepted Answer

Secure OAuth 2.0 authentication in Integration Procedure HTTP Actions: (1) Named Credentials configured with OAuth 2.0 protocol handle token acquisition and refresh automatically — the HTTP Action references the Named Credential and Salesforce manages authentication; (2) An explicit token acquisition pattern: a first HTTP Action calls the OAuth /token endpoint to get an access token, stores it in the IP data context, and a subsequent HTTP Action passes the token as an Authorization: Bearer header. Hardcoding credentials violates security best practices.

Question 18

An Integration Procedure needs to iterate over an array of records and call a DataRaptor Load for each item. Which element enables this looping?

Accepted Answer

The Loop element in Integration Procedures iterates over an array in the data context. Child elements nested inside the Loop execute once per array item, with the current item's data accessible to child elements. A DataRaptor Load nested inside a Loop will execute for each record in the input array. The current item can be referenced using a configured loop variable in the child element's Input JSON paths.

Question 19

An Integration Procedure's HTTP Action receives a JSON response that needs to be mapped to a specific structure in the data context before it is returned to the OmniScript. Which approach handles this transformation?

Accepted Answer

After an HTTP Action retrieves the API response, a DataRaptor Transform element can be used to reshape the response JSON into the required structure. DataRaptor Transform's path-based field mapping provides flexible restructuring (renaming keys, nesting/flattening, filtering fields) without code. While the HTTP Action has basic output path configuration, complex structural transformations are best handled by a subsequent DataRaptor Transform.

Question 20

A developer wants to unit test an Integration Procedure's HTTP Action without calling the real external API. Which two approaches achieve this? (Choose 2)

Accepted Answer

For testing HTTP Actions without real API calls: (1) Some OmniStudio versions support a Mock Response configuration on the HTTP Action element that returns a predefined JSON response during test runs; (2) Temporarily replacing the HTTP Action with a Set Values element that injects the expected response JSON allows testing the Integration Procedure's logic (DataRaptor Loads, Conditionals, Loops) in isolation from the external API. Both are practical developer testing strategies.

Question 21

A FlexCard developer wants to conditionally show different card content based on the value of a field (e.g., show 'Active' card layout when Status = 'Active' and 'Inactive' layout when Status != 'Active'). Which FlexCard feature implements this?

Accepted Answer

FlexCard States are distinct visual configurations of the same FlexCard that are shown based on conditions evaluated against the card's data. Each State can have completely different layouts, fields, actions, and styling. State transition conditions (e.g., State 'Active' shows when Status = 'Active') are configured declaratively in the FlexCard designer. This enables rich conditional UI without needing multiple separate FlexCards or custom code.

Question 22

A FlexCard developer needs to add a custom LWC element inside a FlexCard. Which requirement must the custom LWC meet?

Accepted Answer

To use a custom LWC inside a FlexCard, the LWC must extend `FlexCardMixin(LightningElement)` (imported from `omnistudio/flexCardUtils`). This mixin provides the LWC with access to the FlexCard's data context and event system. The LWC must also be registered as a FlexCard custom component using the OmniStudio Custom Components feature. Standard LWCs without the mixin cannot receive data from the FlexCard's data source.

Question 23

A FlexCard is loading slowly because its data source (DataRaptor Extract) retrieves too many related records. Which two performance optimizations should a developer apply? (Choose 2)

Accepted Answer

For FlexCard performance: (1) Adding filter conditions to the DataRaptor Extract reduces the number of records returned from Salesforce, directly reducing data transfer and processing time; (2) DataRaptor Turbo Extract is faster than standard Extract for simple read operations as it executes a lightweight SOQL without the full DataRaptor engine overhead. FlexCard caching improves repeat-access performance but doesn't fix slow initial loads. The number of FlexCard States does not affect data retrieval performance.

Question 24

A FlexCard displays a list of orders with an 'Activate' button on each row. Clicking 'Activate' should update the order status and refresh the FlexCard data. Which FlexCard action and behavior achieves this?

Accepted Answer

FlexCard action buttons can be configured with DataRaptor Load as the action type (to perform a DML operation like updating the order status). Enabling 'Refresh Data After Action' on the button causes the FlexCard to re-execute its DataRaptor Extract data source after the action completes, automatically refreshing the displayed data without a full page reload. An Integration Procedure can also be used for more complex updates, with the same Refresh Data setting.

Question 25

A developer needs to pass data from a parent FlexCard to a child (nested) FlexCard. How is data shared between parent and child FlexCards?

Accepted Answer

When a child FlexCard is nested within a parent FlexCard, data is passed from parent to child through the child FlexCard's Input parameters configuration in the parent. The parent's data fields (from its DataRaptor or Integration Procedure source) are mapped to the child FlexCard's defined Input parameters. The child uses these inputs as its data source or as filter parameters for its own DataRaptor calls. Child FlexCards do not automatically inherit parent data.

Plat-Dev-210 — Salesforce Certified OmniStudio Developer