IPQ-435 Practice Questions

An "Effective Until date," commonly implemented as an EndDate on a subscription or contract record, is the specific mechanism used to define the termination point of a subscription plan. This date field provides a clear, declarative boundary for the subscription's active period. The system uses this date to automatically manage the subscription's lifecycle, ensuring that services and billing cease correctly when the plan concludes, preventing unintended renewals or charges. This is the most direct and precise method for ensuring a subscription ends on a specific date.

1. Salesforce Help

"Subscription Fields": The Subscription object in Salesforce CPQ includes an SBQQEndDatec field. This documentation states its purpose is to define "The last day of the subscription term." This directly corresponds to the concept of an "Effective Until date." (Reference: Salesforce Help Portal

Object Reference for Salesforce CPQ

Subscription object field definitions).

2. Salesforce Help

"Contract Fields": The standard Contract object

which often governs subscriptions

has an EndDate field. This field is defined as "The end date of the contract

" establishing the overall term limit for any associated subscriptions. (Reference: Salesforce Help Portal

Standard Objects

Contract object field definitions).

3. Salesforce Billing Implementation Guide: The guide details how Order Products

which represent subscriptions to be billed

are managed. The End Date on the Order Product is critical as it "determines the end of the billing period for the subscription product." This confirms the end date's role in terminating the billing lifecycle. (Reference: Salesforce Billing Implementation Guide PDF

section on "Order Management and Activation").

The scenario describes a service relocation, which is a standard Move, Add, Change, Disconnect (MACD) process in order management. In the context of the Salesforce Industries data model, a customer's active service is represented as an Asset. All MACD operations, including a "Move," are initiated by performing an action on the corresponding Asset. The "Move" action is the most precise function for this scenario, as it is specifically designed to orchestrate the transfer of a service from one location to another, typically by creating a new order that manages the disconnection at the old address and installation at the new one.

1. Salesforce Help

Industries Order Management

"Move a Service Using the Move Standard Flow." This document explicitly states

"The Move flow enables you to move a customer's service from one location to another... The Move flow is launched from an asset." This directly supports that the "Move" action is taken on the Asset.

2. Salesforce Help

Industries Order Management

"Move

Add

Change

or Disconnect (MACD) for Orders and Assets." This guide outlines the overall MACD process

stating

"You can modify

cancel

or disconnect an asset after an order has been fulfilled." This confirms that such lifecycle actions are performed on the Asset

not the original Order.

3. Salesforce Developer Documentation

"Industries CPQ and Order Management for Developers

" Asset-Based Ordering. The architectural documentation for Salesforce Industries describes the asset-based ordering model where an initial order creates an asset

and any subsequent modifications (MACD) are new orders generated from that asset. This principle invalidates performing a move action on the original

fulfilled order.

The Vlocity Cart's line item configuration window allows users to specify details for each individual product or service within an order. A primary function of this window is to associate the line item with the correct accounts for fulfillment and invoicing. Users can select or change the Service Account, which defines where the service will be provisioned or to which entity the asset belongs. Similarly, users can modify the Billing Account on a per-line-item basis, enabling different items in the same cart to be billed to different accounts. This is a standard and fundamental capability for managing complex orders.

1. Salesforce Industries CPQ Developer Guide

"Object and Field Definitions for Orders": The Order Item (OrderItem) object in the Industries CPQ data model includes lookup fields such as ServiceAccountId and BillingAccountId. The line item configuration window in the Vlocity Cart UI is the primary interface for populating these fields for each item in the cart. (Reference: Specific field definitions within the Order and OrderItem object documentation).

2. Salesforce Industries Communications

Media

and Energy (CME) Administrator Essentials Courseware

"Module: Industries CPQ Cart": This official training material demonstrates the cart's user interface. It explicitly shows that upon clicking to configure a line item

the user is presented with a modal window containing fields to select both the Service Account and Billing Account for that specific line item. This confirms it is a standard

modifiable piece of information.

3. Salesforce Help

Industries CPQ

"Configuring Products in the Cart": The documentation describes how the cart allows for detailed configuration of products. This configuration includes "setting the service and billing accounts for the asset that will be created from the order line item." This directly supports the modification of both account types at the line item level. (Reference: Section on line item configuration and assetization).

The Recurring Total and One Time Total fields displayed for each line item in the Quote Line Editor (referred to as the "Cart Line Items pane") represent the final calculated prices for that line. The Salesforce CPQ pricing engine follows a specific sequence, often called the price waterfall. This process starts with the list price and sequentially applies various modifications, including automated adjustments from pricing rules and promotions. The final result of this waterfall calculation is the Net Price, from which the One Time Total and Recurring Total are derived. Therefore, these totals inherently reflect all active pricing adjustments.

The putCartsItems method is the specific API action required to update items within the Industries CPQ cart. In the context of cart-based APIs, this method corresponds to an HTTP PUT request. It is designed to modify existing line items, such as changing their quantity or updating product attribute selections. While a handler like CpqAppHandler might invoke this logic, putCartsItems represents the direct, precise operation for performing the update, distinguishing it from actions like adding new items (postCartsItems) or retrieving cart data (getCartsItems).

