Plat-Dev-210 Exam Dumps and Practice Questions

In Preview, the JSON node that shows the data sent to the Response Action is the name of the Response Action itself. In this case, it is ResponseCart. The other nodes show either the input data or the output data of the Integration Procedure.

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

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript. Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce's OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

The verified answer is A, not the mock-highlighted C. FlexCard States display based on conditions configured on the state. For this scenario, the Active, Warning, and Critical states should each have a condition that evaluates the RiskLevel value. For example, Active can evaluate RiskLevel = Low, Warning can evaluate RiskLevel = Medium, and Critical can evaluate RiskLevel = High. At runtime, OmniStudio evaluates the state conditions, and the matching state is displayed. A Set State Action on a button is user-driven and does not automatically evaluate RiskLevel. ''Conditional State Logic on the Base FlexCard'' is not the precise configuration item used here. A main Block state variable is also not what controls card-level state selection.