This two-tier requirement calls for two distinct mechanisms: a non-blocking warning (commonly implemented via a flow-driven screen message or informational alert, not a hard validation rule, since it should not prevent submission) at 20%, and a formal Approval Process with entry criteria referencing the calculated discount percentage at the 35% threshold, which routes the Quote for manager sign-off. A single blocking validation rule would incorrectly prevent reps from proceeding at the lower 20% threshold, and hardcoding a max discount on Product2 does not support this tiered warning/approval structure.

Revenue Cloud Product Discovery provides a Default Catalog option in Product Discovery Settings so that:
If there is only one primary catalog, it can be preselected automatically.
Users are not prompted to choose a catalog each time.

"Derived Pricing allows a product's price to be calculated based on another product's price, either within the same quote or across transactions."
*"The Derived Pricing Scope determines when and how the derived price is evaluated:
Transactional: The derived price is calculated dynamically when both products are in the same quote or order.
Global: The derived price references a price from the catalog or price book, not quote-specific."*
"If the Derived Pricing Scope is not set to Transactional, product interdependencies within the same quote will not evaluate." Step-by-Step Reasoning:
Scenario: Warranty should price dynamically based on another product in the same transaction.
Root Cause: The Derived Pricing Scope on the warranty product is likely not set to Transactional.
Solution: Update the Derived Price record for the warranty product set Derived Pricing Scope = Transactional.
Why B is Correct: Ensures the price is recalculated dynamically when the related product exists in the same quote/order.

When using Product Catalog Management in Salesforce Revenue Cloud, visibility of products during quote creation (especially through Product Discovery) is controlled by the Context Definition. Contexts allow administrators to define when and for whom products are visible during the product selection process, based on criteria like sales channels, quote type, or other business rules.
If products are not appearing during quote preparation, it is often due to a missing or misconfigured context definition. Assigning the correct Context Definition in Product Discovery Settings ensures that products and bundles are available during quoting based on business logic.

In Salesforce Revenue Cloud, particularly when managing Lot-based or As-Is Renewals, the system tracks pricing and lifecycle changes using the Asset Action object. This object represents a single lifecycle event (e.g., purchase, renewal, upgrade) that occurred to an asset and captures:
Net Unit Price at the time of action
Action type (e.g., renewal, cancellation)
Source and target pricing metadata
To trace back the renewal price to the original net unit price, users should examine the Asset Action records associated with the asset. Each action contains detailed pricing information at the time the action was executed, enabling full auditability.