Explanation
The two OmniStudio tools that the consultant should recommend to meet these requirements are: Calculation Matrix and DataRaptor Extract. A Calculation Matrix is a tool that can perform complex calculations based on multiple input variables and output values. The consultant can use a Calculation Matrix to look up the unit price using the product code, the grade, size, and then multiply the unit price by a discount factor. A DataRaptor Extract is a tool that can retrieve data from a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Extract to get the product code, grade, size, and discount factor from Salesforce

Explanation
The three tools that should be used in the solution are OmniScript, OmniStudio Action, and DataRaptor.
OmniScript can be used to create a user interface for generating invoices from contracts. OmniStudio Action can be used to conditionally display the invoice generation option on the contract page based on the contract status. DataRaptor can be used to read, transform, and write data between Salesforce and external systems.
Interaction Launcher is not needed for this scenario, as it is used to launch interactions from other applications.
FlexCards are not relevant for this scenario, as they are used to display contextual data on record pages.

Explanation
The two use cases that are best solved using Calculation Procedures & Matrices are: To apply the correct factor when determining a cost and To return output that is calculated differently based on the date. A Calculation Procedure is a tool that can perform complex calculations based on multiple input and output variables. A Calculation Matrix is a tool that can perform complex calculations based on multiple input variables and output values within groups. The consultant can use Calculation Procedures & Matrices to solve these use cases, because they involve applying rules and formulas to different data values and scenarios

Calculation Procedures & Matrices are used to perform complex calculations based on input data and predefined rules. They are suitable for use cases that involve pricing, rating, scoring, or eligibility determination. Therefore, the use cases that should be implemented using Calculation Procedures & Matrices are:
Use a house's address, size, and age of the building to determine an insurance premium. (This involves rating based on multiple factors) Use location and past usage to determine the monthly cost for an energy product. (This involves pricing based on variable inputs) Use risk factors for an insured item to determine different insurance product options. (This involves scoring and eligibility based on criteria) The use cases that should not be implemented using Calculation Procedures & Matrices are:
Use rules to determine eligible insurance products based on a house's address and age of the building.
(This can be done using Business Rules Engine or OmniScript logic)
Use the product color and capacity to determine the price of a product. (This can be done using simple formulas or lookup tables)