Explanation:

When viewing the Orders tab in Salesforce Industries (formerly Vlocity), the default statuses typically displayed are:

C. Salesforce Status –
This reflects the standard Salesforce object status field such as Draft, Activated, or Completed.

D. Salesforce Industries Order Status–
This is a more granular, Industries-specific status (e.g., In Progress, Pending, Failed, Completed) that reflects where the order is in the CPQ or OM lifecycle.

Why not the others?

A. State of tasks within an Orchestration Plan –
This level of detail is part of orchestration monitoring, not visible by default on the main Orders tab.

B. State of the Orchestration Plan itself –
Like task state, this is visible in orchestration-specific views, not typically on the Orders tab.

E. PONR Status (Point of No Return) –
This is a lifecycle checkpoint for order orchestration but is not a default column or filter in the Orders tab.

Explanation:

Correct Option: 🟢 B. Discounting the price by 20%
Discounting the price by 20% requires a calculation that uses the product's original price. For example, if a product costs $100, a 20% discount is calculated as $100 × 0.20 = $20, resulting in a new price of $100 - $20 = $80. This process directly relies on the original price to determine the discounted amount, a common feature in Salesforce Industries CPQ pricing rules.

Incorrect Option: 🔵 A. Completely overriding the price
Completely overriding the price does not require a calculation using the product's original price. Instead, it involves setting a new price manually or through a predefined value, disregarding the original price entirely. For instance, in Salesforce Industries CPQ, a price override replaces the base price without performing any calculation based on it, making this option incorrect.

Summary:
This question assesses understanding of pricing mechanisms in Salesforce Industries CPQ, specifically how different pricing actions interact with a product’s base price. Discounting inherently involves a calculation using the original price to determine the reduction, while overriding replaces it without computation. Knowing these distinctions is crucial for configuring accurate pricing rules in CPQ for telecom or other industries.

Reference:
Salesforce Industries CPQ Documentation

Explanation:

When a child product in a promotion has a discounted price, the explanation shown in the cart or UI comes from the:**

Display text set on the price adjustment or price override associated with that child product.

This display text communicates why a price has changed — for example, "Promo Discount" or "Special Offer Applied".

Why the others are incorrect:
A. Time policy display text relates to time-based pricing, not directly to promotions.
B. Base price display text shows standard pricing, not adjusted/discounted pricing.
D. Promotion description might appear elsewhere (e.g., marketing UI), but not directly tied to price explanation.
E. Promotion code is used for identification or entry, not explanation.

Explanation:

Vlocity Product Attributes are a key part of product modeling in Salesforce Industries CPQ (Vlocity).

These attributes are primarily managed through the Vlocity Product Console, which is the recommended and modern interface designed specifically for managing complex products, attributes, and relationships.

The Aloha interface (the classic Salesforce UI) does not fully support managing Vlocity product attributes in the same flexible and robust way. It lacks certain features, validations, and UI capabilities required for complex attribute configurations.

Why False?

The Product Console provides specialized tools such as:

Attribute setup wizards
Dependency rules configuration
Guided workflows for complex offerings

The Aloha interface is not intended for this level of product attribute management and does not allow full interchangeability.

Explanation:

Let’s look at the scenario:

You want to take 20% off the price of a child product in a promotion.
This means you’re discounting the price relative to the product’s normal price.

✅ A. An adjustment → Correct
✅ In Industries CPQ, an adjustment is the correct tool for:
Applying discounts (percentage or fixed amount)
Increasing or decreasing prices
Adding surcharges

Adjustments can be defined as:
Percentage-based → e.g. “-20%”
Fixed amount → e.g. “-$5”
For your scenario:
Apply a -20% adjustment to the child product’s price inside the promotion configuration.

This ensures:
The base price remains stored in the system.
The system tracks the discount as a separate pricing element.

Example configuration:
Adjustment Type: Percentage
Adjustment Value: -20%

Why the Other Options Are Incorrect
✅ B. An override → Incorrect
An override completely replaces the original price with a new fixed value.
For example:
“Set the child product’s price to exactly $50.”
You don’t want to replace the price; you want to discount it by 20%.

✅ C. A price list → Incorrect
The price list defines:
Which products exist in a catalog
The base price of each product
You wouldn’t use the price list directly to apply a promotional discount.

✅ D. A price list entry → Incorrect
A price list entry:
Stores the base price for a product
It’s where the base price lives—but discounts should be handled separately as adjustments.
Overwriting the price in a price list entry would remove visibility into the discount mechanics.