Salesforce OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Exam Practice Test

Multi-language OmniScripts use Salesforce translation infrastructure and custom labels. In normal Salesforce runtime usage, the language shown to the user is driven by the user’s Salesforce language setting, not simply by the browser language or by a random session variable. The default OmniScript language is only the fallback/base design language; it does not decide which translated bundle is displayed for each user when translations exist. Option A is wrong because a global Session Variable is not the standard translation selector. Option B is also wrong in this context because OmniScript translations are tied to Salesforce language and Translation Workbench/custom-label behavior. Therefore, the user’s Salesforce language setting is the correct controlling source for displayed translations.

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

OmniStudio best practices dictate that versioning is used when enhancements are required within the same logical flow, while cloning is preferred when the new flow is functionally different and used separately.

B. The new Integration Procedure will be used independently – Correct. Cloning creates an entirely new IP definition, ideal for building a similar but standalone process, rather than altering behavior for an existing process.

Incorrect Options:

A. Using a Cache Block is unrelated to cloning vs. versioning.

C. Replacing stub data does not require cloning; could be done in a version.

D. Chainability does not influence whether you should clone or version.

Salesforce OmniStudio Guide → Cloning vs. Versioning Integration Procedures

The correct tool is the Test Data and Parameters panel in the FlexCard Designer. The requirement is specifically to test the FlexCard directly in its designer with different JSON inputs before deployment. The OmniScript Test Console is for OmniScript logic, not FlexCard data rendering. IDX Workbench is a migration/deployment tool, not the FlexCard’s built-in data-testing panel. A Data Mapper Turbo Extract preview only tests the Data Mapper query output; it does not validate how the FlexCard processes different JSON structures and renders states, fields, or conditional elements. Salesforce documentation for FlexCard testing describes adding test parameters in the FlexCard Designer and previewing/debugging the card using those values, which directly supports option C.

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

The Upsert Key checkbox indicates that the field is used as a key for upserting records. The Is Required for Upsert checkbox indicates that the field is mandatory for upserting records. The developer needs to check both checkboxes on the Account Id field to update the Account status only if the Account record already exists. Otherwise, a new account will be created.

The Lookup element is used to retrieve data from a single field in a Salesforce record. The Lookup element allows the developer to specify the object, field, and filter criteria for the data retrieval. The Select element is used to display a list of options for the user to choose from. The HTTP Action element is used to send or receive data from an external system using HTTP methods. The DataRaptor Post Action element is used to create or update Salesforce records using a DataRaptor Transform.

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

Salesforce OmniStudio Developer Guide → OmniScript Formula Element

Navigation button labels such as Next are controlled through OmniScript setup-level label mapping/custom label configuration, not by editing each Step element or creating Navigate Actions. The Next button is part of the OmniScript framework navigation, so changing it globally for the script belongs in the setup configuration where element names and labels can be mapped. A Navigate Action is used to navigate to another page or component; it is not the framework Next button. LWC Component Override is for replacing component rendering behavior with a custom LWC, which is excessive and incorrect for a simple label change. Salesforce documentation describes OmniScript setup configuration and custom label references for OmniScript properties, supporting the setup-label approach.

Two separate Group elements with mutually exclusive conditions provide the cleanest declarative control. One Group should execute only when updateBillingAddress is true and updateShippingAddress is false. The other Group should execute only when updateShippingAddress is true and updateBillingAddress is false. This enforces that only one address update path runs. A single OR condition would allow either or both flags to be true, so it cannot prevent simultaneous updates. A Try-Catch Block reacts after an error occurs; it is not the right way to express business-rule branching. An HTTP Action would add unnecessary external dependency. Integration Procedure blocks and groups are designed to run related steps conditionally, so mutually exclusive Group conditions are the correct structure.

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

