Salesforce Certified CPQ Specialist Practice Test Questions, Exam Dumps

Practice Exams:

View All

Certified CPQ Specialist Salesforce Practice Test Questions and Exam Dumps

Question 1

A user needs to amend a contract and change prices to reflect new discounts for existing active subscriptions and assets. How should the user achieve this?

A. Change the status of the contract to Draft. Make price changes on the original quote used to generate the contract and check Contracted on the Opportunity again.
B. Create a Price Book with Price Book Entries to reflect the new prices. Populate the Contract Amendment Price Book ID field with the new Price Book ID to generate Amendment Lines with new prices.
C. Clone the Quote Lines which need to be updated. Modified the desired discounts on the cloned Quote Lines. Update the original Quote Lines to a Quantity of zero.
D. Change the values for Net Price on the subscription or Price field on the asset. Amend the contract and use Refresh Prices.

Answer: B

Explanation:

This question focuses on how to properly amend a contract in Salesforce CPQ when there is a need to update prices for active subscriptions or assets, such as applying new discounts. In a CPQ process, managing pricing updates during amendments must align with how the system handles pricing logic and contract structure.

Option A is not the correct approach. Once a contract is generated and the quote is contracted, the contract becomes a record of historical transaction terms. Changing its status back to "Draft" and attempting to modify the original quote would break the integrity of the process. Additionally, checking "Contracted" on the Opportunity again does not align with Salesforce CPQ’s best practices for handling amendments and renewals.

Option C involves cloning quote lines, modifying discounts, and setting original lines to zero. While this is a technique sometimes used to simulate removal and re-addition of products, it is manual and not scalable. It also doesn't leverage the built-in amendment framework that Salesforce CPQ provides and lacks automation tied to pricing rules or price books. Therefore, it's not the recommended approach for systematic amendments involving new pricing.

Option D proposes direct changes to subscription prices or asset prices and then using the “Refresh Prices” feature. However, CPQ does not support modifying the Net Price or asset Price fields directly to influence pricing during an amendment. These fields are meant to be calculated and not edited manually during a contract’s lifecycle. Also, the “Refresh Prices” functionality cannot generate new prices based on updated pricing rules or discount strategies unless they're tied to a new price book, making this approach ineffective for the scenario described.

Option B is the correct approach. In Salesforce CPQ, when amending a contract and updating prices for active subscriptions or assets, the proper method is to create a new Price Book that includes the updated pricing, including any new discount logic. Then, during the amendment process, the system can be directed to use this new pricing structure by populating the Contract Amendment Price Book ID field with the ID of the new price book. This ensures that amendment quote lines reflect the updated prices and discounts as intended. This method aligns with CPQ’s structured and automated approach to pricing during amendments, preserving system consistency and ensuring correct price calculations.

Therefore, the appropriate and system-supported way to handle this use case is to leverage a custom price book and populate the Contract Amendment Price Book ID field, as stated in option B.

Question 2

Universal Containers wants the Square Footage value selected in a bundle's Configuration Attribute to persist when the bundle is reconfigured in a Renewal Quote. Currently, this value resets to its default, forcing sales reps to re-enter it.

How can an Admin ensure the value is retained automatically?

A. Set the Renewed Asset lookup field on the renewal Quote Lines to reference the original Assets.
B. Create a Twin Field of the Square Footage field on the Quote Line object.
C. Set the Renewed Subscription lookup field on the renewal Quote Lines to reference the original Subscriptions.
D. Create a Twin Field of the Square Footage field on the Asset and Subscription objects.

Answer: D

Explanation:
This scenario relates to Salesforce CPQ’s behavior when handling configuration attributes during the renewal process. Configuration attributes are fields that allow users to input values during product configuration and can influence how the bundle behaves — for instance, filtering product options. In this case, the Square Footage configuration attribute determines which product options are compatible and should be shown or hidden.

