Industries-CPQ-Developer Practice Test Questions

Explanation:

The Vlocity (Salesforce Industries) Product Console is designed to work with standard EPC (Enterprise Product Catalog) objects provided by Salesforce Industries.

👉 It does NOT support creating custom EPC objects.

Key points:
* You can configure and manage standard EPC objects such as Products, Attributes, and Rules.
* You cannot create new or custom EPC object types from the Product Console.
* Any customization beyond standard EPC objects must be handled through:
* Standard Salesforce objects
* Extensions via configuration, rules, or integrations (not new EPC object definitions)

📚 Key Exam Concept to Remember
Product Console = configuration of standard EPC objects only, not creation of custom EPC objects.
This is a classic Ind-Dev-201 true/false question designed to test platform limitations.

🔑 Exam Tip
If you see:
* “Product Console”
* “custom EPC objects”
👉 The answer is False for support, therefore the statement is True.

Explanation:

The Run-time Configurable checkbox is the specific "gatekeeper" for user interaction in the cart.

User Permission: When this property is checked on the Product-Attribute assignment, it tells the CPQ engine that this specific attribute should be rendered as an input field (dropdown, text box, etc.) in the configuration window.

Default Behavior: If an attribute is assigned to a product but is not marked as Run-time Configurable, it acts as a "Read-Only" reference or a background property. The value will exist on the record, but the user will not be able to change it in the Cart.

Flexibility: This allows developers to have "technical" attributes (hidden or read-only) and "commercial" attributes (user-configurable) on the same product.

Analysis of Incorrect Answers:

B. Active property: The Active checkbox on an attribute or its assignment simply determines if the attribute is "on" or "off." If an attribute isn't active, it won't appear at all, but being active doesn't automatically mean the user can edit it; it might still be read-only.

C. Not Hidden property: While there is a Hidden property that determines visibility, being "Not Hidden" only ensures the user can see the attribute. It does not necessarily grant the permission to modify the value. An attribute can be visible but disabled (read-only).

D. Filterable property: This property is used for Product Selection. If an attribute is marked as Filterable, it appears in the left-hand sidebar of the product catalog to help users search for products (e.g., filtering for "Red" phones). It has no impact on the configuration window once the product is already in the cart.

References:
Salesforce Help: Product Attribute Properties
Vlocity Documentation: Configuring Attributes for the Vlocity Cart

Explanation:

In the Industries CPQ Cart (formerly Vlocity Cart), when there’s a configuration error or missing required information on a product in the cart, the UI provides a “Take Me There” icon or link.

When clicked:
It jumps directly to the Line Item Detail modal for that product.
It highlights missing fields or required attributes that need the user’s attention.
This helps users quickly locate and fix configuration errors without manually searching through all cart items.

This behavior ensures a smooth user experience and helps users achieve a Perfect Order.

Why not the other options?
A. Returns the user to the Order Detail page to correct configuration errors
→ Incorrect. The icon is about fixing items inside the cart, not navigating to the order record.

C. Takes the user to the Product Catalog
→ Incorrect. That’s unrelated to the error resolution flow.

D. Opens the Price List associated with the cart line items
→ Incorrect. The price list is not opened by the “Take Me There” icon.

Explanation:

In Salesforce Industries CPQ, rules (including Context Rules, Advanced Rules, and other rule types) are specifically designed to prevent the submission of inaccurate, invalid, or non-compliant orders.
Here’s how rules enforce accuracy and validity during the quoting and ordering process:

Context Rules (Qualification and Penalty)
* Qualification Rules filter out ineligible products, promotions, or price lists based on context (e.g., account type, location, service availability).
→ Prevents users from adding or quoting products/services the customer cannot order (e.g., fiber service in a non-fiber area).
* Penalty Rules ensure appropriate fees are applied (e.g., early termination) so the order reflects true cost and compliance.