A FlexCard is the correct user-interface component for displaying summarized, contextual, responsive information from one or more data sources. The scenario is not asking for a guided form or step-by-step process; it asks for a single-page health summary with list-like lab results and interactive display behavior. An Integration Procedure can absolutely be used behind the FlexCard to aggregate Salesforce demographic data and EMR lab results, but the component that displays and manages the responsive interaction is the FlexCard. A Data Mapper Extract only retrieves Salesforce data and does not handle external EMR data or UI interaction. OmniScript is better for guided data collection and process automation, not a compact summary card. Therefore, the front-end OmniStudio component should be a FlexCard.

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

The best practice for configuring the Input JSON for a DataRaptor Load is to copy the Input JSON from the OmniScript {Data} modal. This ensures that the Input JSON matches the data structure and format of the OmniScript data. The DataRaptor Action Debug node may not have the same data as the OmniScript data, and building the Input JSON node by node in an editor or in the DataRaptor Designer may introduce errors or inconsistencies.

The Node field for the parent FlexCard should be set to {Records}, which is an array of all the records retrieved by the parent FlexCard data source. This will allow the child FlexCard to access the records and display them in a DataTable.

The correct syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.

OmniScript is the correct tool because the scenario describes an end-to-end guided business process: collecting property details, applying conditional steps, calling calculation logic, and submitting the final application. Integration Procedures are excellent for server-side orchestration, integrations, and calculations behind the scenes, but they do not provide the user-facing guided interaction by themselves. Data Mappers retrieve, transform, or save data; they are not the process UI. FlexCards display contextual information and actions but are not designed as the primary multi-step application workflow. Salesforce describes OmniScripts as guided, interactive processes that help users complete business tasks and collect data across channels. Therefore, the core component controlling this process is an OmniScript.

A DataRaptor Load Action can be used to retrieve data from a Salesforce object by specifying the object name, fields, and filter criteria. A Lookup Input Element can be used to retrieve data from a Salesforce object by allowing the user to search for a record using a lookup field

 The Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact’s postal code in the child FlexCard.

Versioning a FlexCard allows the developer to make changes to the FlexCard without affecting the existing instances of the FlexCard. The developer can choose to update all instances of the FlexCard with the new version or keep them as they are. This is useful when the changes are minor and do not affect the functionality or layout of the FlexCard. Cloning a FlexCard creates a copy of the FlexCard with a new name and ID. The developer can make changes to the cloned FlexCard without affecting the original FlexCard. This is useful when the changes are major and require a different configuration or design of the FlexCard1. In this case, since all instances of the FlexCard must be updated with the changes, versioning is the best course of action.

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.

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

 Option D is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have the same key/value pairs as Input Data, and the value should be set to {{InputData.key}} for each key. This will pass the value of Input Data for each key to Additional input.

Runtime OmniScript access alone is not always enough when the OmniScript executes Data Mappers, Integration Procedures, or Remote Actions that rely on Apex-backed services. Salesforce has OmniStudio security checks for Apex class access, and its documentation specifically describes configuring Apex class permission checkers so users require explicit access to the Apex class that administers a Remote Action. Save Options do not control Lightning component authorization. Multi-language settings affect labels and translations, not runtime component permissions. FlexCard permissions are not the most likely cause because the error occurs while launching an OmniScript and the scenario already confirms OmniScript runtime access. The developer should therefore investigate missing Apex class access behind the OmniScript’s actions.

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

A Sub-Integration Procedure Action lets a parent Integration Procedure call another Integration Procedure, so shared logic can be built once and reused wherever needed. This improves maintainability because future changes are made in the child Integration Procedure instead of being copied manually across many parent procedures. It also supports cleaner modular design: one procedure can handle a specific reusable operation, while parent procedures orchestrate the overall flow. Option A is not the key advantage because asynchronous behavior depends on specific chainable or queueable configuration. Option B is wrong because exception handling may still be required. Option C is not guaranteed, especially when chainable execution is used. The central design benefit is reuse and modularity of server-side logic.

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