The issue is that when a renewal quote is created, the original Square Footage value is lost, and it defaults to a pre-set value. This adds unnecessary manual work and increases the risk of user error.

To solve this, we need to understand how Salesforce CPQ handles data persistence between original quotes and renewal quotes. CPQ uses a concept called Twin Fields to preserve data across lifecycle transitions — from quotes to assets or subscriptions, and back to quotes during renewals.

A Twin Field is a field that exists with the same API name and data type across related objects — like Quote Line, Asset, and Subscription. When a field is configured as a Twin Field, Salesforce CPQ automatically maps and copies the value from one object to its counterpart during operations like order generation or renewal quote creation.

In this case, since we want to carry over a value (Square Footage) from a prior configuration into a renewal quote — and that value lives in a configuration attribute (typically linked to Asset or Subscription after ordering) — the appropriate strategy is to ensure that this field exists with the same name on both the Asset and Subscription objects. That way, during the renewal process, CPQ will transfer the value automatically from the original Subscription or Asset to the new Quote Line and, ultimately, back into the Configuration Attribute.

Let’s analyze the other options to clarify why they aren’t correct:

Option A: Setting the Renewed Asset lookup field does help link renewal quote lines to original assets but doesn't by itself copy configuration attribute values. It helps establish the relationship for pricing and other asset-related logic but not for custom field value propagation.
Option B: Creating a Twin Field only on the Quote Line would not help in renewals unless the data is also available on the Asset or Subscription from which the renewal is derived. Since the configuration attribute value doesn’t persist in Quote Lines beyond the initial quote, this field wouldn’t help the renewal quote inherit the correct value.
Option C: Like Option A, setting the Renewed Subscription lookup ensures that the renewal quote lines are connected to the original subscriptions. However, this alone doesn't control field value propagation.
Option D: This is the correct approach because Salesforce CPQ will detect matching fields on Asset and Subscription objects and use them to carry over values automatically. If the Square Footage configuration attribute maps to a field of the same name on those objects, then on renewal, the system will repopulate the attribute accordingly.

Thus, the correct answer is D.

Question 3

Universal Containers allows clients to negotiate a discount for Product A until a specified date upon Contract activation.

Which three fields on the Contracted Price record should be configured to satisfy this requirement? (Choose three.)

A. Effective Date
B. Expiration Date
C. Product
D. Contract
E. Discount

Answer: A, B, E

Explanation:

This question focuses on the proper configuration of a Contracted Price record in Salesforce CPQ to enforce a temporary discount for a specific product upon contract activation. Universal Containers’ requirement implies that a client is eligible for a discounted price for Product A, but only until a specific expiration date—after which the discount no longer applies.

Salesforce CPQ provides the Contracted Price object, which allows admins to define custom pricing rules for products at the account or contract level. These pricing rules can override standard prices, and they support time-based configurations through Effective Date and Expiration Date fields.

Let’s evaluate each option in detail:

Option A – Effective Date:
This field sets the start date for when the Contracted Price becomes applicable. In this case, since the discount is valid after contract activation, the Effective Date is essential to define the beginning of the discount period. Without this, CPQ wouldn’t know when to start applying the discounted price.

Option B – Expiration Date:
This field defines the end date of the Contracted Price’s validity. It directly satisfies the requirement of limiting the discount to a specific end date. Without setting this field, the discount might be considered perpetual or open-ended, which goes against the business requirement.

Option C – Product:
While this seems relevant at first glance because the discount is for Product A, the Product field is actually not required on a Contracted Price record. Instead, a Contracted Price can be defined at the Account, Product, or Contract level depending on your pricing model. If you’re applying the discount for a product in general for a specific account, and you're doing it through a Contract, the Contract field will carry the necessary context. In some configurations, Product is used, but in this case, it is not strictly necessary.

Option D – Contract:
This field links the Contracted Price to a specific contract. Although useful in some pricing scenarios, this is not required just to define the discount and its time limits. The pricing rule itself is determined by the Effective Date, Expiration Date, and Discount fields.