A. done: A generic term for completing a process, not a specific API method for updating cart items.

B. vlcCart: Refers to a component or a variable, not an executable action or method for updates.

C. CpqAppHandler: A high-level controller or handler class that orchestrates cart operations, not the specific update method itself.

D. createCart: This method is used to instantiate a new cart, not to modify items in an existing one.

E. getCartsltems: A method to retrieve (GET) item data from the cart, not to update it.

F. getCartsProducts: A method to retrieve product information, not to update items within a specific cart.

H. postCartsltems: This method is used to add new items to the cart, whereas putCartsItems is used to update existing items.

I. checkout: The final step in the cart lifecycle to proceed with order creation, not for item modification.

J. submit: A generic action for form submission or finalization, not the specific cart update operation.

1. Salesforce Developer Documentation

Digital Commerce APIs: The "Update Items in a Cart" API is explicitly defined for this purpose. The documentation specifies the method as PUT and the endpoint as /v3/carts/{cartId}/items. This API is used to "update one or more items in a cart

for example

to change the quantity." This directly corresponds to the putCartsItems action.

Source: Salesforce Developer Documentation

"Digital Commerce APIs"

Section: "Update Items in a Cart".

2. Salesforce Help

Industries CPQ Cart-Based APIs: This documentation clearly distinguishes the roles of different HTTP methods for cart manipulation. It specifies that POST requests to the /items endpoint are for adding items

while PUT requests are for updating existing items. This confirms that putCartsItems is the correct choice for an update operation over postCartsItems.

Source: Salesforce Help Portal

"Industries CPQ Cart-Based APIs Overview".

3. Salesforce Industries CPQ Developer Guide: The guide details the architecture of the cart and its interaction with APIs. It describes the sequence of API calls for a typical Guided Selling session

where changes to quantities or configurations of items already in the cart trigger a PUT call to the cart items resource to ensure the cart state is updated correctly before validation or checkout.

Source: Salesforce Industries CPQ Developer Guide

"Working with the Cart API" section.

In the Vlocity (Salesforce Industries) Context Rule Framework, the initialization policy is specified within a Context Mapping. A context mapping defines how a context dimension is populated with data. To initialize the context at the beginning of a transaction (e.g., loading a cart), a specific mapping is configured to execute an Integration Procedure or a Vlocity Intelligence script. This procedure acts as the "initialization policy," fetching and setting the initial data required for the rules engine to function.

1. Salesforce Industries CPQ Developer Guide

"Context Mappings" section: The official documentation states

"A context mapping defines how a context dimension is populated... You can map a context dimension to a value

an sObject field

a user profile field

or an initialization integration procedure." This explicitly links the initialization procedure (policy) to the context mapping configuration.

2. Salesforce Industries CPQ Administration Essentials (EDU-351) Courseware

"Context Rules Framework" module: This courseware details the components of the framework. It explains that Context Mappings are the mechanism to bring data into the context

and a common pattern is to use an Integration Procedure

specified in a mapping

to run at the start of a process for initialization.

3. Salesforce Help

"Create a Context Mapping": The documentation on creating context mappings describes the different mapping types

including Initialization. It details how to associate an Integration Procedure with this mapping type to populate context dimensions when a process begins.

The statement is incorrect because a rule's "active" status is only a prerequisite for it to be considered for evaluation by the system's rule engine. It does not guarantee execution. A rule will only execute (or "fire") if it is both active and its defined conditions are met. The conditions specify the criteria that the data (e.g., quote lines, product options) must satisfy for the rule's actions to be triggered.

1. Official Vendor Documentation (Salesforce): In the context of Salesforce CPQ

which is central to the IPQ-435 domain

Price Rules are a core feature. The official documentation states that the evaluation process involves checking conditions before applying actions. "Salesforce CPQ evaluates a price rule’s conditions. If they’re met

the rule’s action applies a value to the quote

quote line

or quote line group field that you targeted." This explicitly separates the evaluation of conditions from the rule's existence or active status.

Source: Salesforce CPQ Developer Guide

"Price Rule Fields

" Section on "Conditions Met."

Reference: Salesforce Help

"How Price Rules Work." The documentation outlines the sequence: a rule is evaluated

its conditions are checked

and only then

if the conditions are met

does the action execute.

2. University Courseware (Stanford): General principles of rule-based and expert systems confirm this logic. A rule is typically structured as an "IF-THEN" statement (also known as a production rule). The "IF" part contains the conditions (the antecedent)

and the "THEN" part contains the actions (the consequent). The system's inference engine will only execute the "THEN" part if the "IF" part evaluates to true based on the current data.

Source: Stanford University

CS227B - General Game Playing

Course Notes.

