Explanation:

In Salesforce Industries Order Management (OM), when an order is canceled, the system automatically creates a supplemental order to handle the reversal or corrective actions required for fulfillment and downstream systems.

👉 This supplemental order is created automatically by OM, not manually by CPQ or a user.

Why this happens:
Cancellation may occur after fulfillment has started
OM must generate a supplemental order to:
- Reverse provisioning steps
- De-activate services
- Sync changes with external fulfillment or billing systems

This behavior is part of Industries OM orchestration logic.

Why the other options are incorrect
A. The same way any other order is created ❌
Supplemental orders are system-generated, not user-created

B. Similar to any other New Order, but Order Type = “Supplemental” ❌
Users do not manually set the Order Type to create supplemental orders
This is a common exam trap

C. Automatically by CPQ when an order is canceled ❌
CPQ handles pricing and order capture
Order Management, not CPQ, controls cancellation and orchestration behavior

Key Exam Tip 🧠
For supplemental orders, remember this rule:
CPQ captures orders → OM manages fulfillment and cancellation

So:
Cancellation logic → Order Management
Supplemental order creation → Automatic

If the question mentions order cancellation, reversal, or supplemental order → the answer is OM does it automatically.

Explanation:

In Salesforce Industries CPQ, when you want to create a bundle where specific child products are discounted (e.g., 20% off a child accessory or service when the bundle is added), you configure the discount directly in the promotion that targets the bundle.

The exact place to set discounts on individual child products is in the Product Structure section of the promotion (also called the Promotion Products or Child Product Adjustments area).

Steps:
- Create or edit a Promotion record.
- In the Promotion Designer, go to Product Structure (or Promotion Applies To → select the bundle parent product).
- Expand the child products under the bundle.
- For each child product you want to discount, add a Pricing Adjustment (percentage or amount off) or Pricing Override (fixed price) directly on that child line.
- Save → when the bundle is added to the cart and the promotion applies, the child products will show the discounted prices.

This is the declarative, reusable way to discount child products within a bundle via a promotion.

Why the other options are incorrect:
A. The price list where the price list entry is located:
Price Lists define the base price (list price) of products — not promotional discounts. You do not discount child products in a promotion by editing the price list.
C. The cart currently open:
In the cart you can manually apply discounts (e.g., manual adjustment on a line item), but this is not how you configure a reusable bundle promotion that automatically discounts child products when the bundle is added. Cart-level changes are one-off, not part of the bundle/promotion definition.
D. The cart currently open:
Same as C (likely a duplicate option in the test).

Reference
Trailhead: "Build a Promotion" and "Adjust the Pricing of Child Products" units — Explicitly show going into the product structure of the bundle inside the promotion to add adjustments/overrides on child products.
Salesforce Help: "Promotion Product Structure" — "In the product structure section of a promotion, you can define pricing adjustments and overrides for child products in the bundle."

Explanation:

In the standard Vlocity Cart interface, the primary user-friendly method to modify a product's configuration (e.g., change attribute values like color, storage size) after it has been added to the cart is via the line item's action menu.

B is Correct:
Typically, each line item in the cart has an "Actions" dropdown menu (often represented by an ellipsis ... or a "More" link). Within this menu, there is an option labeled "Configure" or "Reconfigure." Selecting this action opens a configuration modal or navigates to a configuration step, allowing the user to modify the product's attributes and update the line item in the cart.

Why the other options are incorrect or not standard:
A. Delete and re-add the product: While this would technically achieve a new configuration, it is inefficient and not the intended user workflow. The "Configure" action is designed specifically for in-place modification.
C. Update the product's attribute in Vlocity Product Console: The Product Console is an administrative tool for defining product templates and attributes, not for changing the configuration of a specific line item in a user's active cart.
D. Invoke Field Mapper: A Field Mapper is a DataRaptor tool used for data transformation in integrations or OmniScripts. It is not a user-facing feature for reconfiguring cart items.

Standard User Flow:
- Product is added to cart with initial configuration.
- User reviews cart and wants to change an option.
- User clicks the "..." menu on the line item and selects "Configure."
- A configuration window opens, user makes changes and saves.
- The cart updates the line item with the new configuration and recalculates pricing.

Reference:
Salesforce Industries (Vlocity) User Guide: "Modify Items in the Cart." The standard cart user experience includes a Configure/Reconfigure action in the line item menu for this exact purpose. This is a core feature of the vlcCart component.

Explanation:

A Sales Catalog (often referred to as a Product Catalog in Vlocity CPQ) is a customer-facing grouping used to control which offers are visible and available to specific customers or channels during the sales process.

B. Correct:
A Sales Catalog defines a curated set of sellable products and active promotions that are presented to a particular market, customer segment, or sales channel. It is the storefront or menu from which customers or sales reps can select items.

Why the other options are incorrect:
A. A catalog of prices: This describes a Price List. Price Lists define the pricing for products, while Catalogs define the visibility and assortment.
C. A catalog of technical and commercial products: This describes the Shared Catalog (in CME), which is the master repository of all product definitions. The Sales Catalog is a subset or view of the Shared Catalog, tailored for sales.
D. A set of products that are related through Relies On dependencies: "Relies On" dependencies are a type of product relationship (like Requires, Recommends) defined in Product Rules. This is not the definition of a catalog.

Key Concept:
Shared Catalog (EPC): The single source of truth for all product definitions (both commercial and technical).
Sales Catalog: A filtered, commercial subset of the Shared Catalog, used for a specific sales context, often including promotions.

Reference:
Salesforce Industries CPQ Documentation: "About Product Catalogs." The documentation states that a Product Catalog is "a collection of products and promotions that you make available to customers or sales agents." It is used to control offer visibility.

Explanation:

In Salesforce Industries (Vlocity) Context Rules, a rule set does NOT have to contain more than one rule.

👉 A rule set can contain a single rule or multiple rules.

Rule sets are simply containers used to:
- Group related rules
- Control evaluation order
- Assign rules to products, promotions, or contexts

There is no minimum number of rules required.

Why A. True is incorrect ❌
Saying “True” would imply:
- A rule set must always have at least two rules
- Single-rule scenarios are invalid

This is incorrect and contradicts how Context Rules are designed and used in real implementations.

Key Exam Tip 🧠
For Context Rules structure questions:
- Rule = individual condition + action
- Rule Set = container
- Minimum rules per rule set = 1

If the question says “must contain more than one,” that’s your cue to answer False.