Explanation:

In Salesforce Industries CPQ (Vlocity), the cardinality settings of a promotion’s child product define quantity and inclusion rules within the product structure.

✅ A. Minimum quantity
The minimum number of units the user must select for the child product.
Example: Customer must buy at least 1 modem when choosing an internet bundle.

✅ B. Maximum quantity
The maximum number of units the user is allowed to purchase.
Example: A promotion may limit users to buy no more than 2 extra devices.

✅ D. Optionality
Defined via the "Required" setting:
If checked, the product is mandatory (not optional)
If unchecked, the child product is optional
This is often used for upsell or add-on components.

❌ C. Whether the price of the product rolls up into the total for the promotion
This is not controlled by cardinality.
Price roll-up behavior is managed through:
Pricing element configuration
Bundle pricing settings
Promotional pricing rules

Explanation:

In Salesforce Industries CPQ (Vlocity Cart), the Attribute Category Name is the field that appears as a heading during run-time configuration and filtering in the Cart UI. This helps organize product attributes into logical sections for easier navigation and selection.

✅ Why Name is correct:
The Name field of the Attribute Category is used as the label shown in the Cart’s Filter and Configuration windows.
It helps users identify and group related attributes (e.g., “Connectivity”, “Color”, “Wearables”).

❌ Why the other options are incorrect:
B. Display Name: This field is used for internal or design-time purposes and does not appear at run-time.
C. Category: This is not a standard field used for display in the Cart UI.
D. No fields are displayed at run-time: Incorrect — the Name field is explicitly shown as a heading.

Explanation:

The Collapse Hierarchy flag in Salesforce Industries CPQ (Vlocity EPC) is used to optimize performance when dealing with large and deeply nested product bundles. When enabled, it reduces the amount of hierarchical data passed during Cart operations by flattening the product structure.

✅ Why B is correct:
It collapses the hierarchy of product relationships into simplified key-value pairs.
This reduces payload size and improves Cart rendering and API response times, especially for bundles with multiple levels of nesting.
It’s particularly useful in Digital Commerce scenarios where performance is critical.

❌ Why the other options are incorrect:

A. Enables a Search Item dialog... → This is unrelated to the Collapse Hierarchy flag. Search dialogs are controlled by UI settings and Cart configuration.

C. Allows the product to inherit the parent product's cardinality → Cardinality inheritance is managed via object types and product relationships, not the Collapse Hierarchy flag.

D. Restricts the product from retrieving cardinality settings from any linked object types → Again, cardinality logic is governed by object type configuration, not this flag.

Explanation:

This scenario describes a loyalty or retention strategy where the CSR offers Sarah a recurring discount tied to her account for future billing cycles. That aligns with the definition of an Account-Based Discount in Salesforce Industries CPQ.

✅ Account-Based Discount
Applied directly to the customer’s account record
Automatically affects future orders or quotes associated with that account
Typically used for retention, negotiated pricing, or VIP customer programs
Valid for a defined period (e.g., 12 months in Sarah’s case)

📌 Example: Sarah’s account now carries a 20% discount on monthly charges for the next year. Any new quote or order linked to her account will inherit this discount automatically.

❌ Why the other options are incorrect:
A. Order-Based: This applies a one-time discount to a specific order or quote. Sarah’s discount is ongoing.
C. Contract-Based: This is tied to a formal contract or frame agreement. Sarah’s discount was offered informally by the CSR and not through a negotiated contract.

Explanation:

In Salesforce Industries (Vlocity) CPQ, the Digital Commerce API caches product data (including prices) for performance. If updates aren’t reflected:

Regenerate Cached API Records forces a cache rebuild with the latest data.
This ensures the API returns updated prices (e.g., after a price list change).

Why Other Options Are Incorrect?

A. Populate API Cache → Initializes cache but doesn’t force updates.
B. Migrate Cache Records → Moves cache data between orgs, irrelevant here.
C. Delete Expired Cache → Removes stale entries but doesn’t refresh active ones.