Industries-CPQ-Developer Practice Test Questions

Explanation:

In Vlocity Context Rules (Salesforce Industries Context Rules), a Context Dimension is used to define criteria such as customer type, location, or segment.

A Vlocity picklist can be linked to a Context Dimension, allowing you to dynamically determine values from predefined picklist options and use them to evaluate rules.

Analysis of options

A. Context Dimension → Correct. This is the component specifically designed to be linked to picklists to drive dynamic context-based logic.

B. Context Mapping → Incorrect. Context Mapping is used to map object fields to context dimensions, but it is not directly linked to picklists.

C. Context Scope → Incorrect. Context Scope defines which fields or objects are included when retrieving context, but it is not linked to picklists.

D. Context Rule Set → Incorrect. A Context Rule Set groups multiple rules but does not directly connect to picklists.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), when you assign a new attribute to an Object Type (for example, Device, Plan, Service), that attribute is not automatically or dynamically propagated to all products linked to it.

Instead, you must explicitly run the Attribute Hierarchy Maintenance job in the CMT Administration screen.

This job will:

Copy the newly assigned attribute down to all products that reference that Object Type.
Ensure that the products' attribute JSON field is updated accordingly.

Analysis of options:

A. Dynamically through inheritance
→ Incorrect. The system does not support real-time dynamic inheritance for attributes; explicit maintenance jobs are required.

B. By running the EPCProductAttribBatchJob to regenerate the product attribute JSON field
→ Incorrect. EPCProductAttribBatchJob is not used for this purpose; it's more related to attribute JSON regeneration after price list changes.

C. Via a deep copy to Product2
→ Incorrect. No deep copy is automatically made to Product2 in this context.

✅ D. By running the Attribute Hierarchy Maintenance job on the CMT Administration screen
→ Correct. This is the standard and documented process.

Explanation:

In Salesforce Industries (Vlocity) Guided Selling, the persistent cart is a specialized implementation of the Vlocity Cart designed to save and retrieve cart data across sessions. Here’s why:

Persistent Cart = Vlocity Cart (Correct Answer - A)

The persistent cart is built on the Vlocity Cart framework, which stores quote/order data in a structured format.
It retains cart items, configurations, and pricing even after a user logs out or returns later.
This is not a lightweight component (B) but a core feature of the Vlocity platform.

Why Not the Other Options?

B) Lightweight OmniScript component → The persistent cart is not just a UI component; it’s backed by server-side cart logic.

C) Designed for novice users / D) Designed for power users → The cart’s persistence benefits all users, regardless of expertise.

Explanation:

After creating a new product in the Vlocity Product Console, especially one with no child products, Felix must ensure that the system properly reflects the product in both the hierarchy and pricing engines.

This involves running two administrative jobs in sequence:

Step 1:

- Run the Product Hierarchy Maintenance job
- This updates the internal product hierarchy.
- Ensures the product is correctly structured and visible in the catalog.

Step 2:

- Run the Refresh Pricebook job
- Recalculates and regenerates pricebook entries.
- Makes the product available for pricing and selection in CPQ flows.

Why not the others:
A. No additional steps are needed – This is incorrect because the system does not automatically update the hierarchy or pricing.
B. Running Refresh Pricebook before Product Hierarchy Maintenance – This can cause pricebook data to be inaccurate due to missing hierarchy updates.
D. Clearing platform cache and then running Refresh Product Hierarchy Maintenance – Cache clearing is not required, and "Refresh Product Hierarchy Maintenance" is not a standard job name.

True

Explanation:

In Salesforce Industries CPQ (Vlocity), a picklist name is a developer/designer-facing identifier used only at design-time.

It is used when configuring context dimensions, defining attribute value sets, and linking picklists to context rules.

At run-time, customers only see the picklist values (labels), not the internal picklist name.

This means the picklist name helps identify or reference the picklist in configuration but is not exposed to end users during run-time experiences.

Analysis of options

A. True → Correct. The picklist name is only used at design-time and not shown to customers.
B. False → Incorrect. The picklist name is not visible at run-time.

Explanation:

Child Price Lists in Salesforce CPQ are used to override or extend pricing from a parent price list under specific conditions. Here’s when they are most useful:

A) Different Regions (Geographic Pricing)

If a product has region-specific pricing (e.g., higher prices in Europe, lower in Asia), a child price list can apply those adjustments without modifying the parent price list.

D) Customer-Specific Pricing (Context Rules)

Child price lists can be linked to context rules (e.g., customer segment, contract type) to offer custom pricing for specific buyers.

Example: A VIP customer gets a 10% discount via a child price list.

Why Not the Other Options?

B) Changing parent product pricing in a bundle → Parent product pricing is controlled by the main price list, not child price lists.

C) Changing child product pricing in bundles → Bundle pricing is usually handled via Product Rules or Discount Schedules, not child price lists.

Explanation:

While the Vlocity Product Console allows you to manage product-related discounts, discounts in Salesforce CPQ/Vlocity can be created and managed in multiple ways:

Discount Schedules - Created in CPQ settings to apply tiered or volume-based discounts
Price Rules - Can be configured to apply automatic discounts based on conditions
Quote Line Editor - Allows manual application of discounts during quoting
OmniScripts - Can include discount logic in guided selling flows

Why Not True?

The Product Console is just one of several places where discounts can be configured. The statement is too absolute.

To contain one or more context rules in a set that can be assigned to products,
promotions or price list entries

Explanation:

In Vlocity Context Rules (Salesforce Industries CPQ), a rule set is used to group one or more context rules together.

This allows you to assign them as a single set to products, promotions, or price list entries.
When the rule set is assigned, all its context rules are evaluated to determine if the product or promotion should be available, visible, or applicable to a given scenario.

Analysis of options:

A. Correct. Rule sets are designed to group context rules and assign them to commercial entities.
B. Incorrect. You cannot combine Advanced Rules and Context Rules into the same set.
C. Incorrect. Rule sets do not define cardinality for rule processing.
D. Partially true but incomplete. The main purpose is not just to organize but to enable assignment and evaluation together at runtime.

Explanation:

In Vlocity Cart (Salesforce Industries CPQ Cart), when a product has a default quantity cardinality of 0, it means:

The product is optional, not auto-included.
It is visible in the cart, but not pre-selected or pre-added.

How it appears to the user:

It shows up as a line item in the cart interface.
Instead of a quantity field (since it’s initially 0), the user sees an Add to Cart button, allowing them to explicitly add the product if they want.

Analysis of options:

✅ A. As a line item with an Add to Cart button
→ Correct. This is exactly how products with a default quantity of 0 are represented.

B. In a yellow font as a Recommended Product
→ Incorrect. This is not the standard visual indicator.

C. As a line item with a quantity of 0
→ Incorrect. It does not show an actual "0" quantity; it shows an add button.

D. As an available product in the Search Item dialog
→ Incorrect. The product may also be available in search, but this is not how it is primarily presented in the cart.

Explanation:

To price the same product differently for B2B and B2C customers, the most effective method is to use separate price lists.

- Create a price list for B2B customers with the smartphone priced at $999.
- Create a price list for B2C customers with the smartphone priced at $900.

Use context rules to qualify which price list applies based on the customer's segment.
This ensures dynamic pricing, product reuse, and efficient catalog management.

Why not the others:

A. Assigning two pricebook entries – Relevant for core Salesforce CPQ, not Industries CPQ.
B. Bundles with pricing overrides – Overrides are better suited for specific configuration scenarios, not segment-level pricing.
C. Creating two versions of the product – Leads to unnecessary duplication and maintenance overhead.