Industries-CPQ-Developer Practice Test Questions

Explanation:

In Salesforce Industries (Vlocity) CPQ, an attribute becomes a product attribute only when it is associated with the product model—that is, when it is assigned to a product or to an object type that products inherit from.

Simply creating an attribute does not automatically make it a product attribute. The designation happens through assignment, not through where or how the attribute is created.

🔍 Why option B is correct
Attributes in Industries CPQ are generic by default. They can be reused in many contexts (product configuration, rules, pricing, etc.). An attribute becomes a product attribute when:

It is assigned directly to a product, or
It is assigned to an object type, and products inherit it from that object type

Once assigned, the attribute:
Appears in the product configuration UI
Can be configured by users (if run-time configurable)
Participates in pricing, rules, and validation
This assignment step is what formally designates the attribute as a product attribute.

❌ Why the other options are incorrect

❌ A. Setting its applicable object to Product2
The applicable object defines where data is stored, not whether the attribute is a product attribute.
An attribute can have Product2 as its applicable object and still not be assigned to any product.
❌ C. Creating the attribute through Vlocity Product Console
The Product Console is just a tool for creation and management.
Creating an attribute there does not automatically associate it with a product.
❌ D. Setting the type to Product Attribute
There is no attribute type called “Product Attribute” in Industries CPQ.
Attributes are typed by data type (String, Number, Boolean, etc.), not by usage.

📌 Key Exam Takeaway
An attribute becomes a product attribute only when it is assigned to a product or object type.
This is a very common Ind-Dev-201 exam trap, testing the difference between:
Attribute definition
Attribute assignment

📚 References
Salesforce Industries CPQ – Product Attributes Overview
Enterprise Product Catalog (EPC) – Object Types and Attribute 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:

When a promotion is applied to a cart, it often brings with it specific modifications, such as discounted prices, added products, or attribute overrides. A Deep Delete is designed to "undo" the entire impact of that promotion.

Reversal of Discounts:
If the promotion provided a 20% discount on a phone, deleting the promotion will revert the phone to its original base price.

Removal of Included Items:
If the promotion automatically added a "Free Case" to the cart, the Deep Delete will remove that specific case record from the line items.

Cleaning the JSON:
It ensures that all hidden metadata and adjustments associated with that specific promotion ID are purged from the Cart's data structure, returning the remaining products to their "Pre-Promotion" state.

Analysis of Incorrect Answers

A. Removes the promotion and everything from the Cart, including products not related to the promotion:
This would be a catastrophic user experience. A Deep Delete is surgical; it only targets the "Promotion" entity and the specific changes it caused. Products added manually by the user that are not part of the promotion will remain untouched.

C. Removes the promotion, but nothing else:
This describes a "Shallow Delete." If the system only removed the promotion record but left the discounted prices or free items in the cart, it would allow users to "cheat" the system by getting the benefits of a promotion without the promotion actually being active.

References
Salesforce Help: Deleting Promotions from the Cart
Vlocity Documentation: Promotion Maintenance and Cart Actions

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:

To set a flat price (a single, fixed price) for a bundle in Salesforce CPQ (Vlocity):
D. Change the price of the parent product to the total price of the bundle –
The parent product (the bundle itself) is given the total bundled price (e.g., $100 for the entire package).
A. Change the child product prices to zero –
The child products (components of the bundle) are priced at $0 so they don’t add to the parent price.
This ensures the bundle price is only the parent’s price, not a sum of child prices.

Why the Other Options Are Incorrect:
B. Change the child products that are not optional to zero – Incorrect.
All child products (optional or required) should be $0 to avoid double-charging, unless you want some to have separate charges.
C. Change the price of the parent product to zero – Incorrect.
This would make the bundle free. The parent must carry the bundle’s total price.
E. Do nothing, you can't create a bundle with a flat price – Incorrect.
Bundles can have flat prices using the method above.

Reference:
Salesforce CPQ bundle pricing:
Parent price = total bundle price.
Child prices = $0 (unless you want itemized pricing).

Conclusion:
For a flat-price bundle, set the parent price to the bundle total and child prices to zero (Options A and D).

