Industries-CPQ-Developer Practice Test Questions

Explanation:

Price Details Window in Salesforce CPQ/Vlocity:

This window shows a breakdown of how a line item’s price is calculated, including:
Base Price: Original price from the price list.
Adjustments: Discounts, markups, or promotions (e.g., "$50 off").
Overrides: Manual price changes (e.g., sales rep edits).

Why Options B & C?
B. Pricing Adjustment:
Explicitly lists discounts/promotions (e.g., "20% Summer Sale").

C. Pricing Override:
Shows manual price changes (e.g., "Overridden Price: $90").

Reference: Salesforce CPQ Price Details

Why Not Other Options?
A (Base Price): Doesn’t reflect adjustments (it’s the pre-discount price).
D (Product Description): Unrelated to pricing logic.
E (Price List): Only shows the source, not applied adjustments.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity):

Price Lists are the primary mechanism for storing prices for products.
Each Price List can define a base price for the same product, but potentially for:

Different customer segments
Different sales channels
Different regions or geographies
Different contract terms

This allows you to assign multiple base prices to the same product by placing it in multiple price lists. For example:

Employee Price List → $15 for Product X
Retail Price List → $25 for Product X
Wholesale Price List → $10 for Product X

Hence, statement A is correct.

Why not the other options?
B. You don’t need the Salesforce price book.
❌ Incorrect. While Salesforce Industries CPQ uses its own price lists in the EPC (Enterprise Product Catalog), integration with the Salesforce price book is still often required for Order Management and other core Salesforce objects. The price book isn’t simply “not needed.”

C. You can ignore affectivity time frames.
❌ Incorrect. Affectivity (valid-from and valid-to dates) remains critical even when using multiple price lists. It controls:

When a price is valid
Seasonal or promotional pricing

You cannot ignore affectivity—it’s fundamental to pricing logic.

Explanation:

Promotions and Child Product Discounts in Salesforce CPQ/Vlocity:
Promotions can include time-bound discounts on child products (e.g., "20% off for the first 3 months of a 12-month promotion").
The parent promotion’s end date and child product discount’s end date are independent.

Why "True"?

Example:
Promotion runs for 12 months (Jan–Dec).
Child product discount expires after 3 months (Jan–Mar).

Reference: Salesforce CPQ Promotions

Explanation:

In Salesforce Industries CPQ, the Qualification context rule type is used to determine whether a customer is eligible for a promotion before it’s added to the cart. These rules evaluate conditions such as:

Account type (e.g., B2B vs. B2C)
Customer location
Subscription status
Any custom field or context dimension

By applying Qualification rules, you ensure that promotions are only offered to customers who meet specific criteria—helping maintain pricing integrity and targeting accuracy.

❌ Why not Penalty?
Penalty rules are used to apply consequences (like fees or restrictions) when a customer cancels a promotion or contract early.
They do not determine initial eligibility.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), Guided Selling uses remote methods (also called remote actions) to:

Create and manage the Cart
Add products
Retrieve cart items
Update configurations
Submit orders

These remote methods live in an Apex class called CpqAppHandler.

CpqAppHandler is the server-side Apex controller that exposes various remote methods used by:

OmniScripts
Lightning components
Guided Selling UI

Examples of remote methods in CpqAppHandler

createCart
getCartsItems
postCartsItems
putCartsItems
checkout
submit

So while names like createCart, getCartsItems, etc. are the individual methods, the class in which they exist is CpqAppHandler.

Hence, the correct answer to:
In Guided Selling, which of these is the class for the remote methods?
is clearly CpqAppHandler.

Why not the other options?
A. done
Not a valid class.

B. vlcCart
Refers to a front-end JavaScript object used in Vlocity UI—not an Apex class.

D. createCart, E. getCartsItems, F. getCartsProducts, etc.
These are method names, not class names.

I. checkout, J. submit
Methods, not classes.

Explanation:

