From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.
* A. OmniScript Action - This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.
Incorrect Options:
* B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.
* C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.
OmniStudio Developer Guide # OmniScript Actions

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.

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:
* A. "The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript." This is a common configuration issue. If the paths between the OmniScript ' s structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.
* B. "The fields that are not updated are read-only in Salesforce."If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.
Incorrect Options:
* C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.
* D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.
Salesforce OmniStudio Developer Guide # DataRaptor Load # Troubleshooting Salesforce Help Documentation: OmniStudio DataRaptor Best Practices