Industries-CPQ-Developer Practice Test Questions

Explanation:

Automated Price Reduction in Salesforce CPQ/Vlocity:
Time Plans: Define scheduled price changes (e.g., "Reduce price by 5% every 3 months").
Rules: Trigger reductions based on the time plan (e.g., IF MonthsSinceLaunch >= 3 THEN Price = Price * 0.95).

Why Option B?

Dynamic Control:
Time plans set the cadence (e.g., monthly/quarterly).
Rules enforce the logic (e.g., percentage drop).

Why Not Other Options?
A (Time Policies): Govern renewals/terminations, not gradual pricing.
C/D (Price Lists/Entries): Require manual updates for each change.

To create a child product with a cardinality of 1, 1, 1

Explanation:

Cardinality in Salesforce CPQ/Vlocity:
Cardinality defines the minimum, default, and maximum quantity of a child product in a bundle.

Setting it to 1, 1, 1 ensures:
Auto-add: The child is added by default (default = 1).
No deletion: Min/max = 1 locks the quantity (users can’t remove or add more).

Why Option A?

Simplest Solution:
No extra rules or flags needed—cardinality handles all requirements.

Reference: Salesforce CPQ Bundle Cardinality

Why Not Other Options?
B (Auto-Add + Requires Rules): Overcomplicates for this use case.
C (Flags): No native "No Delete" flag exists.
D (Context Rule): Used for pricing, not bundle enforcement.

Explanation:

In the Vlocity Product Console (Salesforce Industries CPQ), a layout section is used to group related fields and attributes within a facet. Think of it as a way to organize the user interface for product configuration:
Facets are the tabs or panels (like "General Properties", "Pricing", "Context Rules") that appear on the left side of the Product Console.
Sections are subdivisions within those facets that help structure the layout and improve usability.

This setup allows administrators to:
Create clean, intuitive layouts for product object types
Group attributes logically (e.g., all connectivity options in one section, all pricing variables in another)
Enhance the user experience during product setup and configuration

❌ Why the other options are incorrect:

B. Lightning user interface control: Layout sections are part of the Product Console metadata, not standard Lightning UI components.
C. Container for a Visualforce page: Visualforce isn’t used in layout sections—this is unrelated.
D. WYSIWYG page editor: The Product Console doesn’t offer a drag-and-drop WYSIWYG editor. Layouts are configured through structured metadata.

Explanation:

In Salesforce Industries CPQ:
A Context Dimension is a variable that represents a single piece of contextual data used in rules, such as:

Country
Customer Segment
Sales Channel
Account Type

It does not directly store the data itself but acts as a label or placeholder for the rule logic. During runtime, the dimension’s value is:

Retrieved from a field on an object (via a context mapping)
Calculated dynamically
Defaulted to a static value
Hence, a context dimension:

✅ Stores the value(s) that rules evaluate to determine:

Eligibility
Visibility
Availability
Pricing conditions

So, for the exam question:

In Vlocity Context Rules, what is a context dimension?

✅ The correct definition is:

A. A variable that stores rule condition values.

Why not the others?

B. A link to data stored in sObjects, calculated using a function, or typed in during design time
❌ That describes a context mapping, not a dimension.

C. The relational path from a root sObject, such as an Order, to related sObjects, such as Account
❌ That’s the context scope or relationship path.

D. A multi-dimensional array of sObject data
❌ Incorrect. Dimensions are single-value variables, not arrays.

Explanation:

In Salesforce Industries CPQ, when you want a bundle listed in the Products list of the cart to show a minimum starting price, the system calculates that price based on:

The parent product’s price
Plus the lowest possible combination of child product prices

By making all child products optional, the bundle’s starting price reflects only the parent product’s price, since no child products are required by default. This gives users a clear view of the lowest entry point for the bundle.

This strategy is especially useful for:
Configurable bundles where users can add features based on need
Marketing bundles that advertise “starting at” pricing
Simplifying quoting by showing the base cost upfront

❌ Why the other options don’t achieve this:

B. Change the display text of the parent product Affects labeling, not pricing logic.

C. Change the display text of the child products Again, this is cosmetic and doesn’t influence the displayed price.

D. Adjust the price of the parent product While this sets the base price, it doesn’t prevent required child products from inflating the starting price unless they’re made optional.

Explanation:

In Salesforce Industries CPQ, a time policy defines how a promotion behaves in relation to time-based conditions. Specifically, it determines:

