Explanation:

Default Pricing Plan Step Sequence:
The standard flow for pricing in Salesforce CPQ follows this order:
Initialize Pricing Context (Sets up the pricing environment).
[Custom Attribute-Based Pricing Step] (Your custom logic here).
Load Price List Entries (Fetches prices from price lists).
Apply Offer Adjustments (Applies discounts/promotions).

Why Option D is Correct:
Attribute-based pricing must run after the context is initialized (to access product/quote data) but before price lists are loaded (to influence which prices are fetched).

Example: A rule like *"If Storage=256GB, apply Price List X"* requires context but must execute before price lists load.

Why Other Options Are Incorrect:
A. After Apply Parent Variables: Too late—price lists are already loaded.
B. Before Initialize Pricing Context: Impossible—no context exists yet.
C. Between Initialize Pricing Variables and Apply Offer Adjustments: Skips critical price list loading.

Explanation:

Why Option C is Correct?
In Salesforce Industries CPQ (Vlocity CPQ), product attributes are used to define customizable properties of a product (e.g., color, size, material). Before creating an attribute, you must:

Create an Attribute Category → This acts as a container for related attributes.
Example: A category named "Display Options" could hold attributes like "Screen Size" and "Resolution".
Without a category, attributes cannot be logically grouped or assigned to products.

Why Other Options Are Incorrect?

A. Create the product → Attributes can be created before or after products exist. They are linked later via Attribute Assignments.
B. Create the object type → While object types (e.g., "Device") are used in Vlocity Data Model, they are not required for basic attribute creation.
D. Create the picklist → Picklists define attribute values (e.g., "Red/Blue/Green"), but the attribute itself must exist first.

Explanation:

In Salesforce Industries CPQ, cart-based guided selling experiences are often built using AngularJS templates, especially in legacy implementations or when using the Digital Commerce framework. These templates:

Power the interactive cart UI, enabling dynamic product selection and configuration.
Work alongside Cart APIs to manage product recommendations, pricing, and quote generation.
Are ideal for internal user flows with known traffic patterns and authenticated sessions.

This approach allows developers to customize the guided selling journey using modular, reusable components that respond to user inputs and backend logic.

Explanation:

Making a Product Non-Assetizable in Vlocity EPC:
To prevent a product from being converted to an asset after order fulfillment:

Option A: Enable the Virtual Item flag (for services/digital goods with no physical asset).
Option B: Enable the Not Assetizable flag (explicitly blocks asset creation).

Why Options A & B?

Virtual Item: Implies the product is a service (e.g., "Installation") and skips asset tracking.
Not Assetizable: Hard override to exclude from assetization (e.g., one-time fees).

Reference: Vlocity Product Configuration

Why Not C & D?
C: Context rules manage pricing/logic, not assetization.
D: No "Do Not Assetize" flag exists in cart configuration.

Explanation:

In Salesforce Industries CPQ (Vlocity), you can assign multiple context rule sets to a single promotion. This flexibility allows developers to layer different qualification criteria—such as geography, account type, or product eligibility—into a promotion’s logic.

Each rule set can contain one or more context rules, and promotions can evaluate all assigned rule sets during runtime to determine whether the promotion should be qualified or disqualified for a given customer.

This modular approach makes it easier to:
Reuse rule sets across multiple promotions
Combine eligibility logic from different business domains
Maintain cleaner and more scalable rule configurations