Important Salesforce Plat-Dev-210 Exam Questions

Answer: B

Explanation:

FlexCards support embedding a custom Lightning web component through the Custom LWC element. The developer should drag the Custom LWC element onto the FlexCard canvas and configure the component name so OmniStudio knows which Lightning web component to render. Using an HTML element with an lwc tag is not the supported declarative method and can create security, rendering, and maintenance problems. An Action element is used to trigger behavior such as launching flows, OmniScripts, or navigation, not to host an LWC visually inside the card. Option D is also wrong because the configuration does not point to a ''Card'' property for the Lightning web component. The required implementation is the Custom LWC element with the component name configured.

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

Answer: A

Explanation:

According to the OmniStudio DataRaptor Extract documentation, if a developer wants to limit the number of records returned, the best way is to set the 'Limit' property on the element or action that is calling the DataRaptor, such as in an Integration Procedure or OmniScript Action.

A . Set the Limit property on the action that calls the Data Mapper Extract -- This is the correct method. The calling context (e.g., OmniScript Action or Integration Procedure) includes a property for setting the limit on query results, which is a recommended and clean method to ensure only one record is retrieved.

Incorrect Options:

B . There is no 'LIMIT' clause within the DataRaptor Extract definition UI or JSON definition itself.

C . Custom Output Type controls the structure, not the quantity of output.

D . The Filter function applies conditional logic, not record count.

Salesforce OmniStudio Developer Guide DataRaptor Extract Configuration

Answer: B

Explanation:

The correct configuration is to disable Save for Later through the OmniScript setup configuration, not by hiding it with CSS or deleting a nonexistent structural element. Save for Later is a framework-level OmniScript capability controlled by Save Options, so the proper approach is a configuration setting in the Setup tab. Conditional View is used for OmniScript elements, but Save for Later is not a normal element placed in the script structure. Custom CSS would only hide the button visually and would be a poor, fragile workaround. Salesforce documentation describes Save and Resume behavior as an OmniScript Save Options feature and confirms that Save for Later can be enabled or disabled through configuration rather than custom UI manipulation.

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

Answer: A

Explanation:

According to theIntegration Procedure Actionspage, ''To pass data from a Set Values action to a DataRaptor action, add the Set Values action name to the Additional Input field of the DataRaptor action.''

Answer: A

Explanation:

A Remote Action is the Integration Procedure element designed to call custom Apex logic. This scenario requires execution of an Apex method that performs custom authentication and token generation before later data retrieval, which is exactly the type of server-side custom logic handled by a Remote Action. A Data Mapper Transform restructures data; it does not execute Apex. A Sub-Integration Procedure calls another Integration Procedure, not an Apex method directly. An HTTP Action calls an external REST endpoint, which is useful after token generation but does not execute local Apex code. Salesforce documentation explicitly states that the Remote Action element calls the specified Apex class and method or an invocable action.

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