Industries-CPQ-Developer Practice Test Questions

Explanation:

In Salesforce Industries CPQ, when configuring Product Rules or Price Rules that use Advanced Rules with entity filters, you often need to evaluate Product Attribute values to determine if a rule should be triggered.

Entity Filter Context:
Entity filters allow you to filter records based on related entities (like Product, Quote, Account) and their fields or attributes.

Evaluating Product Attributes:
Product Attributes are custom fields on the Product object. To evaluate them in an entity filter, you must specify how the attribute value should be evaluated.

Role of "Evaluation Criteria":
This field on the Entity Filter record defines the logic or criteria used to evaluate the attribute value. It essentially tells the rule engine, "How do I want to assess this attribute?" Examples include:
Equals
Not Equal To
Greater Than
Is Null
Contains

Without setting the Evaluation Criteria, the system does not know what condition the attribute value must satisfy for the filter to pass.

Why the Other Options Are Incorrect:

A. Entity Filter Type
This defines what type of entity you are filtering on (e.g., Product, Quote Line, Asset). While necessary for setting up the filter's scope, it does not define how an attribute's value is evaluated.

C. Formula for Conditions
This is used for more complex logic where you might write a Salesforce Formula (similar to a validation rule formula) to evaluate a condition. While powerful, it is not the required field specifically for evaluating a product attribute value on a standard entity filter. The basic entity filter uses the Evaluation Criteria field for the operator.

D. Attribute Lookup Field Name
This refers to the field that holds the attribute value you want to evaluate (e.g., a field API name). This is certainly required to identify which attribute to evaluate, but it alone is insufficient. You must also set the Evaluation Criteria to define the condition (e.g., equals, not null).

Reference:

In the Entity Filter configuration in Salesforce CPQ Advanced Rules, the key fields are:
Field: The attribute or field to evaluate (e.g., Product__r.My_Attribute__c).
Evaluation Criteria: The operator (e.g., Equals, Not Equal To).
Filter Value: The value to compare against.

The Evaluation Criteria is a mandatory component to define the condition's logic when evaluating any field or attribute value.

Conclusion:
To evaluate a product attribute value, you must specify the condition logic via the Evaluation Criteria on the Entity Filter. Therefore, the correct answer is B. Evaluation Criteria.

Explanation:

Promotions are used in Salesforce Industries CPQ to deliver targeted, time-limited, or segment-specific incentives such as special pricing, discounts, or restricted eligibility. They are ideal for conditional and temporary offers rather than permanent product rules or penalties.

Appropriate Use Cases

B. The product's price should change based on the customer type
Promotions support segment-based pricing (e.g., different prices for B2C vs. B2B or enterprise vs. SMB) using eligibility or context rules tied to Account attributes.

C. The product should only be available to B2C customers
Promotions can restrict eligibility or visibility to specific segments (e.g., B2C only) through rules that evaluate Account Type, Record Type, or custom fields.

E. Special pricing should only be available for a limited time
Promotions include built-in Start Date and End Date fields, making them perfect for temporary offers like flash sales, seasonal discounts, or promotional campaigns.

Why the Others Are Not Appropriate

A. Cancellation penalties
Cancellation penalties are managed via Pricing Rules, Pricing Adjustments, or contract logic — not Promotions.

D. “Sell quickly”
This is a business or marketing goal, not a configuration use case handled by Promotions.

References

Salesforce Trailhead:
Learn About Promotions and Discounts in CPQ — Covers time-bound offers and customer-segment targeting

Salesforce Trailhead:
Industries CPQ Promotions — Explains creating promotions for limited-time pricing and eligibility rules

Explanation:

In Salesforce Industries CPQ (Vlocity), Configuration and Validation Rules are used to enforce logical product relationships during cart or order configuration. These rules ensure that customers can only select valid combinations of products and services. The three supported product relationship types are:

1. Requires
The Requires relationship enforces dependency between products. If a customer selects one product, another product must also be included.
Example: Selecting a mobile data plan requires a SIM card or a base subscription.

Purpose: Prevents incomplete or invalid configurations by ensuring all necessary components are present.

2. Excludes
The Excludes relationship prevents incompatible products from being selected together.
Example: A premium internet package excludes the ability to select a basic internet package simultaneously.
Purpose: Avoids conflicts and ensures customers do not purchase overlapping or contradictory services.

3. Recommends
The Recommends relationship suggests complementary products when a product is selected.
Example: Adding a smartphone to the cart may recommend accessories such as a protective case or insurance plan.
Purpose: Supports upselling and cross-selling strategies without forcing customer choices.

Why Other Options Are Incorrect

Optional:
Not a formal relationship type; optionality is inherent in product selection.

Limited Quantity:
Managed via inventory or quantity constraints, not product relationship rules.

Suggests:
Not a defined relationship type; “Recommends” is the supported term.