A FlexCard is the correct front-end component for a single, focused view on a Contact record page. The data may come from Salesforce and an external grant management system, and an Integration Procedure can be used behind the scenes to aggregate that data. However, the question asks which OmniStudio tool should retrieve and display the combined information in a compact record-page view. A Data Mapper Transform reshapes data but does not provide the visual record-page card. A Calculation Procedure performs calculation logic, not case-manager display. OmniScript is better for guided multi-step processes, not quick contextual viewing. Salesforce documentation confirms that FlexCards can be configured with data sources, including Salesforce or external databases, and can display contextual information on record pages.

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

The AccountId is not the issue because the Debug Log already shows that the Data Mapper Extract retrieved data successfully. The failure is at the response-return stage of the Integration Procedure. In OmniStudio, a Response Action is used to end the Integration Procedure and return data to the caller. If the Data Mapper action runs but no Response Action is configured, the internal debug data can exist while the external response remains empty. Option A is weaker because the core requirement is not only adding data to an internal response JSON property; the Integration Procedure needs a Response Action to send the final output. Option C adds unnecessary and inaccurate wording about Send JSON Path. The clean verified cause is that no Response Action was added.

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

The correct configuration is the Knowledge Articles property on the Step element. OmniScript supports Salesforce Knowledge integration through Knowledge Options configured on a Step. This lets the developer display or filter Knowledge content where the user needs it in the guided process, such as a complex product-information step. A Knowledge Action is not the standard OmniScript element used for step-level help article display. Messaging Framework is unrelated because it handles messaging behavior, not Knowledge article rendering. A custom LWC could be built, but that would be unnecessary custom development when OmniScript already provides Knowledge configuration on the step. The requirement is step-specific, context-sensitive article display, so the Step element’s Knowledge Articles configuration is the correct answer.

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

If the user already has OmniScript runtime access, the next security issue to investigate is access to the underlying Apex classes used by OmniStudio runtime operations, Data Mappers, Integration Procedures, or Remote Actions. Salesforce’s OmniStudio security checks include Apex class access enforcement, especially where Remote Actions or managed package classes are involved. Save Options would affect how data is saved, not whether the Lightning component can be accessed. Multi-language settings do not cause a permission-to-access-component error. FlexCard permissions are not the most likely cause when the problem occurs while launching an OmniScript. Therefore, the developer should verify the user’s permission sets/profile grant access to the Apex classes required by the OmniScript’s runtime and called actions.

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

The correct answer is A. In a parent-child FlexCard design, attributes are passed from the parent FlexCard to the child FlexCard and referenced in the child using the Parent context variable. Salesforce documentation states that the Parent context variable is used to reference attributes from the parent FlexCard on the child FlexCard, and child FlexCard properties allow passing data from the parent by creating attributes and assigning data merge field values. Therefore, when the postal code is passed as a parent attribute, the child FlexCard should reference it as {Parent.postalcode}. {Params.postalcode} is used for URL or runtime parameters, {postalcode} references local data only, and {attr.postalcode} is not the correct OmniStudio parent context syntax.

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

A contextual cache key partitions cached Integration Procedure data by the key value. Since the first request used AccountId = 001A, that cache entry is valid only for that contextual value. A later request using AccountId = 001B is a different context, so OmniStudio should not return the 001A response. Instead, the Integration Procedure runs again and creates a separate cache entry for 001B. This is the point of contextual caching: improve performance without mixing data across records or users. Option A is wrong because a new key does not clear the previous key. Option B is wrong because contextual keys are valid cache configuration. Option C would be a serious data leakage issue.

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

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. 

OmniStudio does not natively support direct JSON-to-XML transformation using DataRaptors. When a transformation to specific XML formats is needed for integration with external web services, it is recommended to use Remote Actions that invoke custom Apex classes.

A. Use a Remote Action that calls the XMLStreamWriter class – Correct. The XMLStreamWriter Apex class provides precise control over XML structure and is the Salesforce-recommended way to programmatically generate XML from data within a Remote Action step in an Integration Procedure.

Incorrect Options:

B. The XML checkbox in DataRaptor does not convert JSON to XML; it defines output data format for display or API serialization.

C. XMLStreamReader is used for parsing XML, not for generating it.

