Explanation:

When new product bundles are added to the shared catalog in Salesforce Industries (Vlocity) CPQ, specific background jobs must be run to ensure the catalog structure and cart behavior are updated correctly across the platform.

B. Product Hierarchy Maintenance
This job is required to:
Rebuild and synchronize the product hierarchy
Ensure bundles, child products, and their relationships are structured correctly
Make newly added bundles visible and navigable in Guided Selling and Product Selection

If this job is not run, newly added bundles may not appear correctly or may not appear at all in the catalog hierarchy.

D. Refresh Platform Cache
This job performs the following functions:
Clears and reloads cached catalog and pricing data
Ensures newly added bundles are immediately available to users
Prevents issues where outdated catalog data continues to be displayed

This step is especially important after making changes to a shared catalog.

Why the other options are incorrect

A. Load API Metadata
This job is used to load API-related metadata and is not related to catalog structure, bundle availability, or product visibility.

C. EPCProductAttribJSONBatchJob
This job generates JSON data for product attributes. It is required when attribute definitions change, not when new product bundles are added to the catalog.

Key Exam Tip
For shared catalog updates, remember the following sequence:
Rebuilding structure → Product Hierarchy Maintenance
Making changes visible → Refresh Platform Cache

Explanation:

In the standard Salesforce Industries CPQ (Vlocity) Cart interface, the Line Item Cart pane, where selected products are displayed, is designed to provide a clear financial summary for each item. The five standard fields shown for each line item are listed below.

Standard Fields Displayed
Quantity: The number of units selected for the product.
Recurring Charge: The per-unit cost billed on a recurring basis, such as monthly charges.
Recurring Total: The total recurring cost for the line item, calculated as Quantity multiplied by the Recurring Charge.
One Time Charge: The one-time upfront cost per unit, such as an activation or setup fee.
One Time Total: The total upfront cost for the line item, calculated as Quantity multiplied by the One Time Charge.

Why Other Options are Incorrect

B
This option includes fields such as Total Charges and Discount Percentage, which are not part of the five standard, out-of-the-box fields displayed in the core cart line item pane.

C
Although the cart layout can be customized using templates like cpq-cart-item, the question refers specifically to the default configuration provided by the Salesforce Industries CPQ package, not a customized implementation.

D
The line item fields are fixed in the standard cart layout and cannot be dynamically altered by simple user interaction or selection within the user interface.

Reference:
Salesforce Help documentation for Industries CPQ Cart describes the default cart layout and the standard line item fields displayed in the cart interface.

Explanation:

Attribute-Based Pricing relies on a specific pricing engine workflow that moves data from the Cart to a lookup table and back again. The correct components work together to form this engine and enable dynamic pricing based on selected attributes.

Why "A, B, and D" are Correct
These three components make up the core Attribute-Based Pricing engine:

Calculation Matrices (D)
This component acts as the lookup table. It stores combinations of attribute inputs and their corresponding output prices. For example, a matrix row might define Attribute: Speed = 1Gbps with an Output Price of $70.

Calculation Procedures (B)
This is the logic layer. It takes attribute values from the Cart, passes them into the Calculation Matrix, retrieves the resulting output, and can apply additional calculations such as taxes, fees, or multi-service discounts before returning the final price to the Cart.

Pricing Plans (A)
This component orchestrates the pricing flow. For Attribute-Based Pricing to function, the Default Pricing Plan must include specific steps (such as InitializePricingContext or CalculatePrice) that trigger the Calculation Procedure during the pricing phase of the Cart lifecycle.

Why the Incorrect Answer is Wrong

C. Overrides
In Vlocity EPC, an Override is used to change the price or metadata of a child product when it is part of a bundle. While it does modify pricing, it is a static configuration defined at design time and does not use the dynamic lookup and calculation logic provided by Calculation Matrices and Procedures. Therefore, it does not support Attribute-Based Pricing.