In Salesforce Industries CPQ (Digital Commerce), the dcOffersList component is responsible for using a child catalog code to call the APIs and retrieve the appropriate products. This component is typically used in Guided Selling flows where product offers are dynamically filtered and displayed based on catalog hierarchy and context.

It interacts with the Digital Commerce APIs, passing the child catalog code as part of the request to:

Fetch relevant product offers
Apply context filters (e.g., account type, location)
Display results in a user-friendly format

This makes dcOffersList ideal for scenarios where product selection is driven by nested catalogs or customer-specific eligibility.

❌ Why the other options are incorrect:
A. dcCatalog: This component displays the top-level catalog, not child catalogs or filtered offers.

B. dcChildCatalog: While it may reference child catalogs, it doesn’t directly handle API calls to retrieve filtered product offers like dcOffersList does.

Explanation:

Context Mapping in Vlocity Context Rules
A context mapping connects context dimensions to data sources. It can pull values from:
- sObjects (e.g., Account.Industry)
- Functions (e.g., Apex methods)
- Static values entered during setup

Key Characteristics
- Links dimensions like CustomerTier to real data
- Supports dynamic calculations through functions
- Enables rule flexibility across different contexts

Why This Matters
Context mappings power dynamic pricing and promotions by connecting business rules to actual customer/product data.
Example: Mapping "CustomerTier" to Account.Tier__c field automatically applies tier-specific pricing.

Technical Note
Mappings are configured in OmniScripts or through Vlocity's admin UI, not in code.

Explanation:

In Salesforce Industries CPQ, a pricing element represents a component of the pricing logic used to calculate the final price of a product or service. Each pricing element includes:

C. Pricing Calculation This defines how the price is derived—whether it's a flat rate, percentage, tiered, or based on usage. It’s the logic behind the pricing element.
D. Charge (Amount) This is the actual monetary value applied to the product or service. It’s the result of the pricing calculation and is what appears on the quote or invoice.

These two components are essential to every pricing element: one defines the logic, the other delivers the result.

❌Why the other options are incorrect:
A. Currency Code While important for pricing display and conversion, it’s a metadata attribute, not a core part of the pricing element itself.
B. Price Category This is used to group or classify pricing elements (e.g., recurring vs. one-time), but it’s not a functional part of the pricing calculation or charge.

Explanation:

The createCart method in Salesforce Industries CPQ:

Initializes a new CPQ cart session.
Creates the core sales transaction object (either Quote or Order) depending on the cart’s configuration.
Optionally associates the cart with an Opportunity.

Here’s how each option fits:

✅ A. Order
Can be created by createCart.
If the transaction type is set to Order, the CPQ engine creates an Order record during the cart session.

✅ B. Quote
Can be created by createCart.
If the transaction type is set to Quote, the CPQ engine creates a Quote record to store product selections, prices, etc.

✅ D. Opportunity
Can be created or linked by createCart.
The cart often references an Opportunity record, and some flows allow the creation of a new Opportunity if one does not already exist.

❌ C. Contract
NOT created by createCart.

Contracts result from downstream processes like:

Order activation and fulfillment
Subscription or billing processes
Contracts are not part of the cart creation process. They’re a post-order entity, typically generated after the order is completed and activated.

Hence, the answer to:

Which of the following is NOT created using the createCart method?

is clearly Contract.

Explanation:

Vlocity Object Type Inheritance
Vlocity uses HAS-A (composition) architecture for object relationships.

Key Characteristics
- Objects reference other objects instead of inheriting properties directly
- Example: Product Bundle contains child products without inheriting their attributes
- Enables flexible, modular data structures

Why HAS-A Architecture?
- Avoids rigid class hierarchies of IS-A inheritance
- Better suited for complex product/service configurations
- Matches real-world business relationships

Technical Implementation
Implemented through lookup relationships and reference fields in the Vlocity data model

Comparison
HAS-A (Vlocity) = Composition/Containment
IS-A = Traditional class inheritance (not used)
Hybrid/Private = Not applicable to Vlocity's model