D. DataRaptor Transforms only manipulate JSON structure; they do not support converting JSON into XML format.

Salesforce Developer Guide → Apex XMLStreamWriter Class

OmniStudio Integration Procedures → Using Remote Actions with Custom Apex

Margin controls spacing outside an element, so Margin Bottom is the correct property when the goal is to create or reduce space between the Text element and the Button below it. Padding controls internal spacing inside the boundaries of the selected element; it would move the text within its own box rather than primarily controlling the gap between two separate elements. Layout controls structural placement and responsiveness, not direct vertical spacing. Spacer can be used as a separate layout object, but it is not the property on the Text element itself. Salesforce’s FlexCard styling guidance separates dimensions, spacing, classes, and inline styles, and the spacing-around-element documentation specifically uses margin controls for external spacing.

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

The child OmniScript must receive specific nodes from the parent OmniScript’s data JSON, so the developer should pass them through Additional Input key/value pairs on the child OmniScript element. Additional Input is used to pass named values into an action or embedded component when the child process needs specific data from the current script context. ContextId would pass only a record identifier, not full Address and Contact JSON nodes. PreFill is used to populate data into an OmniScript, but the question asks which property on the child OmniScript element should be used to pass parent nodes. LWC Component Override is unrelated because it replaces rendering behavior rather than mapping parent script data. Therefore, Additional Input is the correct configuration.

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

The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The % sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.

An Integration Procedure that calls a Remote Action depends on the referenced Apex class existing in the target org. If the Apex class is missing, the Integration Procedure cannot resolve that dependency during deployment or execution. The required fix is to deploy the Apex class first, then deploy the Integration Procedure that references it. Cache Duration has no relationship to metadata dependency resolution. Chainable configuration controls long-running transaction behavior and governor-limit handling, not missing Apex metadata. A Try-Catch Block can help handle runtime failures, but it does not solve a deployment failure caused by an absent Apex class. Salesforce’s OmniStudio deployment guidance specifically includes considerations for Apex class checks and dependencies when deploying Integration Procedures.

 The Use Data JSON property must be selected in the properties of the Type Ahead Block in order to display the fetched data in the fields. The Lookup Mode property is used to specify the type of lookup to perform. The FirstName, LastName, and BirthDate fields can be placed inside or outside the Type Ahead Block. The typeHead key is in the correct 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.

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

Cloning an Integration Procedure creates a copy of it that can be modified and used independently from the original one. This is useful when the new Integration Procedure has a different purpose or functionality than the original one

When testing a FlexCard data source in the designer, the developer must provide valid runtime values for context variables so the configured Integration Procedure can execute as it would at runtime. In this scenario, that means manually entering a valid Context ID, such as an Account record ID, in the Setup or Test Data Source settings and then viewing the returned data. Without a valid context value, the Integration Procedure may not receive the input required to query Account, Opportunity, and Case data. Option C is important inside the Integration Procedure design, but the question asks about testing the FlexCard’s data configuration in the designer. Option B is not generally required for SOQL. Option D is a design choice, not the key testing step.

According to the DataRaptor Load Overview page, a Linked Mapping is used to “create or update multiple records in different objects that are related by lookup fields”.

The element name for the missing data must match the JSON node key in the Integration Procedure Response, otherwise the data will not be mapped correctly. The JSON sent from the Integration Procedure Action must match one of the Original Input for the Integration Procedure, otherwise the Integration Procedure will not execute properly. The Integration Procedure Preview Input Parameters and the Response JSON Path have no effect on displaying data in OmniScript.

This scenario relates to FlexCard preview behavior and data mapping issues.

B. There is no Salesforce record for the FlexCard based on the RecordId in the layout ' s Test Data Source Settings – If the test record does not exist, the FlexCard will not display any data during preview. This is a common setup mistake.

C. The Data Node field for the FlexCard is empty – The Data Node field must be set correctly to match the JSON node where the expected data resides. If it is empty or incorrect, the FlexCard won’t bind data to UI elements.

