# Free Salesforce Omnistudio Consultant Practice Questions

*Last updated September 2026 · https://www.certifyforce.com/salesforce-omnistudio-consultant-practice-exam/free-questions*

18 free Omnistudio Consultant practice questions from the Certifyforce bank of 300 reviewed questions, spread across the 6 official exam sections in proportion to their weight. Each has the correct answer, an explanation, and the official documentation it was verified against.

## Omnistudio Fundamentals (16%)

### Question 1

Cloud Kicks' Account record page has hundreds of fields, and sales reps say they need only a few key metrics and recent activities. The org runs Omnistudio on the Standard Runtime. What should the consultant recommend?

- A. Build an Omniscript that walks reps through the Account fields one step at a time so they can skip the ones they don't need to see.
- B. Create a Flexcard that highlights the critical metrics and recent activities, and place it on the Account page with or instead of the layout.
- C. Create a Data Mapper Extract that hides the unused fields on the page layout each time a rep opens an Account record.
- D. Create an Integration Procedure that clears the values of unused fields so that the page shows only the populated data.

**Correct answer:** B. Create a Flexcard that highlights the critical metrics and recent activities, and place it on the Account page with or instead of the layout.

**Explanation:** Trailhead lists simplifying the user interface as a Flexcard scenario: create a simple Flexcard that highlights only the most critical information and place it on the Account page, replacing or supplementing the standard layout. An Omniscript is a guided process, not a way to declutter a record view. A Data Mapper Extract reads data and doesn't change page layouts. Clearing field values with an Integration Procedure destroys data instead of improving the view.

