Industries-CPQ-Developer Practice Test Questions

Explanation:

Product Attributes in Vlocity/Salesforce CPQ:

An attribute becomes a product attribute when it is assigned to a product or an object type (e.g., "Smartphone") that is used by products.

This links the attribute to the product’s configuration.

Why Option B?

Direct Association:
Attributes are inert until assigned to a product/object type.

Example: A "Color" attribute only affects products after assignment.

Reference: Vlocity Attribute Management

Why Not Other Options?

A (Product2 object): All attributes technically apply to Product2, but assignment activates them.
C (Vlocity Product Console): Just a UI tool; doesn’t define attribute types.
D (Type): No "Product Attribute" type exists—attributes gain context via assignment.

Explanation:

When you adjust the price of a product for a promotion in Salesforce Industries CPQ (formerly Vlocity):

You’re modifying pricing data, not the product hierarchy or core catalog structure.

Promotions and price adjustments:
Are stored as records linked to products or price list entries.
Do not change the parent-child relationships of products in the hierarchy.
Do not require platform cache refresh in most cases for price updates.

Hence:

You do NOT have to run Product Hierarchy Maintenance when merely updating prices or promotions.
You also typically do NOT need to refresh platform cache simply because of price changes—price data is fetched fresh during cart calculations.

Running jobs like:

Product Hierarchy Maintenance
Refresh Platform Cache
→ These are necessary when you:

✅ Change the structure of the product hierarchy (e.g. new parent/child relationships).
✅ Add new products to the catalog that should appear in search trees.
✅ Change data that affects cached catalog structures (like hierarchy paths).

But price adjustments for promotions don’t require these jobs.

Example
You change the promo discount for “iPhone X” from $50 off to $75 off.
This update happens directly in the promotion or price adjustment record.
No need to run maintenance jobs afterward.

Explanation:

In Salesforce Industries CPQ, when you perform a deep delete on a promotion, it removes:

The promotion itself
All discounts, cardinality changes, and products directly associated with that promotion

This ensures that the cart is fully cleaned of any promotional influence tied to that specific offer. It’s the default behavior controlled by the DeleteServices setting in Vlocity CMT Administration2.

❌ Why the other options are incorrect:
A. Removes everything from the Cart, including unrelated products Deep delete only affects the promotion and its related items, not unrelated products.
C. Removes the promotion, but nothing else That describes a shallow delete, which only removes the promotion and its discounts, leaving the products in the cart.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), the standard way to generate custom PDF quotes is through:

✅ Vlocity Document Templates

These are:

Templates designed in Microsoft Word or other document editors, then uploaded into the Salesforce org.
Connected to CPQ objects (e.g. Quote, Order, Account).
Capable of dynamically merging data:

Customer names
Quote line items
Pricing details
Custom fields

The process:

Design the template in Word (or any DOCX editor).
Upload it to Salesforce as a Document Template.
Configure bindings so template fields pull data from CPQ objects.
Users can then generate PDF quotes directly from the Cart or Quote UI.
This allows for highly customizable quote documents without coding or custom integrations.

Hence, the correct answer is:

✅ D. Vlocity Document Templates

Why not the others?

A. Integration with Microsoft Word
❌ Partially true—templates originate from Word—but the CPQ system uses Vlocity Document Templates to generate PDFs, not a direct runtime integration with Word.

B. Copy and pasting screen text
❌ Not a scalable or professional approach for PDF quotes.

C. Custom integration for each customer deployment
❌ Unnecessary. The product’s built-in Document Templates feature eliminates the need for custom integrations in most cases.

Explanation:

In Salesforce Industries CPQ, to configure a flat price bundle, you typically:

Set the parent product’s price to the total bundle price (Option D). This ensures the bundle appears as a single-priced item in the cart.
Zero out the child product prices (Option A). This prevents child products from contributing additional cost and keeps the bundle price fixed.

This approach is commonly used when:

You want to simplify quoting with a single price for a bundle.
You’re offering promotional pricing that hides individual component costs.
You’re using bundled product options or option pricing overrides to suppress child pricing.

❌ Why the other options are incorrect:

B. Change the child products that are not optional to zero
This is too narrow. You should zero out all child products, not just non-optional ones.

C. Change the price of the parent product to zero
That would make the bundle free unless child products contribute pricing—which defeats the flat price goal.

E. Do nothing, you can't create a bundle with a flat price
Not true! Flat pricing is a well-supported strategy in CPQ using bundled options and overrides.

Explanation:

The Take-Me-There feature in the Industries CPQ Cart (formerly Vlocity):

Appears as a clickable icon or link next to error or warning messages in the cart.