Option E – Discount:
This is the core of the entire configuration. Without defining the discount amount or percentage, CPQ would not know how to adjust the product price during the specified timeframe. This is one of the most essential fields for this use case.

In summary, the three essential fields that must be configured are:

Effective Date, to define the start of the discount
Expiration Date, to enforce the end of the discount period
Discount, to specify the amount or percentage of the negotiated discount

The Product and Contract fields may be useful depending on broader configuration needs, but they are not explicitly required to meet the basic requirement stated in the question. Thus, the correct choices are A, B, and E.

Question 4

An Admin wants to allow users to select product options and specify option quantities during the bundle configuration process.

Which three Configuration Type values would support this behavior? (Choose three.)

A. Configurable
B. Required
C. Allowed
D. None
E. Disabled

Answer: A, B, C

Explanation:
Salesforce CPQ provides different Configuration Type settings for product bundles that define how users interact with the configuration interface. The Configuration Type field controls whether a product can be configured and how much flexibility the user has when adding or modifying bundle options.

In this case, the Admin’s goal is to let users choose product options and define option quantities through the configuration UI. Let’s explore what each Configuration Type means and how it relates to that requirement:

A. Configurable
This is the most flexible setting. When the Configuration Type is set to Configurable, the product bundle opens the configuration interface automatically when added to a quote. Users can select or deselect product options and modify their quantities. This configuration meets the requirements precisely and is often used for optional configurations.

B. Required
When the Configuration Type is set to Required, the configuration UI is also triggered automatically when the bundle is added to a quote. The key difference from Configurable is that users must interact with the configurator before proceeding — i.e., they must select at least the required options. Like Configurable, it allows users to select options and set quantities, so this also fulfills the requirements stated in the question.

C. Allowed
This Configuration Type gives users the option to configure the product, but it does not automatically launch the configurator when the product is added to a quote. Users can choose to configure it by clicking the “Configure” button manually. Inside the configurator, they can select/deselect options and define quantities. Since it provides full access to configuration when triggered by the user, this setting is suitable as well.

Now, let’s review the two incorrect options:

D. None
With this Configuration Type, no configuration is allowed. The product is treated as a standalone item without any options, or with all its options pre-selected and locked. Users cannot interact with the configurator or change option quantities. Therefore, this setting does not meet the requirements.

E. Disabled
When set to Disabled, the configurator is completely inaccessible for the bundle. The configuration interface will not launch at all, even manually. This is used when configuration is not permitted under any circumstances. Therefore, this also does not meet the requirement.

In summary, only Configurable, Required, and Allowed allow users to interact with the configuration interface to choose options and define quantities. These types provide varying degrees of user control and configurator automation but all satisfy the core requirement.

The correct answers are A, B, C.

Question 5

Universal Containers (UC) has a required Configuration Attribute for Color on all containers it sells. UC wants to display the Color of the containers in the output document.

On which objects will the Admin need to create the Color field to meet this requirement?

A. Product, Product Option
B. Product, Quote Line
C. Quote Line, Asset
D. Product Option, Quote Line

Answer: D

Explanation:

In Salesforce CPQ, a Configuration Attribute such as "Color" is typically used during the product configuration process when a sales rep is customizing a bundle or product. Configuration Attributes are displayed during product selection and can be passed to the Quote Line so they appear in both internal CPQ processes and in external-facing documents like quotes or proposals.

Let’s break down why Product Option and Quote Line are the correct objects for the Color field in this scenario:

Product Option:
This object represents a child product within a bundle. If the Color is something a user selects when configuring a container (and containers are likely sold as bundles or have selectable options), then the Product Option is where the Color Configuration Attribute is defined. The field is needed here because the CPQ engine will associate it with a specific component of the bundle.
Quote Line:
The Quote Line is where information from the configuration process is ultimately captured and stored for quoting and output. If UC wants to show the selected Color on the output document (like a PDF quote), the field must exist on the Quote Line, because that is what gets merged into templates using Quote Line merge fields.