**Sources:** [Get to Know Omnistudio Flexcards (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/omnistudio-flexcard-fundamentals/get-to-know-omnistudio-flexcards), [Omnistudio Flexcards](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_flexcards_24388.htm&language=en_US&type=5)

### Question 2

Cloud Kicks plans to use the Omnistudio Migration Assistant to move its Vlocity Industries managed package org from the Managed Package Runtime to the Standard Runtime. The consultant reviews the org before committing to a timeline. Which two findings mean the tool can't migrate the org as is? Choose 2 answers.

- A. The sales team relies on the out-of-the-box Industries CPQ application that came with the industry package.
- B. Customers use Save and Resume in several Omniscripts, so saved sessions exist that need to keep working.
- C. An Omni Interaction Config record sets EnableLegacyOmniScriptDesignerForLWC to true in the org today.
- D. Several Experience Cloud site pages and Lightning record pages embed Omniscripts and Flexcards that will move.
- E. Custom labels and Omni Global Auto Numbers are referenced by many of the org's existing Omnistudio components.

**Correct answers:** A. The sales team relies on the out-of-the-box Industries CPQ application that came with the industry package.; C. An Omni Interaction Config record sets EnableLegacyOmniScriptDesignerForLWC to true in the org today.

**Explanation:** The Help migration page lists limitations of the Omnistudio Migration Assistant: it doesn't support migrating the out-of-the-box Industries CPQ application, and it doesn't support migration when the Omni Interaction Config settings EnableLegacyOmniScriptDesignerForLWC=true or ShowLegacyOmniStudioUi=true are present. Omniscript saved sessions are migrated automatically by the tool. Updating Lightning pages and community pages is also automated. Migrating custom labels and Omni Global Auto Numbers is automated as well, so none of those three findings blocks the tool.

**Sources:** [Migrate Omnistudio Components from Vlocity Industries Managed Packages and Custom Data Model to Omnistudio Standard Runtime](https://help.salesforce.com/s/articleView?id=sf.os_migrate_omnistudio_custom_objects_to_standard_objects.htm&language=en_US)

### Question 3

AW Computing is designing an energy company's agent console on the Omnistudio Standard Runtime. A Billing Details Flexcard must show charges and due dates held in an external billing system, while the customer's address comes from the Salesforce Account. Which approach should the solution architect recommend for the billing data?

- A. A Data Mapper Extract that calls the billing system's REST API directly, because Extracts are the Omnistudio tool for external web services.
- B. A Data Mapper Load that copies all billing records into Salesforce every time an agent opens the Flexcard, so that the card can query them.
- C. An Omniscript embedded in the Flexcard that asks the agent to type in the charges and due date as the customer reads them from a bill.
- D. An Integration Procedure connected to the Flexcard that uses an HTTP Action to call the billing system and return the data.

**Correct answer:** D. An Integration Procedure connected to the Flexcard that uses an HTTP Action to call the billing system and return the data.

**Explanation:** Trailhead's contact center example connects an Integration Procedure to the Billing Details Flexcard; it uses the HTTP Action to fetch data from the billing system and sends it to the card, while Data Mapper Extracts read Salesforce data such as the Account. Data Mapper Extracts read Salesforce data and don't make REST calls; Integration Procedures do. Copying every billing record on each card load with a Data Mapper Load is wasteful and writes data rather than displaying it. Asking agents to retype figures defeats the purpose of integrating the billing system.

**Sources:** [Explore Omnistudio Use Cases (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/omnistudio-basics/explore-omnistudio-use-cases), [Omnistudio Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_integration_procedures_48334.htm&language=en_US&type=5)

## Flexcards (18%)

### Question 4

On a Get Cloudy Consulting account Flexcard (Standard Runtime), a Flyout action opens a child Flexcard in a popover. The child has an Update Contact button, and the popover must close by itself as soon as the update finishes. What should the consultant recommend?

- A. Add a Navigate action after the update on the child Flexcard that returns the user to the account record page
- B. Add a Reload card action on the parent Flexcard that runs whenever the child's contact record is updated
- C. Add a pubsub Event action on the child Flexcard that uses the flyout's channel name and the event name close
- D. Set a Refresh Interval on the parent's data source so the popover closes the next time the parent card reloads

**Correct answer:** C. Add a pubsub Event action on the child Flexcard that uses the flyout's channel name and the event name close

**Explanation:** Help's way to close a modal or popover flyout after a task completes is a pubsub event in the flyout's Flexcard that uses the channel name set on the parent's flyout action and the event name close. Help recommends against using a Navigate action directly on a flyout or modal, and it would leave the account page. Reloading the parent refreshes its data, but it doesn't close the flyout. A Refresh Interval re-checks data on a schedule and has no link to closing a flyout.

**Sources:** [Set Up Flyouts on a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_launch_a_flyout_from_an_action_on_a_flexcard_27319.htm&language=en_US&type=5)

### Question 5

A Get Cloudy Consulting client has a contact Flexcard (Standard Runtime) with seven actions such as Log Call, Send Email and Update Address, and the buttons crowd the card. The business wants the actions kept on the card but presented compactly. Which element should the consultant recommend?

- A. A Data Table element that lists the actions as rows so users can sort them by how often they're used
- B. A State for each action so that only one of the buttons is visible on the card at any given time
- C. A Block element for each pair of actions so that users can collapse the groups they don't need
- D. A Menu element that groups the actions into a dropdown list attached to a single menu button

**Correct answer:** D. A Menu element that groups the actions into a dropdown list attached to a single menu button

**Explanation:** The Menu element groups actions into a dropdown list, which keeps all the functions available without crowding the layout. Data tables show data records rather than actions, so rows of actions wouldn't run them in a natural way. States change the layout based on conditions, not on a user's choice of action, so actions would be hidden from users who need them. Collapsible blocks group related information, but several blocks of buttons add clutter instead of reducing it.

**Sources:** [Group Actions in a Menu on a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_add_a_menu_to_a_flexcard_30859.htm&language=en_US&type=5), [Trailhead: Get Started with Flexcard Designer](https://trailhead.salesforce.com/content/learn/modules/omnistudio-flexcard-fundamentals/get-started-with-flexcard-designer)

### Question 6

Northern Trail Outfitters' Standard Runtime customer 360 Flexcard embeds 11 child Flexcards and a Data Table that is expected to show up to 1,200 rows. Omnistudio Design Assistant shows warnings for the card. Which recommendation aligns with the Design Assistant recommended limits?

- A. Keep the Data Table as designed and reduce only the child Flexcards, because the recommended limit for child Flexcards is 7 and tables have none
- B. Consolidate the children to 7 or fewer and filter or page the table data so the Data Table stays within 750 rows
- C. Keep the 11 child Flexcards, because the recommended limit for children is 20, and cut the Data Table to below 750 rows
- D. Ignore the warnings, because Design Assistant messages are informational and recommended limits only matter for Omniscripts

**Correct answer:** B. Consolidate the children to 7 or fewer and filter or page the table data so the Data Table stays within 750 rows

**Explanation:** The Design Assistant recommended limits for Flexcards are 7 child Flexcards within a parent and 750 rows in a Data Table, so this card exceeds both and both need redesigning. The Data Table does have a recommended limit, so reducing only the children leaves the 1,200-row table over it. Twenty is a recommended limit for items such as event listeners, Data Mappers and Integration Procedures in a Flexcard, not for child Flexcards. Recommended limits are published for Flexcards as well as Omniscripts, and the warnings point to design choices that can cause latency and runtime issues, so ignoring them isn't a sound recommendation.

**Sources:** [Recommended Limits (Omnistudio Design Assistant)](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_design_assistant_recommended_limits.htm&language=en_US&type=5), [Omnistudio Design Assistant](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_design_assistant.htm&language=en_US&type=5)

## Omniscripts (17%)

### Question 7

AW Computing's Standard Runtime warranty Omniscript has a Text element for the serial number, which always has two letters, a dash and six digits. The business wants a specific message, "Serial numbers look like AB-123456," whenever the format is wrong. A builder set a Mask on the element and typed that message as custom error text, but users see a generic error. What should the Omnistudio consultant recommend?

- A. Keep the Mask and move the message into the element's Help Text so that it appears next to the field when the format is wrong
- B. Keep the Mask and add a Set Errors element after the Step that maps the same message to the serial number element
- C. Remove the Mask and use a simple regular expression in Pattern with the message in Pattern Error Text, since masks show the default error
- D. Keep the Mask and switch the element to a Telephone element, because only Telephone elements display custom error text when a Mask is set

**Correct answer:** C. Remove the Mask and use a simple regular expression in Pattern with the message in Pattern Error Text, since masks show the default error

**Explanation:** The Common Omniscript Element Properties page states that when the Mask property is set on text fields, Salesforce shows the default error message instead of custom error messages for those fields. Pattern accepts a regular expression with custom Pattern Error Text, and simple patterns such as this one are supported, so it delivers the requested message. Help Text appears on hover over a help icon and isn't a validation message. A Set Errors element runs after the step and is meant for checks that depend on later steps, not format checks on the current step. Switching to a Telephone element doesn't fit a serial number and isn't documented as changing mask error behavior.

**Sources:** [Common Omniscript Element Properties](https://help.salesforce.com/s/articleView?id=xcloud.os_common_omniscript_element_properties_definitions__10687.htm&language=en_US&type=5)

### Question 8

Bloomington Caregivers needs a Standard Runtime intake Omniscript with a 12-question wellness screening. Every question offers the same three answers: Never, Sometimes and Often. Staff want the questions on one Step in a compact questionnaire format. Which component should the Omnistudio consultant recommend?

- A. Twelve Radio elements, each with its own Never, Sometimes and Often options
- B. A Multi-select element that lists all twelve questions as selectable options
- C. A Radio Group with the three options and the twelve questions listed in it
- D. An Edit Block in table mode with a Select element for each screening question

**Correct answer:** C. A Radio Group with the three options and the twelve questions listed in it

**Explanation:** A Radio Group shows many multiple-choice questions in a questionnaire format with the same options for each question, so the three answers are defined once and the questions are listed under Radio Group Questions. Twelve Radio elements work but repeat the same options twelve times and lose the questionnaire layout. A Multi-select captures several choices from one list, not one answer per question. An Edit Block is for managing records, and Help notes that table mode should have no more than six elements.

**Sources:** [Create an Omniscript Questionnaire with a Radio Group](https://help.salesforce.com/s/articleView?id=xcloud.os_radio_group_15340.htm&language=en_US&type=5), [Trailhead: Explore Omniscript Group and Input Elements](https://trailhead.salesforce.com/content/learn/modules/omnistudio-omniscript-fundamentals/explore-omniscript-group-and-input-elements)

### Question 9

Cumulus Financial is setting Omniscript standards for a team of eight builders on the Standard Runtime. Which two practices should the Omnistudio consultant include in the standards? Choose 2 answers.

- A. Document each element's purpose in its Internal Notes property so that other builders understand why it exists
- B. Avoid renaming elements after deploying to production, and when unavoidable, update every place the element is referenced
- C. Give elements on different Steps the same name when they hold the same kind of value, such as Phone, to keep the data JSON uniform
- D. Reuse the same response node name across Data Mapper actions so that each new response overwrites the previous one cleanly
- E. Write design notes in each element's Help Text so that testers can read the notes by hovering over the icon at runtime

**Correct answers:** A. Document each element's purpose in its Internal Notes property so that other builders understand why it exists; B. Avoid renaming elements after deploying to production, and when unavoidable, update every place the element is referenced

**Explanation:** Omniscript best practices recommend documenting an element's purpose in its Internal Notes property, which appears only in the designer, and avoiding element name changes after production deployment, applying the change wherever the element is referenced when it can't be avoided. The same page calls for unique names for Omniscript elements and Data Mapper response nodes, so shared element names and reused response nodes break that rule. Help Text is shown to end users at runtime, so it's the wrong place for design notes.

**Sources:** [Omniscript Best Practices](https://help.salesforce.com/s/articleView?id=sf.os_omniscript_best_practices_8368.htm&language=en_US&type=5), [Common Omniscript Element Properties](https://help.salesforce.com/s/articleView?id=xcloud.os_common_omniscript_element_properties_definitions__10687.htm&language=en_US&type=5)

## Integration Procedures (17%)

### Question 10

Cumulus Financial is planning an Integration Procedure on the Omnistudio Standard Runtime that calls a credit bureau's REST API. The bureau issues OAuth 2.0 access tokens to a client ID and secret, and the security team doesn't want any secret stored in Omnistudio components. What should the consultant recommend for authentication?

- A. Select a named credential in the HTTP Action whose external credential uses the OAuth 2.0 client credentials flow, so Salesforce obtains the token.
- B. Store the client secret in REST Options: Header on the HTTP Action and mark the header as private so that only administrators can open it.
- C. Save the client ID and secret in a custom setting and pass them to the HTTP Action as merge fields in the Request Body on every call.
- D. Add the bureau's token URL as a Remote Site Setting, because the remote site record stores the OAuth credentials for the callout.

**Correct answer:** A. Select a named credential in the HTTP Action whose external credential uses the OAuth 2.0 client credentials flow, so Salesforce obtains the token.

**Explanation:** Help for the Integration Procedure HTTP Action recommends named credentials for securely managing authentication data, and an external credential defines how Salesforce authenticates, including the OAuth 2.0 Client Credentials with Client Secret flow, so Salesforce obtains the token. Typing the secret into a header value is the hardcoding that the HTTP Action page warns against. Saving the secret in a custom setting and merging it into the Request Body still places it in the request the procedure builds instead of letting the credential supply it. A Remote Site Setting only permits calls to a host and stores no OAuth credentials.

**Sources:** [HTTP Action for Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_http_action_for_integration_procedures_53002.htm&language=en_US&type=5), [Authentication Protocols for Named Credentials](https://help.salesforce.com/s/articleView?id=xcloud.nc_auth_protocols.htm&language=en_US&type=5)

### Question 11

Ursa Major Solar's monitoring vendor documents a PATCH request for updating only the changed fields of an existing panel record. A business analyst asks whether an Integration Procedure on the Omnistudio Standard Runtime can make this call declaratively. How should the consultant respond?

- A. No: the HTTP Action supports only GET and POST, so the team must write an Apex Remote Action for every PATCH request it makes.
- B. No: the HTTP Action sends PATCH only through an Omniscript HTTP Action, so the call must move into the guided process instead.
- C. Yes: the HTTP Action's HTTP Method can be set to PATCH, along with GET, POST, PUT and DELETE, for the vendor's own endpoint.
- D. Yes: but the method must be set to PUT, which the HTTP Action converts to PATCH whenever the request body has fewer fields.

**Correct answer:** C. Yes: the HTTP Action's HTTP Method can be set to PATCH, along with GET, POST, PUT and DELETE, for the vendor's own endpoint.

**Explanation:** Salesforce Help lists GET, POST, PUT, PATCH and DELETE as the HTTP Method values of the HTTP Action for Integration Procedures, so a PATCH call needs no code. Saying the action supports only GET and POST understates it, and an Apex Remote Action is unnecessary. Moving the call into an Omniscript isn't required, since the procedure's own action supports PATCH. The HTTP Action doesn't convert PUT into PATCH; PUT and PATCH are separate methods.

**Sources:** [HTTP Action for Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_http_action_for_integration_procedures_53002.htm&language=en_US&type=5)

### Question 12

Northern Trail Outfitters exposes a Standard Runtime Integration Procedure through the REST API to a partner's order system. When no order matches the request, the partner wants the HTTP status code 404 in the response header instead of 200 with an empty body. What should the consultant recommend?

- A. Add a Set Values action that writes a StatusCode node with the value 404 into the data JSON before the procedure ends.
- B. Set a Failure Conditional Formula on the order lookup so the platform returns 404 whenever no record matches the request.
- C. Add an Additional Output key named StatusCode with the value 404 on the final Response Action when no order is found.
- D. Add a Response Headers entry named StatusCode with the value 404 on a Response Action that runs when no order is found.

**Correct answer:** D. Add a Response Headers entry named StatusCode with the value 404 on a Response Action that runs when no order is found.

**Explanation:** The Response Action's Response Headers property adds data to the response header, and a key named StatusCode with a valid HTTP value overrides the returned status code; an Execution Conditional Formula makes that Response Action end the procedure only when no order is found. Additional Output and a Set Values node only put a StatusCode value in the data JSON body, so the header still reports the normal status. A Failure Conditional Formula marks the step as failed and adds the Failure Response pairs to the data JSON; it doesn't set the HTTP status of the reply.

**Sources:** [Response Action for Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_response_action_for_integration_procedures_54655.htm&language=en_US&type=5), [Integration Procedure Actions](https://help.salesforce.com/s/articleView?language=en_US&id=xcloud.os_integration_procedure_actions_50165.htm&type=5)

## Data Mappers (17%)

### Question 13

Ursa Major Solar registers solar inverters through a Standard Runtime Omniscript whose Data Mapper Post action calls a Data Mapper Load on a custom Inverter Registration object. A registration is unique only by the combination of Serial_Number__c and Model__c, because different models can reuse serial numbers. Re-registering an inverter must update its record. Which two statements should the Omnistudio consultant include in the design? Choose 2 answers.

- A. Enable Upsert Key on the Serial_Number__c mapping only, because the Load treats the first upsert key it finds as the record's unique identifier
- B. Enable Upsert Key on both the Serial_Number__c and Model__c mappings, so the two fields act together as a multi-field upsert key
- C. Map the record Id as an extra upsert key alongside the two fields, so the Load can also match registrations created in earlier runs
- D. Use an Integration Procedure with two Loads, one keyed on each field, because a single Load accepts only one upsert key per object
- E. A registration is updated only when it matches both the serial number and the model; when no record matches both, a new one is created

**Correct answers:** B. Enable Upsert Key on both the Serial_Number__c and Model__c mappings, so the two fields act together as a multi-field upsert key; E. A registration is updated only when it matches both the serial number and the model; when no record matches both, a new one is created

**Explanation:** Help's Load configuration page says that when Upsert Key is enabled on several field mappings, the result is a multi-field upsert key that the Load uses to decide whether to create or update. The Omniscript Data Mapper Action Elements page adds that with multiple upsert keys the record must match all keys for a match, so a record with the same serial number but a different model is inserted as new. Keying on the serial number alone would treat different models that share a serial as one record. Help says not to use an ID as the upsert key, and because multi-field keys are supported, two separate Loads aren't needed.

**Sources:** [Configure an Omnistudio Data Mapper Load](https://help.salesforce.com/s/articleView?id=sf.os_object_field_mapping_47137.htm&language=en_US&type=5), [Omniscript Data Mapper Action Elements](https://help.salesforce.com/s/articleView?id=xcloud.os_omniscript_data_mapper_action_elements.htm&language=en_US&type=5)

### Question 14

An Integration Procedure on the Omnistudio Standard Runtime at Get Cloudy Consulting receives a quote response from a partner's REST API. Before an Omniscript shows the quote, the payload's nodes must be renamed and regrouped, and a total premium must be added with a SUM formula. The architect wants this step to run no SOQL queries. Which Data Mapper type fits this step?

- A. A Data Mapper Extract, because only Extracts can add formula results to an output JSON structure that an Omniscript reads
- B. A Data Mapper Turbo Extract, because it's the fastest Data Mapper at run time and supports renamed output paths for each field
- C. A Data Mapper Load with the partner payload as its JSON input, because Loads can apply formulas before data is returned
- D. A Data Mapper Transform, because it restructures and renames in-memory data and applies formulas without querying Salesforce

**Correct answer:** D. A Data Mapper Transform, because it restructures and renames in-memory data and applies formulas without querying Salesforce

**Explanation:** A Transform converts input data into a new structure, renames fields and applies formulas and functions; because it works with data in memory, it doesn't use a SOQL query or read Salesforce objects. An Extract also supports formulas, but it reads Salesforce data with queries, which the architect wants to avoid, and Extracts aren't the only formula-capable type. A Turbo Extract reads a Salesforce object and can't use formulas. A Load writes its output to Salesforce objects, so it would create or update records rather than return a reshaped quote.

**Sources:** [Omnistudio Data Mappers](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_dataraptors_45587.htm&language=en_US), [Explore Data Mapper Types (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/omnistudio-data-mapper-fundamentals/explore-data-mapper-types)

### Question 15

A Cumulus Financial Data Mapper Transform on the Omnistudio Standard Runtime uses the formula `FILTER(LIST(Accounts), 'Status == "Active"')` to pass only active accounts to a Flexcard. Some records arrive from a legacy system with the status ACTIVE in capital letters. What should the Omnistudio consultant tell the business analyst?

- A. Those records are included, because the FILTER function performs case-insensitive matching of strings
- B. Those records are dropped, because FILTER compares strings only with case-sensitive matching
- C. Those records cause an error, because FILTER needs a function that converts mixed-case values first
- D. Those records are included only if the output data type of the Status mapping is set to String

**Correct answer:** A. Those records are included, because the FILTER function performs case-insensitive matching of strings

**Explanation:** Help states that FILTER returns the JSON objects in a list that match an equivalence condition and that it performs case-insensitive matching of strings, so Active and ACTIVE both match. Saying FILTER compares with case-sensitive matching contradicts that statement. FILTER needs no conversion function for mixed-case values, and the documented matching causes no error. The output data type of a mapping affects how a value is written to the output, not how FILTER compares values inside the formula.

**Sources:** [Omnistudio List and Array Functions](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_list_functions.htm&language=en_US&type=5)

## Best Fit Solutions (15%)

### Question 16

Northern Trail Outfitters runs a Vlocity Industries managed package (Communications, Media, and Energy) on an older release and plans to move to the Omnistudio Standard Runtime with the Omnistudio Migration Assistant. The draft plan starts the migration on the package version the org has today and uninstalls the managed package after go-live to keep the org clean. Which two changes should the solution architect recommend? Choose 2 answers.

- A. Upgrade the Vlocity Industries managed package to Winter '26 or later before the migration starts
- B. Keep the managed package installed after go-live, as org workflows may still rely on its schema
- C. Run the Migration Assistant in Migrate mode first and Assess mode after, to confirm what moved
- D. Skip the migration, because CME orgs already use the standard data model and standard runtime
- E. Turn the Managed Package Runtime setting back on after go-live, so custom components still work

**Correct answers:** A. Upgrade the Vlocity Industries managed package to Winter '26 or later before the migration starts; B. Keep the managed package installed after go-live, as org workflows may still rely on its schema

**Explanation:** The Salesforce Developers blog on migrating to the standard runtime says to upgrade to the Vlocity Industries managed package version Winter '26 or later before starting the migration, whatever the transition path, and notes that package uninstallation isn't recommended because existing org workflows and custom components may still rely on package schema or metadata. Its process runs Assess mode first, fixes the flagged issues and reruns Assess until the report is green, and only then runs Migrate mode. Vlocity Industries packages such as CME use the custom data model pointing to the managed package runtime, so migration is required. Help's Disable the Managed Package Runtime page says that after you disable the setting, you shouldn't re-enable it.

**Sources:** [Migrate From Managed Package Runtime to the Omnistudio Standard Runtime](https://developer.salesforce.com/blogs/2026/08/migrate-from-managed-package-runtime-to-the-omnistudio-standard-runtime), [Disable the Managed Package Runtime and Deploy Custom Lightning Web Components](https://help.salesforce.com/s/articleView?id=sf.os_enable_standard_omnistudio_runtime.htm&language=en_US&type=5)

### Question 17

AW Computing is preparing a quarterly release of Standard Runtime Omniscripts, Integration Procedures and Data Mappers that also includes a data migration script. Before production, the release manager wants one final, production-like rehearsal of the deployment procedure, the solution's performance and the migration script. Which environment should the Omnistudio consultant recommend for this rehearsal?

- A. A Developer sandbox, because it refreshes often and so keeps its configuration closest to the current production setup
- B. A partial copy integration sandbox, because a sample of production data is enough for performance and migration checks
- C. A full copy staging sandbox, because it mirrors production configuration and data for the final check before release
- D. A training sandbox, because it stays stable for long periods and holds anonymized data that is safe for a rehearsal

**Correct answer:** C. A full copy staging sandbox, because it mirrors production configuration and data for the final check before release

**Explanation:** Salesforce Well-Architected describes staging sandboxes (full copy) as mirroring production configuration and data, which gives final validation before production and production-like testing of deployment procedures, performance characteristics and data migration scripts. A Developer sandbox is a lightweight environment for individual feature development, not a production-fidelity rehearsal. A partial copy integration sandbox holds enough production data to test realistic workflows, and integration tests run there before promotion to staging, so it is the step before the final rehearsal. A training sandbox is meant for user training and demos with synthesized or anonymized data, not release validation.

**Sources:** [Operational Excellence (Salesforce Well-Architected)](https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence.html)

### Question 18

Get Cloudy Consulting is choosing Data Mapper actions for three parts of a Standard Runtime claims Omniscript: prefilling Step 1 with fields from the claimant's Contact only, with no formulas; reshaping the answers gathered on earlier Steps into a partner's structure without reading Salesforce; and saving the claim with its claim lines. Which two pairings should the consultant recommend? Choose 2 answers.

- A. Prefill: a Data Mapper Turbo Action, which is simpler to set up and can run faster for one object
- B. Reshape: a Data Mapper Extract Action, which reads the earlier answers from the Omniscript itself
- C. Reshape: a Data Mapper Transform Action, which sends the data JSON and returns the mapping
- D. Save: a Data Mapper Turbo Action, which writes the claim and its lines in one faster operation
- E. Prefill: a Data Mapper Transform Action, which queries the Contact and renames its fields

**Correct answers:** A. Prefill: a Data Mapper Turbo Action, which is simpler to set up and can run faster for one object; C. Reshape: a Data Mapper Transform Action, which sends the data JSON and returns the mapping

**Explanation:** Omniscript Data Mapper Action Elements says a Data Mapper Turbo Action gets data from a single Salesforce object, doesn't support formulas or complex field mappings, and is simpler to set up and can run more quickly than an Extract, which suits the prefill. A Data Mapper Transform Action sends the full Omniscript data JSON to the Data Mapper and returns the mapping without reading or writing Salesforce data, which suits the reshaping. Extract actions retrieve data from Salesforce objects, not from the Omniscript's answers. Saving needs a Data Mapper Post Action that calls a Load, because a Turbo action only reads, and a Transform doesn't query objects.

**Sources:** [Omniscript Data Mapper Action Elements](https://help.salesforce.com/s/articleView?id=xcloud.os_omniscript_data_mapper_action_elements.htm&language=en_US&type=5)

## Related pages

- [Salesforce Omnistudio Consultant practice exam](https://www.certifyforce.com/salesforce-omnistudio-consultant-practice-exam)
- [Practice exam packs](https://www.certifyforce.com/practice-exams)
- [Official Omnistudio Consultant exam guide](https://help.salesforce.com/s/articleView?id=005298970&language=en_US&type=1)