The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle-managed records (e.g., originating from CPQ+ or Subscription Management flows).
This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK's app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce.

In Salesforce Revenue Cloud's Contract Lifecycle Management (CLM) module, Obligations are used to track post-signature responsibilities and ensure compliance with contractual commitments. An obligation represents an actionable item tied to a contract clause, such as delivering a report, making a payment, or completing a follow-up.
One of the primary benefits of creating obligations is the ability to:
Assign Owners (users or roles)
Attach Tasks
Set due dates, statuses, and related metadata
This allows organizations to track performance on obligations over the lifecycle of the agreement and maintain accountability.
Option A is correct, as assigning owners and tasks is core to the obligation management model.

"Bundle-Based Pricing allows you to define how the total price of a bundle is determined, whether from component prices, a fixed price, or dynamic price calculation."
"Price Adjustment Matrices are used within pricing procedures to apply conditional or tiered discounts to bundle or product pricing."
"Attribute-Based Pricing is used for pricing individual products based on attribute values, not entire bundles." Step-by-Step Reasoning:
Requirement:
Create bundle pricing logic (discounted total price).
Apply varying discounts under specific conditions.
Correct Components:
Bundle-Based Price: Controls how bundle total is derived.
Price Adjustment Matrix: Applies dynamic, condition-based discounts.
Why B is Correct:
Matches both aspects -- bundle calculation and dynamic discounting.

In Salesforce Revenue Cloud, when product bundle behavior must change dynamically based on contextual data (e.g., Opportunity or Account fields), the correct approach is to use context-aware Constraint Models. Constraint Models can reference context attributes, such as the Industry field from the parent Opportunity, to dynamically control which product options are available or preselected during bundle configuration.
This approach ensures the configurator UI loads with the correct options and default selections without additional automation or UI components. The logic resides in the Constraint Model, which can define inclusion, exclusion, or recommendation rules that evaluate the context in real time.
Flows or configuration rules (like option B) don't have direct access to Opportunity context within the configurator session; Constraint Models are specifically designed for contextual, attribute- driven logic.

"During quote-to-contract conversion, the selection options presented in the discount popup are derived from the Contract Item Price object's Discount Type picklist field."
"Administrators can remove or rename values from the Discount Type picklist to customize which discount options appear to users during the conversion process."
"The screen flow and LWC components rely on metadata values; modifying these underlying picklist entries changes the available options in the UI." Step-by-Step Reasoning:
Requirement: Remove "None" option from the discount-selection popup.
Configuration Location: The options come from Contract Item Price Discount Type picklist.
Solution: Remove the "None" picklist value in object metadata setup.
Why B is Correct:
Declaratively removes the undesired value from the popup.