Let’s review why the other options are incorrect:

A. Product, Product Option:
While the Product object holds general product information and the Product Option supports configuration attributes, putting the Color field on the Product won’t help in this case because the Color is a dynamic, user-selected value—not a fixed attribute of the product itself.
B. Product, Quote Line:
This is close but still not ideal. Again, the Product object would not hold user-defined or configured values like Color. You need to track the chosen Color per quote, and for that, the Product Option is the correct source.
C. Quote Line, Asset:
The Asset object comes into play after a sale is made and the product becomes a serviceable item. It is not involved during the quoting process. Including the Color field on Asset would help in post-sale tracking, but it does not help with showing the Color in quote documents.

Therefore, placing the Color field on both the Product Option and the Quote Line ensures that it can be selected during configuration and displayed during quoting. This dual placement also supports CPQ best practices for handling configuration attributes.

In summary, for Universal Containers to allow users to select a Color during configuration and then display that selected Color on quote output documents, the Color field must be created on both the Product Option and the Quote Line objects. This ensures smooth data capture during the configuration and quoting processes.

Question 6

Sales reps have complained that using the Calculate button in the Quote Line Editor after every change is slowing down their workflow. Management wants the calculation process to happen automatically after each change.

Which Managed Package setting should the Admin enable to achieve this?

A. Enable Quick Calculate
B. Calculate Immediately
C. Use Inactive Prices
D. Use Legacy Calculator

Answer: B

Explanation:
In Salesforce CPQ, the Quote Line Editor (QLE) is the interface that allows sales reps to modify quote lines, quantities, discounts, and more. By default, when reps make changes to a quote in the QLE, the system does not automatically calculate the new totals or pricing details until the user manually clicks the Calculate button. This manual calculation is designed to improve performance in environments with complex pricing logic or many quote lines.

However, in environments where speed and efficiency are more important than limiting processing overhead, the Admin can enable a managed package setting to force the system to perform automatic calculations after each change in the QLE. This feature is especially useful when users frequently make individual changes and want to see real-time pricing or total updates.

Let’s break down each of the provided options to see which one enables that behavior:

A. Enable Quick Calculate
This setting is used to enable a lightweight version of the calculate operation, which can be triggered via a custom action button. While it offers performance improvements in some scenarios, it still requires user interaction. It does not make calculations happen automatically after every change, so this is not the right answer.

B. Calculate Immediately
This is the correct answer. The Calculate Immediately setting, when enabled in the CPQ managed package settings, ensures that the system automatically performs calculations every time a change is made in the Quote Line Editor. This eliminates the need for the sales rep to manually press the Calculate button. It is ideal for smaller or less complex quotes where system performance won’t be significantly affected by automatic recalculations.

C. Use Inactive Prices
This setting allows the system to reference and use prices from inactive price book entries. It is completely unrelated to quote line calculations and would not affect whether calculations are manual or automatic.

D. Use Legacy Calculator
This setting reverts CPQ to use its older calculation engine instead of the current one. This might affect how calculations are performed in general, but it does not control whether calculations are done automatically. Also, the legacy calculator is not recommended for most orgs, especially those using newer CPQ features.

Therefore, to meet the request from management and improve the user experience for sales reps by automatically triggering calculations after each change, the Admin should enable the Calculate Immediately managed package setting.

The correct answer is B.

Question 7

An Admin is creating a Product Rule with an Advanced Condition. How should the Admin reference a specific Error Condition record in the text of the Advanced Condition field?

A. Value of the Index field
B. API name of the field in the Tested Field
C. Salesforce ID of the Error Condition record
D. Value of the Condition # field

Answer: D

Explanation:

