A sales user created a quote with one line item last week, and new features...

The source identifies acontext-definition mismatch between Pricing and Product Discovery. The pricing procedure must use the context definition selected in Product Discovery Settings so that catalog browsing, configuration, and pricing operate over a compatible transactional context.

Context Service acts as a common data contract among Revenue Management components. If Product Discovery hydrates one context definition while the pricing procedure expects another incompatible definition, required nodes, mappings, attributes, or tags can be unavailable. That can manifest both as missing products in Browse Catalog and configuration errors on existing lines.

The timing in the scenario is important: the quote worked before a production deployment and fails afterward. This strongly suggests that metadata or configuration introduced by deployment is inconsistent rather than the quote itself suddenly becoming invalid.

Option A points to general Revenue Settings rather than the feature-specific context selection identified by the source. Option C similarly treats Pricing Setup as the authoritative Product Discovery context configuration.

The implementation principle is to preservecontext-definition alignment across Product Discovery, configuration, and pricingwhen deploying Revenue Management metadata.

Study Guide Reference:Catalog Management — Product Discovery Settings; Context Service; pricing-context alignment; deployment troubleshooting.

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