OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Free Practice Exam Questions (2026 Updated)

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.

he Aggregation Step in a calculation procedure allows the developer to perform aggregate functions such as SUM, COUNT, MIN, MAX, and AVG on the output of a previous step. The developer can use this step to calculate the sum of the entire base price by specifying the field name and the aggregation function

 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.

Integration Procedure is the correct tool because the requirement goes beyond a simple Salesforce record extraction. Complex filtering, sorting, aggregation, orchestration, and preparation should be handled server-side before the OmniScript displays the result. A Data Mapper Extract is appropriate for retrieving Salesforce data, but it is not the best orchestration layer when multiple operations and preparation logic are required. An HTTP Action only calls an external endpoint; it does not by itself manage the full data-preparation workflow. A Set Values Action is useful for assigning values in the OmniScript data JSON, not for complex server-side data shaping. Salesforce describes Integration Procedures as server-side processes used to automate data operations between Salesforce and external systems, which matches this requirement.

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

In OmniStudio Integration Procedures, when referencing data from a prior step in the HTTP Action URL, the correct merge code syntax is:

%ElementName.PropertyName%

So, referencing a value called Date from a step named SetValues must be written as:

%SetValues.Date%

This is the format recognized by the OmniStudio Merge Language (OML) for dynamic value substitution in URLs or headers.

Incorrect Options:

A. Invalid syntax – not recognized by OmniStudio merge logic.

B. {{SetValues.Date}} is used in FlexCards, not in Integration Procedures.

D. %SetValues: Date% is incorrect merge syntax due to space and colon use.

Salesforce OmniStudio Documentation → Merge Code Syntax for Integration Procedures

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.

The Expression Set component in OmniStudio allows developers to perform calculations using steps such as Aggregation, Calculation, and Sub Expression.

C. Add an Aggregation Step as SUM(BasePrice) – This is correct. Aggregation steps are specifically designed to perform functions like SUM, AVG, COUNT, MIN, MAX over collections (arrays) of data. In this use case, summing the entire BasePrice array is best handled using an Aggregation Step.

Incorrect Options:

A. Sub Expression Step is used to combine or manipulate previously calculated values, not to aggregate across an array.

B. Calculation Step is used for row-level calculations, not aggregation across multiple rows.

Salesforce OmniStudio Documentation → Expression Sets → Aggregation Step

 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’)}}.

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 syntax for merge codes in OmniScript is %%sNodeName%%, where NodeName is the name of the JSON node in the data source. The other options are either missing the s or using incorrect symbols.

The correct best practice is to use one Data Mapper Load configured for the related object mappings. Salesforce documentation explains that Data Mapper Load supports updates to multiple Salesforce objects and displays separate mapping tabs for each target object. It also documents Multiple Related Object Loads, or Link Mappings, for propagating data between related objects during a load sequence. This avoids unnecessary multiple sequential Data Mapper Load Actions and keeps the update logic declarative, maintainable, and transactionally cleaner. A Remote Action with Apex should only be used when declarative mapping cannot satisfy the requirement. A Salesforce REST API HTTP Action is also unnecessary because the operation is inside Salesforce and OmniStudio already provides Data Mapper Load for this exact use case.

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

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 Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues. 

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.

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

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. 

The cleanest method is to assign a unique CSS class to the second Block and apply the styling once at the Block level. This keeps the design maintainable because all less-critical fields inside that Block inherit or are affected by the same styling pattern. Manually changing each Text element works technically, but it is inefficient and harder to maintain if more fields are added later. A Layout property does not exist as a reliable “Small” styling switch for this requirement. A State element is for alternate card presentations based on conditions, not simply applying a different font style to one section. Salesforce FlexCard documentation supports applying custom CSS classes and inline styles to FlexCard elements when built-in style properties are not enough.

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

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’)}}.

The best practice is to create a separate child FlexCard for the related-contact display. A child FlexCard gives the team a reusable UI component that can be embedded in other FlexCards without copying layout elements, actions, fields, and styling each time. Duplicating the elements would create maintenance problems because later changes must be repeated everywhere. A global CSS class can standardize appearance, but it does not make the component logic reusable. A Data Mapper can retrieve or transform data, but it is not a display component. Salesforce documentation confirms that FlexCards can be embedded inside other FlexCards and can use either their own data source or the parent FlexCard’s data, which supports modular reuse.

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