Not Compatible:
This is essentially covered by Excludes, not a separate relationship type.

References
Salesforce Industries CPQ Developer Guide – Product Relationships in Configuration and Validation Rules
Salesforce Developer Documentation
Salesforce Help – Industries CPQ Product Relationships Overview
Salesforce Help Documentation

Explanation

The remote method postCartItems is a core API call used in the Salesforce Industries CPQ (formerly Vlocity) application. Its function is to take a selection of products and physically add them as line items to the current active Quote or Order object (the "Cart"). It facilitates the transition of selected products from the available catalog into the transactional cart list.

Why other options are incorrect

A. Filters products for the cart
Product filtering is handled by different mechanisms like Context Rules or API methods such as getProducts with specific filters, not postCartItems.

B. Submits the order
Submitting the order is a distinct process handled by an API like submitOrder or checkout, which typically happens after all items are already finalized in the cart.

C. Puts the items in the selectables list
Items are in the "selectables list" (the available catalog) before being added to the cart. postCartItems moves them out of the selectables view and into the cart view.

E. Moves the order to the next stage
Order movement between stages is part of the Order Management process, managed by different API calls or workflow configurations that occur after the cart interaction is complete.

Explanation

Telecommunications companies have traditionally faced long and complex onboarding processes for new hires due to:

Highly complex product catalogs (bundles, plans, add-ons)
Strict regulatory and compliance requirements
Multiple legacy systems and operational tools
The need for employees to understand end-to-end service lifecycles (quote → order → provision → bill)

Because of this complexity, onboarding new employees—especially sales, service, and support agents—has historically taken weeks or even months.

Salesforce Industries (Vlocity) solutions were specifically designed to address this challenge by:

Simplifying user experiences
Providing guided flows (OmniScripts)
Reducing training time with standardized processes

Exam Tip 📝

On the Ind-Dev-201 exam, watch for industry pain-point questions like this.
If the question mentions:

Telecom
Complexity
Training or onboarding challenges

👉 The correct answer is very often True.

Explanation:

When you define a Context Mapping, you are mapping a "Context Dimension" (a virtual variable like AccountStatus) to a real piece of data in your Salesforce org.

Mapping to Data:
The Source Expression field is where you specify the path to the data. This is typically the API Name of a field on a specific Salesforce object (sObject).

Relationship Traversing:
You can often use dot notation to traverse relationships. For example, if your mapping is based on the Order object, but you need the Account's region, your Source Expression might be Account.BillingState.

Context Scope:
The system uses this API name to query the record currently in the "scope" of the cart (e.g., the Quote, Order, or Account record) and feed that value into the Rule Engine for evaluation.

Analysis of Incorrect Answers

B. %%field%%
This syntax is commonly used in Vlocity Templates or some legacy email templates to represent merge fields, but it is not the correct syntax for a Context Mapping Source Expression.

C. {{field}}
This is the Handlebars syntax used extensively in Vlocity OmniScripts and FlexCards to reference data in the JSON data wrap. While used elsewhere in the platform, the Context Rule service expects the literal API name or path, not a merge tag.

D. A calculated formula used by the context rule service engine
While you can use "Function" as a mapping type for complex logic, the "Source Expression" field itself is specifically designed to hold the field path or API name. Formulas are typically handled within the Entity Filter logic or via a custom Function mapping, not as a standard text-based "Source Expression."

References
Salesforce Help: Context Mappings in Industries CPQ
Vlocity Developer Guide: Configuring Context Rules and Dimensions

Explanation

Promotions in Salesforce Industries CPQ are designed to be temporary marketing tools with specific, often narrow, constraints compared to standard product offers.

Limited Set of Customers (A)
Promotions frequently target specific customer segments (e.g., new customers only, loyal customers, or specific demographics). While general offers can also be targeted, the combination of customer targeting with time limits points strongly toward a promotion use case.

Available for a Limited Time (C)
This is the defining characteristic of a promotion. Promotions use Time Plans and policies to automatically start and stop offering special terms on a specific date, which isn't the primary function of a standard, ongoing offer or price list entry.

Needs to be Sold Quickly (D)
Promotions are used to create urgency, drive immediate sales volume, or clear inventory. They are tactical business tools for rapid market response.

Why Other Options Are Incorrect

B. Product is available only to B2C customers
This is an eligibility requirement based on a persistent customer type. This can be handled by standard Qualification Rules or Context Rules applied to a basic product offer, which are more permanent parts of the catalog setup than a temporary promotion.

E. Product cost is increasing
An increasing product cost would typically result in a permanent update to the base price list entry for a standard offer, not the creation of a temporary promotional configuration.

Explanation:

The Vlocity Cards Framework (now part of Salesforce Industries Lightning Web Components and the Digital Commerce/Industries CPQ suite) is a powerful, reusable UI framework designed to build flexible, data-driven, and highly customizable user interfaces for Industries applications (such as CPQ, Billing, Order Management, etc.).

It provides three core building blocks:

Cards
Reusable, self-contained UI components that display data from one or more objects (e.g., product cards, account summary cards, line item cards, etc.). Cards can be interactive and support actions like adding to cart or navigating.

Layouts
Define how multiple cards are arranged and organized on a page (e.g., grid, flex, tabbed, or custom layouts). Layouts control positioning, responsiveness, and overall structure.

Templates
Pre-built or custom structures that combine cards and layouts to create complete pages or sections (e.g., product catalog pages, cart summaries, account dashboards). Templates allow rapid assembly of complex UIs using drag-and-drop in Vlocity Build or OmniStudio.

This framework enables developers and administrators to create consistent, responsive, and scalable front-end experiences without heavy custom Lightning Web Component (LWC) development.

Why the Other Options Are Incorrect

B. Cards and pre-built wizards
While the framework supports wizards (via OmniScripts or guided flows), pre-built wizards are not a core part of the Cards Framework itself. Wizards are primarily handled by OmniStudio/OmniScripts.

C. Templates for designing ad-hoc promotions
Promotions are configured via the Promotions object and related rules (eligibility, context, pricing), not through the Cards Framework. The Cards Framework is for UI presentation, not for creating or managing promotions.

References
Salesforce Help: Vlocity Cards Framework Overview
→ "The Vlocity Cards Framework provides cards, layouts, and templates to build dynamic, data-driven user interfaces."
Salesforce Trailhead: Build User Interfaces with Vlocity Cards
→ Covers cards, layouts, and templates as the foundational elements of the framework.

Explanation:

In Salesforce Industries CPQ (Vlocity), Time Plans are used to define temporary pricing or discount schedules for products within a promotion. When you assign a Time Plan to a child product in a promotion, you are specifically controlling the duration and timing of the price change applied by that promotion.

Time Plan Function:
A Time Plan defines start date, end date, and potentially multiple phases (e.g., 50% off for first 3 months, then 25% off for next 3 months).
When linked to a product in a promotion, it dictates how long the promotional pricing or discount applies to that specific product.

Scope:
The Time Plan affects only the product(s) to which it is attached within the promotion—not the entire promotion or other products.
It allows for granular control over promotional pricing duration per product.

Why the Other Options Are Incorrect:

B. When the entire promotion expires
Incorrect. Promotion expiration is controlled by the promotion's own start/end dates, not by a Time Plan assigned to an individual product. A promotion can expire while a product’s Time Plan is still active (or vice versa).

C. Which customers are eligible for the child product
Incorrect. Customer eligibility is managed by Promotion Eligibility Rules or Targeting Rules, not by Time Plans. Time Plans control duration of pricing, not who is eligible.

D. When the time plan begins for the child product
Incorrect. While a Time Plan includes a start date (so it does define when it begins), this option is incomplete. The Time Plan affects both the start and end timing (the entire duration) of the price change, not just the start. Moreover, the core effect is the duration of the price change, not merely the start time.

Reference:
Salesforce Industries CPQ documentation states that Time Plans are used to “define the time periods during which a promotion price adjustment is in effect for a specific product.”
They are often used for introductory offers, limited-time discounts, or phased pricing (e.g., “$10/month for 6 months, then $20/month”).

Conclusion:
Assigning a Time Plan to a child product in a promotion specifically controls how long the price of that child product is changed by the promotion (Option A).

Explanation:

In Salesforce Industries CPQ, Guided Selling provides an intuitive, interactive interface that assists users (especially sales reps) in selecting the right products for customers by walking them through a series of steps and pre-configured logic.

Here's how each of the correct features fits into the Guided Selling experience:

✅ A. Summary of assets
The system can fetch and display previously purchased products or services using the GetAsset API or pre-integrated DataRaptors, helping reps identify upsell or cross-sell opportunities.

✅ B. Step-by-step process
At its core, Guided Selling is a multi-step UI built with OmniScripts, designed to collect preferences, show filtered product choices, and guide users through product selection.

✅ D. Automatic totaling
As users add products to the cart, totals are updated in real-time using pricing engines and remote methods like getBasketDetails, ensuring visibility of the running total.

✅ E. Ability to edit items
Through persistent cart behavior and configured buttons/components, users can modify quantity, attributes, or remove items right from the Guided Selling UI.

❌ Why the Other Options Don’t Apply:
C. Launch cart from account/order
Not a feature of Guided Selling itself. Cart launch happens via actions configured on Account, Opportunity, or Quote but isn't visible within Guided Selling UI.

F. Change the price book
Price book (or Price List) is set at cart creation, not something users typically modify during the Guided Selling flow. It’s usually handled by backend logic.