Explanation:

In Salesforce Industries CPQ and Asset-Based Ordering (ABO), an Asset represents the "Installed Base" of a customer.

When a Quote or Order is successfully fulfilled and activated, the line items are converted into Assets. These records track exactly what the customer currently owns or is subscribed to, such as a specific mobile plan, a serialized router, or a cloud software license.

Assets form the foundation for MACD (Move, Add, Change, Delete) operations, allowing developers to create "Change" orders to modify existing services.

Why Other Options are Incorrect

A. An irreplaceable item of high value
This is a general dictionary definition and does not reflect the technical meaning within Salesforce CRM or CPQ systems.

C. Any commercial or technical item required for a customer purchase
This describes a Product or Service in the shared catalog. An item only becomes an Asset after the purchase is finalized and the service is provisioned for the customer.

References
Salesforce Help: Asset-Based Ordering guide – review the lifecycle of an asset.

Explanation:

Correct Option: 🟢 C. Both of the above
Salesforce Communications Cloud encompasses both order management and contract management. Order management, through Industries Order Management, streamlines order fulfillment and tracking, ensuring efficient customer experiences. Contract management, via Contract Lifecycle Management (CLM), facilitates contract creation, negotiation, and execution. These capabilities integrate with Industries CPQ to support end-to-end telecom processes, enhancing operational efficiency and customer satisfaction within a comprehensive Business Support System (BSS).

Incorrect Option: 🔵 A. Order management
While order management is a key capability of Communications Cloud, selecting only this option is incomplete. It excludes contract management, which is equally critical for managing agreements and renewals in telecom operations. Order management handles order orchestration but doesn’t cover the full scope of BSS functionalities like contract lifecycle processes, making this choice insufficient on its own.

Incorrect Option: 🟡 B. Contract management
Contract management is a vital feature of Communications Cloud, enabling contract creation and execution. However, choosing only this option overlooks order management, a core component for order fulfillment and tracking. This limited selection fails to capture the integrated BSS capabilities of Communications Cloud, which combines both to support comprehensive telecom operations.

Summary:
The question tests knowledge of Salesforce Communications Cloud’s business capabilities, focusing on its role as a BSS for telecom providers. It evaluates understanding of how order management (order fulfillment) and contract management (agreement lifecycle) work together to streamline operations. Selecting “both” reflects the platform’s holistic approach, integrating CPQ, order orchestration, and CLM to deliver end-to-end solutions for CSPs.

Reference:
Salesforce Communications Cloud

Explanation:

When you adjust the price of a product for a promotion in Salesforce Industries CPQ (formerly Vlocity):

You’re modifying pricing data, not the product hierarchy or core catalog structure.

Promotions and price adjustments:
Are stored as records linked to products or price list entries.
Do not change the parent-child relationships of products in the hierarchy.
Do not require platform cache refresh in most cases for price updates.

Hence:

You do NOT have to run Product Hierarchy Maintenance when merely updating prices or promotions.
You also typically do NOT need to refresh platform cache simply because of price changes—price data is fetched fresh during cart calculations.

Running jobs like:

Product Hierarchy Maintenance
Refresh Platform Cache
→ These are necessary when you:

✅ Change the structure of the product hierarchy (e.g. new parent/child relationships).
✅ Add new products to the catalog that should appear in search trees.
✅ Change data that affects cached catalog structures (like hierarchy paths).

But price adjustments for promotions don’t require these jobs.

Example
You change the promo discount for “iPhone X” from $50 off to $75 off.
This update happens directly in the promotion or price adjustment record.
No need to run maintenance jobs afterward.

Explanation:

In Salesforce Industries (Vlocity) CPQ, assetization is the process that creates Asset records from order line items after order submission and activation. Not all products should become assets, such as one-time fees, virtual services, promotions, or non-fulfillable items.

To make a product not assetizable, you must configure it at the product (EPC) level. Salesforce Industries provides explicit flags for this purpose.

Why options A and B are correct
A. Check the Virtual Item flag in Vlocity EPC
The Virtual Item flag indicates that the product is not a physical or managed asset and should not result in an Asset record.
Common use cases include one-time charges, fees, promotions, and logical or placeholder items.
Marking a product as a Virtual Item automatically prevents asset creation.

B. Check the Not Assetizable flag in Vlocity EPC
This flag explicitly tells the system not to assetize the product.
Even if the product is otherwise eligible, such as recurring or service products, this flag overrides that behavior.
This is the most direct and explicit control for assetization.

Both flags are best-practice, design-time controls and are commonly tested on the Salesforce Certified Industries CPQ Developer (Ind-Dev-201) exam.

Why the other options are incorrect
C. Create a context rule to control assetization in Vlocity EPC
Context rules control qualification, compatibility, and visibility, but they do not control asset creation.
Assetization is not rule-driven in this way.

D. Check the Do Not Assetize flag in Vlocity Cart's line item configuration window
There is no supported cart-level flag to control assetization.
Assetization behavior must be defined before runtime, in EPC.
Cart configuration is too late in the lifecycle to change assetization rules.

Key Exam Takeaway
Assetization is controlled at the product definition level in EPC, not at runtime.
To prevent asset creation, use the Virtual Item flag or the Not Assetizable flag.

Explanation:

In Salesforce Industries CPQ (Vlocity), when working with asset-based ordering, you can generate a quote from an existing asset by using the Change to Quote action. This action allows you to take the customer’s current assets (e.g., subscribed products or services) and create a new quote that reflects modifications, upgrades, or cancellations.

Let’s break down the distractors:

B. From the Quotes tab
→ You can create new quotes here, but not directly from existing assets.
C. From the Opportunities tab
→ Quotes can be linked to opportunities, but this is not how you generate a quote from assets.
D. From the Orders tab
→ Orders reflect fulfilled quotes; they don’t generate quotes from assets.

The Change to Quote action is specifically designed for asset-based scenarios, making A the correct answer.

Reference:
Salesforce Industries CPQ Documentation – Asset-Based Ordering and Change to Quote