Explanation:
In Salesforce Industries (Vlocity) CPQ, the "Take-me-there" feature is a crucial validation and navigation tool within the Cart.

Error Resolution
When a user attempts to submit an order or validate a cart, the CPQ engine runs rules. If there are missing required attributes, cardinality errors (for example, you need at least 2 of a specific child product), or configuration conflicts, the Cart displays an error notification.

Direct Navigation
The "Take-me-there" link or icon appears next to these errors. When clicked, it automatically navigates the user to the specific product or bundle configuration screen and highlights the exact field or attribute that requires attention.

User Experience
This prevents users from having to manually hunt through complex, multi-level bundles to find the source of a validation error.

Why other options are incorrect
A. Directs you to the customer account page: Navigation to the Account page is typically handled by a "Done" or "Back" action in an OmniScript, not the "Take-me-there" validation tool.

B. Takes you to the product configuration in the master product catalog: The feature operates within the Cart or Transaction context (Quote or Order), not the administrative Product Console or Master Catalog.

C. Provides optional guidance on item configuration: While it helps with configuration, it is not optional guidance like a tooltip; it is a functional navigation aid triggered by validation failures.

References
Using the Vlocity Cart (Salesforce Help)
Cart Validation and Error Handling (Salesforce Documentation)

Explanation:

In Salesforce Industries CPQ (Vlocity CPQ), Attribute Categories (vlocity_cmt__AttributeCategory__c) are used to logically group related attributes for a product or object type. They appear in the cart configuration window (or OmniScript or guided selling configuration panel) during order capture or runtime to organize and display attributes in a user-friendly way.

Display Name
Display Name (the field vlocity_cmt__DisplayName__c on the Attribute Category record) is the value that actually shows up at run-time in the cart.
This is the human-readable label or heading for the category tab or section (for example, "Color & Storage", "Connectivity Options", "Billing Preferences").
It is what the end-user (agent or customer) sees during configuration.

Name
This is the internal API name or developer name (for example, "Color_Storage_Group"). It is not displayed to the user at run-time and is used for backend or reference purposes only.

Category
There is no field called "Category" on AttributeCategory__c that displays at run-time. The object itself represents the category.

No Attribute Category fields display at run-time
Incorrect. Attribute Categories do display at run-time as collapsible sections, tabs, or grouped panels in the cart configuration UI, but only the Display Name is used for the visible label.

Key Concept Summary
Attribute Category organizes attributes into logical groups in the cart configuration window.
Display Name is the runtime-visible label or heading for the category and is what users see.
Name is an internal identifier and is hidden from users.
This separation follows Salesforce best practices: internal names for developers and administrators, display names for user experience.

References:
Trailhead: Configure Product Attributes and Cart Configuration in Industries CPQ modules, which show that Display Name on Attribute Categories appears as the section title in the cart during order capture.
Salesforce Help: Attribute Categories (Industries CPQ), which states that the Display Name is used in the user interface to identify the attribute category during runtime configuration.

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 (Vlocity) CPQ, pricing in the cart is often the result of multiple layers, including:
Base price from a price list
Pricing adjustments such as discounts, promotions, and overrides
Time-based or conditional pricing
To help users understand how the final price was calculated, the Cart provides a dedicated Price Details view.

Why Price Details is the correct choice
When a user clicks the Price Details icon on a cart line item, they can see:
The base price
Any pricing adjustments such as dollar or percentage discounts
Pricing overrides
How each adjustment contributes to the final price
This transparency is essential for sales users explaining prices to customers, troubleshooting unexpected pricing, and validating promotions and discounts.

Why the other options are incorrect
A. The display text in the Products list in the cart
The Products list typically shows only the final price and does not explain how that price was derived.

B. Popup message window after the order is submitted
Pricing explanation must be available before submission. Post-submission popups are not used to explain pricing logic.

D. Pricing adjustments do not display in the cart
Incorrect. Pricing adjustments do display, but only through the Price Details view.

Key Exam Takeaway
The Price Details icon is the primary way users understand pricing changes and adjustments in the cart.
This is a frequently tested concept on the Salesforce Certified Industries CPQ Developer (Ind-Dev-201) exam.