When you click it:
It navigates directly to the Line Item Details modal for the affected product.
Highlights fields or attributes that still require configuration (e.g. missing required attributes, invalid combinations).
Helps users quickly locate and resolve issues that prevent the order from being complete or valid.

Hence, it:

✅ Shows you where more details are needed to complete the order.

Why not the other options?

A. Directs you to the customer account page
❌ Incorrect. It works at the cart item level, not the customer record level.

B. Takes you to the product configuration in the master product catalog
❌ Incorrect. It opens the Line Item Details modal for the item already in the cart, not the catalog.

C. Provides optional guidance on item configuration
❌ Partially true—but the core purpose is to take you directly to fix incomplete data, not merely offer optional guidance.

Explanation:

In Salesforce Industries CPQ (Vlocity Cart), the Display Name field of an Attribute Category is what appears at run-time during order capture in the Cart. This field serves as the section heading in the product configuration window, helping users visually group related attributes.

For example:
If you create an attribute category called "Mobile Devices" and set its Display Name to "Smartphone Specs", that label will show up in the Cart UI as the header for attributes like Brand, Capacity, or OS.

This improves:
User experience by organizing attributes clearly
Sales efficiency by guiding reps through configuration
Data accuracy by ensuring attributes are grouped logically

❌ Why the other options are incorrect:

A. Name: Used internally for identification, not shown at run-time.
C. Category: Refers to the type of attribute grouping, not a display label.
D. No Attribute Category fields display at run-time: Incorrect—Display Name absolutely does.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity):
Promotions can apply discounts to:

The main (parent) product
Specific child products in a bundle

Each discount in a promotion can have its own Time Plan or affectivity period, which:

✅ Defines:
Start date
End date
Duration (e.g. “3 months free”)

This allows a discount on a child product to expire before the promotion itself ends or to only apply during a certain period. For example:

Promotion duration → 12 months
Discount on child product → valid only for the first 3 months
Hence, to limit the duration of a discount on a child product’s price, you should:

✅ Use the time plan on the child product’s discount.

Why not the other options?

A. The time plan on the entire promotion
Controls the global duration of the entire promotion, not individual child discounts.

B. The time policy of the promotion
Similar to A—applies to the overall promotion duration, not child-level discounts.

D. The override of the child product's cardinality
Cardinality controls quantity rules (min/max/default), not discount durations.

✅ Example
Promotion: “Family Bundle Discount” → valid Jan 1 – Dec 31
Discount on Child Product (e.g. streaming service):
Time Plan → valid Jan 1 – Mar 31 only
Discount = 100% off

→ The child product’s discount stops after March 31, but the overall promotion continues for the rest of the year.

Explanation:

To prevent a product from being tracked as an asset in Salesforce Industries CPQ, developers can use the following two best-practice methods:

C. Check the Is Not Assetizable property
This flag is set on the product record in Vlocity EPC. When enabled, it ensures the product is excluded from asset creation during the order lifecycle. This is ideal for promotional items or virtual services that don’t require tracking.

D. Check the Virtual Item property
Marking a product as a Virtual Item also prevents it from being assetized. Virtual items typically represent non-physical or non-trackable components like setup fees, digital services, or bundled discounts.

These two flags work independently or together to ensure products are orderable but not tracked in the customer’s asset list.

❌ Why the other options are less effective:

A. Create a context rule to control assetization
Context rules manage eligibility and visibility, not assetization behavior. They don’t prevent asset creation.

B. Check the Do Not Assetize property in the Cart's line item configuration window
This is a runtime setting, not a persistent product-level configuration. It’s not reliable for consistent assetization control across orders.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), when users configure products in the cart, there may be:

Discounts
Promotions
Markups
Manual overrides
Tax or fees

To help users understand how the final price was calculated, the cart includes the Price Details icon next to each line item.

✅ Price Details icon allows users to:

See the Base Price.
View each pricing element applied:

Discounts
Promotions
Surcharges
View any manual price overrides.
Understand how the final price was calculated.

Hence, the correct answer to:
“How can a user understand changes to pricing applied in the cart?”
is clearly:

✅ C. By clicking the Price Details icon on the line item

Why not the other options?

A. The display text in the Products list in the cart
❌ Incorrect. The product list might show the total price but does not explain how pricing was calculated.

B. Popup message window after the order is submitted
❌ Incorrect. Pricing breakdown is available during cart configuration, not only after submission.

D. Pricing adjustments do not display in the cart
❌ Incorrect. Pricing adjustments absolutely do display in the cart through the Price Details icon.

Example
User sees:
iPhone X → $850.00

Clicks the Price Details icon:

Base Price: $999.99
Promotion: -$50.00
Manual Discount: -$99.99
Total Price: $850.00