C. The end date: The time policy governs when the promotion expires, ensuring that discounts or offers are no longer applied after a certain date.

D. The purchase date: It also controls whether the promotion is valid based on the date of purchase, allowing you to restrict eligibility to specific time windows.

These aspects are critical for managing seasonal offers, limited-time discounts, and subscription-based promotions.

❌ Why the other options are incorrect:

A. The duration: Duration is typically defined by time plans, not time policies. Time policies influence how time plans behave, but don’t directly set duration.

B. The start date: Start dates are managed by time plans or effectivity settings, not by the time policy itself.

Explanation:

Let’s analyze Felix’s situation:
He already has a Wearable product in the catalog.
The only change in the new version is the available colors.
In Salesforce Industries CPQ (formerly Vlocity):
Attributes like Color are typically defined once on the object type (e.g. Wearable).
Individual products inherit attributes from the object type.

To customize attribute values for a specific product (like different color options), you can:
✅ Override the inherited picklist for that attribute at the product level.

Hence, the best practice is:

✅ Create a new color picklist for the new color set.
✅ Assign that picklist as an override for the Color attribute on the specific new product.

This avoids:
Duplicating attributes unnecessarily.
Creating new object subtypes for minor differences.
Altering existing picklists that affect other products.

Hence, the correct answer is:

✅ A. He should create a new color picklist, and when he creates the new product entry, he can override the attribute picklist that is inherited from its Wearable object type.

Why not the others?

B. He should modify the existing color picklist assigned to the existing Wearable object type.
❌ Incorrect. This would affect all wearable products using that object type—even older versions that still use the old color options.

C. He should create a new Wearable object subtype for the new version of the product, and then link the existing color attribute to a new color picklist.
❌ Overkill. A new subtype isn’t needed just to change color options for one product version.

D. He should create a new color picklist and a new color attribute, and then assign them to the new product when he creates it.
❌ Not necessary. The attribute already exists. He only needs a picklist override, not an entirely new attribute.

Explanation:

In Salesforce Industries CPQ, bundles can be nested, but there’s a limit to how deep the hierarchy can go—typically 2 levels in most standard configurations. The image you provided shows:

Bundle A └── Child A.1    └── Child A.1.2      └── Child A.1.2.1

This structure has 3 levels of nesting, which exceeds the supported depth for rendering in the Cart UI. As a result, only the top-level parent product (Bundle A) appears, and the deeper child products are not displayed.

❌ Why the other options are incorrect:

A. Incorrect Selling Dates: Would prevent specific products from showing, but not all child products across levels.

B. Platform cache not refreshed: Might delay updates but wouldn’t block visibility of properly configured products.

D. Mixed pricing types: Doesn’t affect product visibility—only pricing calculations.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity):
Contract discounts are specifically designed to handle:

Negotiated pricing
Frame agreements
Pre-agreed discounts for specific customers or deals

A Contract discount allows:
✅ The creation of an agreement between:

A customer account
The service provider
→ specifying unique pricing conditions (e.g. discounts, special rates) to be automatically applied to:

Quotes
Orders
Billing

This type of discount is perfect for:

Large enterprise customers
B2B agreements
Government contracts

Hence, if you want to apply negotiated discounts via frame/pricing agreements to customer orders, the correct answer is:

✅ A. Contract

Why not the others?

B. Order
Refers to order-specific discounts applied ad hoc, not tied to negotiated contracts.

C. Group
Usually applies to discounts for:
Groups of products
Product bundles
Not negotiated customer-specific agreements.

D. Account
While discounts can be linked to an account, Contract discounts are the specific mechanism for formal agreements.

Explanation:

In Salesforce Industries CPQ, when launching a product like Smart Widget exclusively for existing B2B customers and targeting opportunities, the correct context scope for context mapping is Opportunity.Account.

This scope allows Felix to:

Access account-level data (e.g., customer type, status)
While still anchoring the rule to the Opportunity object, which is the root of the transaction
Apply qualification rules that filter product visibility based on account attributes tied to the opportunity
This is ideal for soft launches, targeted promotions, or account-based eligibility during quoting.

❌ Why the other options fall short:

B. Opportunity: Doesn’t give access to account-level data needed to identify B2B customers.
C. Order.Account: Irrelevant here—Felix is working with opportunities, not orders.
D. Account: Too broad and disconnected from the opportunity context needed for this launch.