Advanced Rules (Compatibility, Configuration, Validation)
* Enforce product relationships: requires, excludes, recommends, or mutual exclusivity within bundles.
→ Prevents invalid configurations (e.g., adding incompatible add-ons or exceeding cardinality limits).
* Validation Rules can block cart submission if mandatory attributes are missing, quantities are invalid, or configuration rules are violated.

Pricing and Discount Rules
* Ensure correct pricing adjustments, promotions, and overrides are applied.
* Prevent manual overrides that violate business rules (e.g., discounts exceeding allowed thresholds).

Overall Purpose
Rules act as guardrails throughout the guided selling, cart, and order submission flow. They reduce errors, ensure regulatory/compliance adherence (critical in industries like telecom, utilities, media), and prevent inaccurate orders from being submitted — which could lead to fulfillment failures, billing issues, or customer dissatisfaction.
Without these rules, users could easily create and submit invalid carts/orders (e.g., wrong product mix, missing required items, ineligible services), resulting in downstream problems.

Why False would be incorrect
False would imply that rules do not help prevent inaccurate order submission — but this directly contradicts the core purpose of rules in Industries CPQ: to enforce business logic, validity, and compliance before an order can proceed.

Key Concept Summary
* Rules (Context + Advanced) are the primary mechanism for validation and eligibility enforcement.
* They block invalid configurations, ineligible items, and non-compliant orders from being submitted.
* This is a foundational principle of Industries CPQ — rules exist precisely to keep orders accurate and valid.

References
Trailhead: "Meet Context Rules" and "Industries CPQ Advanced Rules" modules — Describe rules as tools to "ensure valid product configurations," "control eligibility," and "prevent invalid orders."
Salesforce Help: "Context Rules Overview" and "Advanced Rules in Industries CPQ" — Emphasize that rules validate and qualify during cart and order processes to avoid inaccurate submissions.

Explanation:

In the Salesforce Industries (formerly Vlocity) CPQ reference implementation, the "Submit Order" button is typically configured as an Action that triggers a specific OmniScript (often part of a guided selling or checkout process).

Orchestration via OmniScript: The button doesn't just execute a single command; it launches an OmniScript that handles the multi-step finalization process.

CPQ API Interaction: Within this OmniScript, an Integration Procedure is called (such as SubmitOrderVIP). This procedure invokes the CPQ Checkout API.

Order Lifecycle: The API transitions the Order status (typically to Activated), ensures the order is ready for fulfillment, and handles the "Assetization" process (converting Order Line Items into Assets for Asset-Based Ordering).

User Navigation: After the logic completes successfully, the OmniScript uses a Done Action to redirect the user back to the parent Account record to view the updated assets and order history.

Why other options are incorrect

A. Invokes the CPQ API (Directly): While the API is eventually called, the button in the UI is traditionally wired to an OmniScript or a Card Action to allow for UI feedback and branching logic, rather than a raw API call.

C. Invokes a Flow: Salesforce Industries CPQ uses OmniStudio (OmniScripts and Integration Procedures) as its primary orchestration engine rather than standard Salesforce Flows for its core CPQ actions.

D. Collect information: While some checkout scripts can collect billing info, the primary technical function of the "Submit Order" button in the standard CPQ framework is the backend transition to Order Activation and Asset creation.

References
Checkout API (Salesforce Help)
Submit an Order (Salesforce Documentation)

Explanation:

Adjustments are used to alter the final price of a product without changing the "Base Price" record itself.

$50 off (B): This is a Standard Amount Adjustment. It subtracts a fixed currency amount from the base price. In the Product Console, this would be configured as a Pricing Element with an Amount value of -50.

20% off for 3 months (C): This is a Percentage Adjustment combined with a Time Plan.
* The "20% off" is the adjustment value (Pricing Element).
* The "for 3 months" is a Time Plan that limits the duration of that adjustment.
This is a classic example of a "Promotional Adjustment" used in communications to offer a temporary discount.

Analysis of Incorrect Answers