Reference: Lecture notes on "Inference Rules" describe the structure of production systems where a rule p1 ∧ p2 ∧ ... ∧ pn ⇒ q is only fired if all antecedent conditions p1 through pn are satisfied in the knowledge base. An "active" flag is an external control but does not override this core conditional logic.

3. University Courseware (MIT OCW): Courses on artificial intelligence and expert systems formalize the "recognize-act cycle" of rule-based systems. In this cycle

the system first recognizes which rules have their conditions satisfied by the current state of the working memory. Only rules from this "conflict set" are eligible to be fired. A rule that is merely "active" but whose conditions are not met will not be part of the conflict set and therefore cannot be executed.

Source: MIT OpenCourseWare

6.034 Artificial Intelligence

Fall 2010.

Reference: Lecture 4

"Rule-Based Systems

" describes the forward chaining process where the system matches rule antecedents against facts in the database. A rule only fires if a match is found.

When new product bundles are introduced to the Salesforce CPQ product catalog, two primary types of data processing must occur for them to function correctly.

First, the bundle's structure (parent product, features, and options) must be processed. This is accomplished by running the Product Hierarchy Maintenance batch job, which flattens the bundle data to ensure optimal performance within the Quote Line Editor (QLE).

Second, the new products within the bundle must have active prices in a pricebook to be selectable on a quote. The Refresh Pricebook job is used to synchronize pricing data, ensuring that all pricebook entries are current and correctly reflected, which is a critical step after adding new products or modifying prices.

1. Salesforce CPQ Administrator Guide

"Salesforce CPQ Maintenance Jobs": This official guide details the necessary jobs for maintaining a CPQ org.

For Answer C: It states

"Product Hierarchy Maintenance: Processes product bundle data to improve quote line editor performance. We recommend running this job after you create or change a product bundle." This directly confirms the necessity of this job.

For Answer B: It describes the "Refresh Price Book" job: "When you change a price book entry

run this job to sync the change with your price books." This confirms its role in synchronizing pricing data

a necessary step for new products.

Reference Location: Salesforce Help

Salesforce CPQ

"Salesforce CPQ Maintenance Jobs".

2. Salesforce CPQ Implementation Guide

"Post-Installation Steps": This guide outlines initial setup and ongoing maintenance tasks.

For Answer C: It emphasizes running the Product Hierarchy Maintenance job as a key step after product setup. "To make sure your product bundles perform well in the quote line editor

run the product hierarchy maintenance job."

Reference Location: Salesforce Help

Salesforce CPQ

"Set Up Products"

"Product Setup Considerations".

In Salesforce Industries CPQ, promotions are constructed by defining discounts or adjustments that apply to specific items from the product catalog. The system allows for granular control over what a promotion targets. This includes applying a promotion to a single, standalone product, a collection of products grouped as a bundle, or even more complex structures such as a bundle that is nested within another parent bundle. These entities serve as the foundational building blocks for defining the scope and application of a promotional offer within a quote or order.

1. Salesforce Help

Industries CPQ Developer Guide

"Promotions": The documentation outlines that promotions are created and then associated with products in the catalog. It states

"You can associate a promotion with one or more products... When you add a product that has a promotion associated with it to the cart

the promotion is applied automatically." This confirms that products are the core building block. Since bundles and nested bundles are configured as products in the catalog

they are also valid targets. (Reference: Salesforce Help Portal

Industries CPQ Developer Guide

Promotions section).

2. Salesforce Help

Industries CPQ Developer Guide

"Bundles": The guide details the creation of product bundles

which are treated as a single product entity (with a specific structure) in the catalog. Promotions can target the parent bundle product

thereby applying to the bundle as a whole. This supports the inclusion of bundles and

by extension

nested bundles as promotional targets. (Reference: Salesforce Help Portal

Industries CPQ Developer Guide

Product Bundles section).

The Vlocity Cart user interface is an integrated experience composed of several primary components. The Cart Header provides cart-level information and actions (e.g., Checkout, Save). The Product List is the component, often displayed alongside the cart, that shows the catalog of available products for selection. The Cart Line Items section is the core of the cart, displaying each product that has been added, along with its quantity and price. Finally, the Total Bar, typically at the bottom, summarizes all charges, including subtotals, adjustments, and the final price. These four components constitute the primary user interface for cart management in Vlocity Digital Commerce.

1. Salesforce Industries Digital Commerce LWC Reference: The documentation describes the standard components used to build the cart experience. The vlocityins/cart LWC encapsulates the header

line items

and totals bar. It is designed to be used on a page alongside the vlocityins/productList LWC

which displays the selectable products. This confirms the "Product List" is a primary component of the overall UI. (Salesforce Help

Digital Commerce API and LWC Reference

Sections on cart and productList components).

2. Salesforce Industries Communications

Media

and Energy (CME) Developer Guide: The guide for setting up the LWC-based cart illustrates a standard page layout where a product list is on one side of the page and the cart (with its header

line items

and totals) is on the other. This visual and structural layout establishes these as the primary components of the experience. (Salesforce Help

Set Up the LWC-Based Cart for CME).