When using Advanced Conditions in Salesforce CPQ Product Rules, the system allows you to define complex logical expressions that evaluate multiple Error Conditions together. These advanced logical statements enable more granular control by using boolean logic (like AND, OR) to define how conditions should relate to each other.

Each Error Condition that is part of the Product Rule is assigned a number in the Condition # field. This number is critical when you're using the Advanced Condition text box because it serves as the reference identifier for each individual condition in the logic formula.

For example, if you have three Error Conditions with Condition # values of 1, 2, and 3, and you want to say “Condition 1 AND (Condition 2 OR Condition 3),” you would write the Advanced Condition as:

1 AND (2 OR 3)

This syntax tells the CPQ engine how to evaluate the rule logically. You are not referencing field API names, record IDs, or the index field directly—only the Condition # field values.

Let’s now explain why the other options are incorrect:

A. Value of the Index field:
The Index field is used internally for ordering but is not used in logical evaluation within the Advanced Condition. It plays no part in the logical syntax.
B. API name of the field in the Tested Field:
This is used within individual Error Condition records to define what field is being evaluated, but it is not how you build logic between multiple conditions in an Advanced Condition formula.
C. Salesforce ID of the Error Condition record:
Salesforce IDs are never used in the logic text of Advanced Conditions. These IDs are unique and long strings, not practical or intended for human-readable logic statements.

Because of this, the only correct way to reference and construct logic for multiple error conditions in an Advanced Condition field is to use the Condition # values assigned to each Error Condition record.

Therefore, the correct approach is to assign logical references using the Condition # values and construct boolean expressions accordingly. This approach ensures your product rule evaluates all relevant error conditions in the correct sequence and relationship, supporting advanced validations or dynamic bundle behaviors.

Question 8

An Admin wants to organize Product Features in the Configurator into groups that appear as separate tabs to provide a second level of categorization. What step should the Admin take to implement this?

A. Set Option Layout to Tabs on the Product.
B. Set and choose a Category on the Feature.
C. Set Option Layout to Tabs on the Feature.
D. Set and choose a Group on the Feature.

Answer: D

Explanation:
In Salesforce CPQ, product configuration is managed using Product Bundles, which contain Features and Options. To improve usability, especially for complex bundles with many features, admins can organize features into groupings. One way to do this is to display related features in separate tabs within the configurator. This is particularly helpful in presenting a clean and structured user interface when configuring large bundles.

In this scenario, the Admin is trying to introduce a second level of categorization—that is, organizing Features (not Options) into groupings, with each group shown as a separate tab during configuration. Let’s analyze each answer option to identify the correct one.

A. Set Option Layout to Tabs on the Product
This setting applies to how Options (not Features) are displayed when configuring a product. It organizes Options under a specific Feature into tabs or sections. This would not affect how Features themselves are grouped, so it doesn’t solve the problem of organizing features into tabs.

B. Set and choose a Category on the Feature
Salesforce CPQ does support Feature Categories, but categories are used mainly for filtering and visual identification. They are not intended for creating tabs or second-level groupings. Choosing a category on a Feature does not change how features are grouped or displayed in tabs in the configurator.

C. Set Option Layout to Tabs on the Feature
This setting defines how Options under a single Feature are displayed. For example, if a Feature has multiple Options, setting the layout to “Tabs” affects how those Options are organized—not the Feature itself. Again, this doesn’t address the grouping of Features into tabs.

D. Set and choose a Group on the Feature
This is the correct answer. In Salesforce CPQ, Features can be assigned a Group value, and when multiple Features share the same Group name, Salesforce CPQ will display those Features together under a tab named after that Group. This allows admins to group Features logically—for example, “Networking,” “Storage,” and “Security”—and have each group displayed as a tab in the configurator. It provides the second-level categorization the Admin is looking for.

By using the Group field on the Feature object, admins can define how the features are clustered and presented. All Features with the same Group name will be placed under the same tab, making it easier for users to navigate complex product configurations.

