Explanation:

In Salesforce Industries CPQ (Vlocity CPQ) and Salesforce Billing, an Asset represents a product or service that a customer has already purchased and is tied to a Contract or Subscription.

Why Option B is Correct:
Assets are tracked post-sale and can be used for:

Renewals (e.g., upgrading an existing product)
Entitlements (e.g., service agreements)
Usage-based billing (e.g., tracking consumed services)

Example: If a customer buys a "Cloud Storage Plan," it becomes an Asset in Salesforce.

Why Other Options Are Incorrect:

A. "An irreplaceable item of high value"
This is a general business definition (like real estate or machinery), not Salesforce CPQ’s definition.

C. "Any commercial or technical item required for a customer purchase"
This describes a Product or Configuration, not an Asset.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity CPQ), Compatibility Rules are used to enforce valid product combinations. These rules ensure that when a user selects one product, only compatible products are shown or selectable.

Product Relationships define how products relate to one another (e.g., requires, excludes, auto-add).

In a Compatibility Rule, the Rule Action refers to a Product Relationship — it tells the system what to do when the condition in the rule is met (e.g., prevent selection, add a product automatically, etc.).

So yes, Compatibility Rules use Product Relationships as their Rule Action — this is a fundamental way Vlocity CPQ handles guided selling logic.

Explanation:

In Salesforce Industries CPQ, the base price is the foundational price of a product before any discounts, overrides, or adjustments are applied. Understanding which components use this base price in their logic is key to configuring pricing flows correctly.

✅ A. Pricing element adjustment
A pricing element adjustment modifies the base price by applying a percentage or fixed value change.
It uses the base price as the starting point and then calculates the final price by adding or subtracting the adjustment.
Common use cases include promotional discounts, regional surcharges, or loyalty incentives.

❌ Why the Other Options Are Incorrect:

B. Pricing element override
This replaces the base price entirely with a new value.
It does not calculate from the base price — it ignores it and sets a fixed price instead.

C. Price list
The price list defines the base price but doesn’t calculate from it.
It’s the source of the base price, not a consumer of it.

Explanation:

In Guided Selling within Salesforce Industries (formerly Vlocity), if you want to retrieve products filtered by object type, one of the standard methods is to use a DataRaptor with specific filtering logic. This allows dynamic and server-side filtering based on values such as object types, product families, or custom fields.

Why the other options are not ideal:

A. Add a reusable OmniScript – OmniScripts can guide the process but do not directly filter product data.

B. Use a text query to find the object type – Text queries are not efficient or reliable for structured filtering like object types.

C. Use the Type field of Salesforce – While valid in concept, this doesn't directly apply filtering without using a tool like DataRaptor.

Explanation:

When creating a quote from an existing asset, the corresponding line item status is set to "Change" because:

The asset is being modified (e.g., upgrading a plan, adjusting terms).
This status distinguishes it from new items ("Add") or unchanged items ("Existing").

Why Other Options Are Incorrect:

A. Add: For new products not linked to existing assets.
B. Existing: For assets unchanged in the quote.
D. Disconnect: For assets being removed (not modified).