A. $12 price for a product on an employee price list: This is considered a Price List Entry (PLE) / Base Charge or a Price Override, not an adjustment. It is a specific price defined for a specific segment (Employees). It replaces the standard price rather than modifying it.

D. $35 recurring monthly price for B2C customers: This is a Base Charge (Recurring). It defines the starting point of the price for a customer segment. It is the value that an adjustment would then be applied to.

References
Salesforce Help: Price Adjustments and Overrides
Vlocity Developer Guide: Exercise 4-5: Create Pricing Components

Explanation:

In Salesforce Industries CPQ (Vlocity), you can assign multiple context rule sets to a single promotion. This flexibility allows developers to layer different qualification criteria—such as geography, account type, or product eligibility—into a promotion’s logic.

Each rule set can contain one or more context rules, and promotions can evaluate all assigned rule sets during runtime to determine whether the promotion should be qualified or disqualified for a given customer.

This modular approach makes it easier to:
Reuse rule sets across multiple promotions
Combine eligibility logic from different business domains
Maintain cleaner and more scalable rule configurations

Explanation:

In Vlocity (Salesforce Industries CPQ), context mappings link context dimensions (like “Country,” “Segment,” or “Sales Channel”) to the actual fields on Salesforce objects (such as Quote, Order, Account, etc.) that hold the real data used in context rule evaluation.

You can configure context mappings from either of two places:

✅ From the Context Dimension
You can open the dimension (e.g., “Country”) and define which objects and fields it maps to.

Example:
Dimension: Country
Maps to: Quote.Country__c

✅ From the Context Scope
You can open a context scope (e.g., Quote) and define which context dimensions it includes and how they map to fields.

Example:
Scope: Quote
Dimension mapping:
Country → Quote.Country__c
Segment → Quote.Segment__c

So the statement:
“Context mappings can be configured from the context dimension or the context scope.”
is True.

Explanation:

In Salesforce Industries CPQ, when the Cost & Margin feature is enabled, the acceptable upper and lower bounds for the margin are stored and managed within a Calculation Matrix.

Calculation Matrix Function: The matrix is a powerful lookup table used within a Pricing Procedure. It defines a range of acceptable margins (bounds) based on various inputs (like product type, customer segment, or account ID).

Margin Validation: The CPQ engine checks the calculated margin against the ranges specified in the matrix. If a sales representative attempts to configure a price that falls outside these bounds (e.g., offers too steep a discount resulting in a margin below the lower bound), the system can trigger an alert, require approval, or prevent the order submission entirely.

Why other options are incorrect

B. In a Margin attribute: Margins are dynamic calculations, not static attributes configured on the product itself.

C. In a Cost price list entry: The Cost Price List Entry stores the cost of the product, which is used as an input to calculate the margin, but not the acceptable bounds for that margin.

D. In a price list: The Price List and Price List Entries define the standard selling prices and costs, not the dynamic margin rules or boundaries.

References
Defining Cost and Margins (Salesforce Help)
Calculation Matrix and Lookup Table in Salesforce Industries

Explanation:

In Salesforce Industries CPQ:
The Guided Selling cart is powered by APIs that read, write, and update data in the cart.
To update items already in the cart (e.g. quantity, attributes, selections), you must send data back to the server so it can persist the changes.

That’s precisely what the putCartsItems API does:
putCartsItems → Used to update existing items in the cart.
Updates quantities
Changes attribute values
Modifies selections

Without calling putCartsItems, the changes remain only in the client session and will not persist.

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

B. vlcCart
This is a front-end object, not an API call to update data.

C. CpqAppHandler
It’s an Apex class, not the specific cart update call.

D. createCart
Creates a new cart—not for updating items.

E. getCartsItems
Reads data from the cart but does not update it.

F. getCartsProducts
Fetches available products, not updating items.

H. postCartsItems
Typically used for adding new items rather than updating existing ones.

I. checkout
Used at the end of the process to finalize the order.

J. submit
Submits the order—not used for in-session updates of items.