A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths.
However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.

The Debug Console, or Test Panel, is the correct browser-based tool for testing OmniScript logic and data integration during development. Salesforce CLI and Vlocity Build Tool are deployment or source-control tools; they are not the interactive runtime testing panel inside the OmniScript Designer. Developer Console can inspect Apex and logs, but it is not the built-in OmniScript testing interface. The OmniScript designer preview/debug capability lets the developer execute actions, inspect action requests and responses, and verify how data moves through the script before deployment. Salesforce documentation specifically describes opening the Action Debugger from Preview to view and debug action request and response data, which directly matches the requirement to test script logic and integration behavior.

The correct Output JSON Path is input:BasePrice. The required JSON places BasePrice inside the lowercase input node, so the path must preserve both the correct parent node and the exact field name casing. Option A is wrong because it uses dot notation and incorrectly lowercases BasePrice as baseprice. Option B is wrong because it uses Input with an uppercase I, while the JSON node is input. In JSON-based mappings, path and field names must match the expected output structure. Salesforce's Data Mapper Transform documentation states that the Output JSON Path defines the desired output path and that path levels are separated using colon syntax, for example Contact:LastName. Therefore, C is the only mapping that correctly targets the BasePrice node under input.

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 best available answer is A, but the wording is not perfect. The safe testing pattern is to avoid changing the published cache configuration used by production users. Changing Cache Duration to 0 or disabling the Cache property would alter runtime behavior for everyone using that active Integration Procedure. Changing Type/SubType is also a bad workaround because it changes the component identity and can break callers. A throwaway test input is the least disruptive option because it lets the developer create an isolated request path for testing rather than clearing or disabling shared production cache. In a real implementation, the test value must affect the effective cache signature; if an explicit Cache Key Property is configured and the throwaway value is outside that key, it will not bypass the cached entry.