Explanation:

In Salesforce Industries CPQ promotions, you can change the price of a child product using two mechanisms:

Pricing Element Adjustment (B) → Applies a calculation to the base price (e.g., percentage discount, fixed discount, or markup). This is the standard way to reduce or increase the child product’s price within a promotion.

Pricing Element Override (C) → Replaces the base price with a new fixed value. This is useful when the promotion sets a specific promotional price for the child product, regardless of its original base price.

Why the other options are incorrect:
A. MACD → Refers to Modify/Add/Change/Disconnect actions in asset-based ordering, not pricing.
D. New order → Refers to order type, not pricing.
E. Different price list → Defines base prices but does not directly apply promotional changes.
F. Pricing element charge → Adds fees or surcharges, not discounts.

Reference:
Salesforce Industries CPQ Pricing Guide – Pricing Adjustments and Overrides (Salesforce Help: Industries CPQ Pricing Elements)

Explanation:

Why "False" is Correct
The Context Rules framework is composed of several distinct functional areas and interfaces that work together. It does not use a "single" interface because the administrative tasks are separated from the logic definitions:

Rule Sets & Rule Builders: There is an interface for defining the logic (the "Rule Builder" within a Rule Set) where you combine conditions.

Context Scopes & Mappings: This is a separate administrative area where you define the data source (e.g., Account, Order, or Quote) and map fields to "Context Dimensions."

Product/Promotion Console: You use the standard Vlocity Product Console or the Related Lists on a Product record to assign the rules.

Service/API Layer: The runtime execution happens via a specific set of Digital Interaction API services that the Cart calls.

Because an administrator must move between the Context Lookups, Context Dimensions, Context Scopes, and finally the Rule Sets, the framework is considered a multi-part system rather than a single-interface operation.

Why "True" is Incorrect
If the framework used a single interface, you would be able to define the data mapping, the logic, and the product assignment all on one screen. In Vlocity, these are decoupled to allow for reusability. For example, a "Context Dimension" defined in one interface can be reused across hundreds of different rules in another.

References
Salesforce Help: Context Rules Framework Components
Vlocity Documentation: Refer to the CME CPQ Rules Guide which outlines the distinct steps of creating Dimensions, Scopes, and Rule Sets.
Trailhead: Create Context Rules for Industries CPQ

Explanation:

In Salesforce Industries (Vlocity) CPQ, a product attribute must be associated with an Object Type.
The object type defines where and how the attribute is used (for example: Product, Asset, Order Item).

Because of this dependency:
👉 You must create the object type before creating a product attribute

Without an object type, the system has no context for the attribute, and attribute creation is not possible.

Why the other options are incorrect
A. Create the product ❌
Attributes are defined independently of specific products
Products reference attributes later via attribute assignments

C. Create an attribute category ❌
Categories are used for grouping and UI organization
They are optional and not a prerequisite

D. Create the picklist ❌
Picklists are only needed if the attribute is a picklist type
Not all attributes require picklists

Key Exam Tip 🧠
For attribute-related setup questions, remember this order:
Object Type
Attribute
Attribute Category (optional)
Picklist (optional)
Assign attribute to product

If the question asks “what must exist first?”, the answer is almost always Object Type.

Explanation:

Why "A" is Correct
A Pricing Element Adjustment is the standard tool used within a Promotion to lower a price.

The Logic: An adjustment applies a mathematical change—either a percentage (e.g., -20%) or a flat amount (e.g., -$10)—to the product's original price.

Separation of Concerns: By using an adjustment, the original Base Price remains intact for customers who are not using the promotion. The adjustment is only applied when the specific promotion criteria are met in the Cart.

Why Incorrect Answers are Wrong
B. Edit the base price:
Changing the base price is a permanent change to the product's fundamental cost. This would affect all customers, not just those eligible for a specific promotion.
C. Add another price list entry:
While you can have different prices on different price lists, this is used for segment-based pricing (e.g., Wholesale vs. Retail) rather than a targeted promotion.
D. Create a rule:
While rules (like Context Rules) can trigger pricing changes, they are the "engine" that decides when a price change happens. The actual "payload" or mechanism that decreases the price is still the Pricing Element Adjustment.
E. Use a pricing variable:
A pricing variable (like REC_MNTHLY_CHRG) is a container that tells the system which part of the price is being affected, but it doesn't define the decrease itself.
F. Use a pricing element charge:
A "Charge" is typically used to add a cost (like a setup fee) rather than subtract from one, though some charges can be negative, "Adjustment" is the specific terminology used for promotional discounts.

References
Salesforce Help: Defining Promotion Pricing
Vlocity Documentation: Refer to the CME EPC Guide under Promotion Items, which explains how Adjustments and Overrides are applied to child products.
Trailhead: Manage Promotions in Industries CPQ

Explanation:

In Salesforce Industries CPQ, when defining Context Rules, the Entity Path specifies the relationship path from the source object to the object containing the data you want to evaluate.

Root Scope: The "Root" is the starting point of the evaluation (e.g., the Quote, Order, or Asset itself). Since the engine is already "at" the root, there is no relationship path to traverse.

Implementation: When you configure a Context Scope as a Root Scope, the Entity Path field is left blank because the data being evaluated resides directly on the primary object being processed in the Cart.

Why this matters
If you were evaluating data on the Account related to a Quote, the Entity Path would be Quote.AccountId.
For the Quote itself (the Root), no path is needed.

References:
You can find technical details on scope configuration in the Salesforce Help: Context Scopes documentation.