References
Salesforce Help: Attribute-Based Pricing Overview
Vlocity Documentation: CME CPQ Pricing Guide for standard pricing plan step configurations required for Attribute-Based Pricing
Trailhead: Configure Attribute-Based Pricing

Explanation:

When a promotion is applied, especially to a bundle with child products, each adjustment line item (which represents the discount or price change) includes a Display Text or Description field. This text is what appears to the end user in the cart to explain why the price changed.

C is Correct
In the Promotion Rule, when you configure an Action (such as Adjust Price By Percentage or Override Price), there is a field to specify the Display Text for that adjustment. This text is propagated to the adjustment records created in the cart and is displayed next to the discounted price of the child product. It provides the most granular, accurate explanation because it is directly tied to the specific price change that was applied.

Why the other options are incorrect

A. The display text associated with the time policy
Time Plans control subscription duration and billing periods. They do not provide user-facing display text for promotions or discounts applied to prices.

B. The display text associated with the base price
The base price is defined by the Price List Entry. It does not include display text for explaining discounts or promotional adjustments.

D. The promotion description
The Promotion Description is a high-level administrative field. It is not automatically copied to individual adjustment line items in the cart. End users do not see this description as the explanation for a specific price change.

E. The promotion code
The Promotion Code is the value entered by the customer to activate the promotion. It is not used as the explanatory text for a discount shown on a line item in the cart.

User Experience
In the cart, a child product line might appear as:

List Price: $50
Adjustment: -$10 (Display Text: "Summer Sale Discount")
Final Price: $40

The text "Summer Sale Discount" comes directly from the Display Text configured on the Promotion Action.

Reference
Salesforce Industries CPQ documentation for creating Promotion Rules and Promotion Actions states that Adjust Price and Override Price actions include a Display Text field, which is the text shown to the customer in the order summary to explain the price adjustment.

Explanation:

In Salesforce Industries CPQ Guided Selling (using OmniScripts), the persistent cart (vlcCart) is a lightweight, embedded cart component that maintains cart state across OmniScript steps (unlike the full Vlocity Cart used in agent flows). The cart data lives inside the OmniScript’s data JSON, which persists between steps.

To ensure the vlcCart is created in the correct location in this data JSON (so it renders properly, persists, and updates correctly):

You must manually position it in the OmniScript JSON Editor (accessible from the OmniScript Designer via the JSON tab or Edit JSON).
Specifically, the vlcCart node must be placed as a child under the vlcPersistentComponent parent node.

The vlcPersistentComponent acts as the container for persistent UI elements in Guided Selling OmniScripts.

Placing vlcCart directly under vlcPersistentComponent ensures:
- The cart component renders as a persistent element across steps
- Cart data (items, pricing, totals) is stored in the expected location in the data JSON
- Remote actions such as postCartsItems and getCarts can correctly read from and write to the cart

If the vlcCart is misplaced (for example, placed at the root level or under an incorrect parent), common issues include the cart not appearing, totals showing as 0, or cart state not persisting between steps.

Why the other options are incorrect

A. Check the Show Persistent Cart property for the action that creates it
There is no “Show Persistent Cart” property on actions or remote actions in OmniScripts. Cart persistence is controlled by the OmniScript JSON structure and component placement, not by a checkbox on an action.

B. Specify “vlcPersistentComponent” in the Response JSON Node properly
The Response JSON Node is used to define where a remote action stores its response data. While it can sometimes be set to nodes related to cart data for troubleshooting or totals, it does not control where the vlcCart component itself lives. The vlcCart must still be placed under vlcPersistentComponent in the JSON editor.

D. Check the Render property for the action that creates it
The Render property controls conditional visibility of elements (show or hide based on conditions). It does not affect the data JSON hierarchy or whether the cart persists across OmniScript steps.

Reference
Salesforce Trailhead and Help documentation for Guided Selling OmniScripts explain that persistent cart setup requires configuring the vlcCart component under a persistent parent (vlcPersistentComponent) within the OmniScript JSON structure.