Incorrect Options:

A. Even if the RecordId is from a different record type, as long as the data structure aligns, it would still render; it’s not a definitive reason for the card failing to display.

D. Attributes are not required to display field values directly; they are used for passing data between cards or from context, not for direct field rendering.

Salesforce OmniStudio → FlexCard Data Source Setup & Troubleshooting

The data action should be placed where the step can retrieve the required data before the user needs to see or use it. Placing the Data Mapper Extract Action on the same relevant step keeps the data retrieval close to the UI elements that depend on it and avoids loading unrelated data globally in the Header. Placing the action after the data usage is obviously too late because the fields or options would already be rendered without the needed values. A Set Values element cannot execute a Data Mapper Extract; it only sets or changes values in the OmniScript data JSON. Salesforce’s OmniScript action-element documentation explains that action elements are used to get, modify, and write data during the OmniScript process.

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

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

The most direct and lowest-risk method is to use the Clone button in the Data Mapper Designer. Cloning preserves the original Data Mapper configuration and creates a separate copy that can be modified for the new requirement. Manual copy-and-paste is inefficient and error-prone because mappings, formulas, filters, and output paths can easily be missed. Using SFCLI or deployment tooling to duplicate JSON is possible for advanced source-control workflows, but it is not the most straightforward designer-based approach. Creating an Integration Procedure to call the old Data Mapper does not create a new independent Data Mapper and would not let the developer safely change the mapping logic for the new requirement. Cloning is the intended starting point for this scenario.

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

The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.

The missing access is execute access to the specific Apex class used by the Remote Action. A Remote Action in an Integration Procedure invokes Apex or an invocable action, so the running user must be authorized to execute that Apex class. Salesforce documentation for OmniStudio Apex class permission checkers states that access must be enabled for the classes used by Remote Action APIs for each profile, permission set, or permission set group. “Run Flows” is irrelevant because this is not Flow execution. General data-model access may still be required for object operations, but it does not authorize the Apex class itself. A Try-Catch Block can catch or handle an error response, but it does not fix the underlying unauthorized Apex execution failure.

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

According to the Transform External Data Unit, the Expected Output JSON should match the Output Path of the DataRaptor Transform. In option D, the Output Path is Current:CityState, which matches the Expected Output JSON. The other options have different Output Paths that do not match the Expected Output JSON. Therefore, the correct answer is D.

The minimum access is the OmniStudio User permission set license plus the OmniStudio User permission set. This user only executes guided flows; they do not build or modify OmniScripts, FlexCards, Data Mappers, or Integration Procedures. Assigning OmniStudio Admin would over-permission the user because Admin access is intended for users who create and manage OmniStudio components. A developer permission set would also be excessive and is not the minimum runtime configuration. A PSL alone is not enough because it entitles the user to the feature set, while the permission set grants usable permissions. Salesforce permission guidance states that users must have the appropriate OmniStudio permission set assigned, and the OmniStudio User assignment is appropriate for runtime users rather than designers/admins.

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.

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

According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: AccountName, AccountNumber, AccountType, AccountOwner, ContactName, and ContactPhone. The DRGetAccountDetails action is a DataRaptor Extract action that retrieves data from the Account and Contact objects in Salesforce. The BlkContacts element is a Repeat Block that displays a list of contacts related to the account. Therefore, the JSON from the DRGetAccountDetails action that would display all six values correctly in the OmniScript structure shown is option C, which has the following structure:

{ The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

The correct syntax for merge codes in Integration Procedure is {(NodeName)}, where NodeName is the name of the JSON node in the data source. The other options are either missing the parentheses or using incorrect symbols.

 According to the OmniStudio Developer Guide, “To upsert a record, select the Upsert Key checkbox for the field that contains the unique identifier for the record. If you want to create a new record when no match is found, select Is Required for Upsert.” Therefore, the correct answer is B.

 According to the FlexCard Designer Overview page, another possible cause of a field showing only the label is that “the field is null on the Salesforce record”.

 According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel shown is option C, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

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.