In conclusion, to display Product Features as tabs in the configurator for better organization, the Admin must set and choose a Group on each Feature.

The correct answer is D.

Question 9

An annual subscription for Product A sells for $100 and has a Term Discount Schedule established on its Product record. A volume-based Discount Schedule is related to a Contracted Price that applies to Product A. Product A is added to a Quote for an Account that uses the Contracted Price. As quoted, Product A qualifies for a 10% volume-based discount and a $20 term-based discount.

Which values for Special Price and Regular Price are expected if the Quote’s Subscription Term is 24 months?

A. Special Price = $90, Regular Price = $140
B. Special Price = $100, Regular Price = $140
C. Special Price = $100, Regular Price = $144
D. Special Price = $72, Regular Price = $144

Answer: D

Explanation:

This question evaluates how Regular Price and Special Price are calculated in Salesforce CPQ when both Contracted Prices and Discount Schedules (Term and Volume-based) apply. Let’s carefully break it down.

We’re told:

The base List Price for Product A is $100 annually.
The Quote’s Subscription Term is 24 months (i.e., 2 years).
There is a Term Discount Schedule on the Product record, giving a $20 discount for 24 months.
There is a Volume Discount Schedule on the Contracted Price, giving a 10% discount.
The product qualifies for both discounts.

Let’s walk through the pricing logic step-by-step using Salesforce CPQ’s calculation flow:

1. Regular Price

Regular Price is the price before any additional discounts are applied. It's typically based on the List Price and the Term.

Since the base price is $100/year, for a 24-month (2-year) term:

Base price before discounts: 100 x 2 = $200

Then, apply the Term Discount Schedule, which gives a $20 discount:

200 – 20 = $180

Therefore, the Regular Price is $180.

But the question gives options that suggest Regular Price is $144. This indicates that there's a 24-month price built into the Term Discount Schedule that reduces the annual rate from $100/year to $72/year (i.e., $144 total).

So instead of subtracting $20 from $200, we now interpret it this way:

If the Term Discount Schedule defines a $72/year rate (because $144/2 = $72), then:

Regular Price for 24 months = $144

This is in line with how Term Discount Schedules typically override the regular rate depending on subscription term. So yes, Regular Price = $144.

2. Special Price

Special Price is the price after applying additional discounts, such as volume-based or contracted pricing.

In this case, the volume-based discount is 10% and applies on top of the Term-based discounted price.

So:

Take Regular Price of $144
Apply 10% volume discount → 144 x 0.10 = 14.4
144 – 14.4 = $129.60

But none of the options mention 129.60. So let’s reevaluate. Are we missing the distinction between Regular Price and Special Price here?

Let’s assume:

Regular Price = $144 (after term discount)
Special Price = after volume discount

10% of 144 = 14.4
144 – 14.4 = 129.6

Now consider List Price may have already dropped to $80 before applying the 10%—but we’re told term discount is $20, so perhaps we’re to use $100 – $20 = $80, then 10% off gives $72.

But again, we are given that the Term Discount applies $20, and volume discount is 10%. Let’s try this logic:

Base annual list price: $100
For 24 months: $100 x 2 = $200
Apply Term Discount: $200 – $20 = $180
Apply Volume Discount: 10% of 180 = 18
Final price: $180 – $18 = $162

Again, this doesn’t match the options given.

Wait. Look at Option D:
Special Price = $72, Regular Price = $144

That implies:

Regular Price (post term discount) = 144
Volume discount is applied on a per-year basis or adjusted differently

144 x 0.10 = 14.4
144 – 14.4 = 129.6 — not 72.

But try this:
Annual base = $100
If $20 is the full discount for the 2-year term, that’s $10/year
So net price per year = $90
Then apply 10% volume discount → 90 – 9 = 81
81 x 2 = $162 — again doesn’t give 72

The only way to arrive at $72 is if: