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.

Explanation:

Attribute-Based Pricing (ABP) calculates a price based on specific configuration choices, or attributes, selected by the user. For this to work correctly within the Pricing Plan, the custom step must be placed at the correct sequence.

Initialization Requirement
Before a price can be calculated based on attributes, the system must first know which pricing variables, such as Recurring and One-Time charges, are available.
This initialization occurs at Sequence 30.

Logical Slot
Placing the custom step after Sequence 30 allows the Attribute-Based Pricing service to take the Base Price, which is loaded at Sequence 20, and modify it using attribute matrix logic.

Downstream Effects
The step must occur before Sequence 40, because Sequence 40 applies Offer Adjustments such as promotions or manual discounts.
Adjustments and discounts should be calculated on the attribute-adjusted price rather than on the original base price.

Analysis of Incorrect Answers
A. Before Sequence 10
This is not possible because Sequence 10 initializes the pricing context.
Without this context, the pricing engine does not know which Account or Order it is processing.

B. Between Sequence 10 and 20
At this stage, Price List Entries have not yet been loaded.
You cannot modify a price that has not been retrieved from the database.

D. After Sequence 90
This occurs too late in the pricing flow.
By Sequence 90, parent variables have already been applied and most pricing calculations are complete, so applying attribute-based pricing at this point would result in incorrect totals or adjustments and taxes being calculated on the wrong base amount.

References
Salesforce Help: Pricing Plan Steps and Sequencing
Vlocity Documentation: Implementing Attribute-Based Pricing

Explanation:

In Salesforce Industries CPQ (Vlocity CPQ), the Cart UI renders based on basket data, not directly on the add-to-cart action itself.
When a user adds products to the Cart and nothing renders, the key question is:
Is the Cart able to retrieve and display the basket data after the add operation?

That rendering depends on the basket retrieval call, which is:
👉 getBasketDetails
This method returns:
- The basket (cart) structure
- Line items
- Pricing, attributes, and relationships needed by the Cart UI

If getBasketDetails:
❌ is not called
❌ returns an error
❌ returns an empty or malformed response
…the Cart will appear empty even if products were technically added.

Why the other options are incorrect

A. postCartsItems
❌ Used to add items to the cart, not to render or retrieve cart contents.
B. createCart
❌ Only creates a new cart/basket. Rendering issues occur after the cart exists.
D. getCartsItems
❌ Not the primary API used by Industries CPQ for Cart rendering. The Cart UI relies on the full basket model, not just item lists.

Exam Tip 📝
For UI not rendering / empty cart / pricing not showing issues in Industries CPQ:
Always start troubleshooting with getBasketDetails in the Network tab.
That’s the single most important call for Cart display.

Explanation:

Correct Option ✅: A. createCart method
The createCart method is required to initialize a shopping cart session before products or configurations can be added. Without this method, no cart context exists, making it impossible for Guided Selling to function. It ensures that subsequent operations such as price association and product selection are tied to a valid cart instance.

Correct Option ✅: B. Associating the cart with a valid price list or price book
Every cart must be tied to a valid price list or price book so the system knows which prices to apply for selected products. Guided Selling relies on this association to correctly calculate and display pricing in the cart. Without it, products may appear but won’t have valid pricing data.

Correct Option ✅: C. HTML Template for horizontal or vertical mode
The Guided Selling cart requires a rendering layer that defines how products and categories are displayed. HTML templates in either horizontal or vertical mode provide this structure. They enable a user-friendly, step-by-step selling experience that’s consistent across the cart. Without this, the cart cannot visually present options to the user.

Correct Option ✅: D. Associating the cart with a valid account
A cart must be linked to an account so billing, entitlements, and applicable product offerings can be validated. Guided Selling uses account associations to determine eligibility rules, discounts, and valid configurations. If no account is associated, the cart cannot be processed in a real-world business context.

Incorrect Option ❌: E. Associating the cart with valid user profiles
While user profiles control overall system access, they are not specifically required for building a Guided Selling cart. The cart relies on account and price list associations instead. Linking to user profiles is a broader Salesforce security feature, not a direct Guided Selling configuration step.

Incorrect Option ❌: F. Multiple price lists for filtering product categories
Guided Selling does not require multiple price lists. In fact, a single valid price list per cart is sufficient. Filtering of products and categories happens through rules, attributes, and catalog configuration rather than multiple price lists. Multiple price lists could cause conflicts in pricing logic.

Incorrect Option ❌: G. Linking getCartItems to the template
The getCartItems API is not the required method in Salesforce Industries CPQ; the system uses getBasketDetails for retrieving cart contents. Linking getCartItems would be ineffective since it is not a supported or recognized call. This makes the option invalid for Guided Selling cart construction.

Summary 📝
To build a Guided Selling cart, you must establish a cart session using the createCart method, associate it with both a valid price list and a valid account, and provide an HTML template to control how the selling flow appears. Other options like user profiles, multiple price lists, or unsupported API calls are not necessary. These four requirements create the foundation for a functioning Guided Selling cart in Salesforce Industries CPQ.

Reference 🔗
Salesforce Help: Guided Selling and Cart APIs

Explanation:
Entity Filters are reusable, independent objects in Salesforce Industries CPQ and are not tied to a single Advanced Rule.

B is Correct (False):
An Entity Filter defines a set of conditions (e.g., Product Family = 'Mobile' AND Market = 'US'). This filter can be saved as a standalone, named filter and then referenced by multiple different Advanced Rules (such as Pricing Rules, Discount Rules, or actions within Promotion Rules). This reusability is a key design feature for maintainability and consistency.

Why A is Incorrect:
If Entity Filters were tied to a single rule, administrators would have to recreate the same logical conditions repeatedly across different rules, leading to redundancy, inconsistency, and a maintenance burden.

How it Works:
An administrator creates an Entity Filter (e.g., "US Mobile Phones").

They can then apply that same filter to:
- A Pricing Rule to adjust prices for US mobile phones.
- A Discount Rule to apply a special discount to US mobile phones.
- An Action within a Promotion Rule that adds a free accessory to US mobile phones.

Reference:
Salesforce Industries CPQ Documentation: "Use Entity Filters." The documentation explains that Entity Filters are "reusable filters" that you can "apply to multiple rules," clearly indicating they are standalone components not limited to a single rule.