Sign in
Home/Salesforce/Certified CPQ Specialist/Free questions

Certified CPQ Specialist — Free Practice Questions

10 free sample questions from a bank of 235, with the correct answers and explanations. No signup required — start practising right now.

1A 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?
  • 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.
  • 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.
  • 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.
  • Change the values for Net Price on the subscription or Price field on the asset. Amend the contract and use Refresh Prices.
Answer: C

The short version

C — Clone the lines, discount the clones, and zero the originals. Amendment quotes cannot change discounts on existing subscription lines, so the stranded discount is replaced by cloning and re-discounting while the original is set to zero quantity.

Key concepts in this question

  • Amendment price protection: CPQ locks Additional Discount and standard price fields on amendment lines sourced from existing subscriptions, because that pricing already lives on the contract subscriptions.
  • Clone and zero pattern: Cloning preserves history while the new line carries the fresh discount and the original at zero quantity issues the credit for the remaining term.
  • Refresh versus rewrite: Refresh Prices pulls current price book values for net-new lines only; it does not unlock discount edits on lines tied to existing subscriptions.

Why C is correct

Salesforce help states that changing the discount or standard price fields of existing lines on amendment quotes is not supported, since that data already exists on subscriptions under the contract and cannot change retroactively. Cloning creates a net-new line that is free to carry the newly agreed discount, while setting the original line quantity to zero generates the correct prorated credit for the replaced service.

Why the others are wrong

  • A. Drafting the contract and rechecking Contracted does not unlock discount edits on existing amendment lines.
  • B. A new amendment price book affects net-new lines, not the locked discounts on lines sourced from existing subscriptions.
  • D. Editing Net Price on the subscription and refreshing cannot override the amendment lock on existing line discounts.

Certified-CPQ-Specialist exam tip

Existing amendment lines never accept new discounts: clone the line, discount the clone, zero the original.

2Universal 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?
  • Product, Product Option
  • Product, Quote Line
  • Quote Line, Asset
  • Product Option, Quote Line
Answer: D

The short version

D — Put Color on Product Option and twin it to Quote Line. Configuration Attributes capture option-level choices, so the field must exist where the choice is made plus a matching Quote Line field to carry it to the output document.

Key concepts in this question

  • Product Option attribute home: Product Option holds the Color value entered during configuration for each container option in the bundle.
  • Twin field pattern: A Quote Line field with the same API name receives the option value automatically, making it available to line editor columns and templates.
  • Output document sourcing: Quote templates read Quote and Quote Line fields, not live configurator state, so without the twin the Color never reaches the document.

Why D is correct

Trailhead attribute exercises teach that an attribute value captured on the option needs a twin field on the Quote Line to persist it to the quote. Creating Color on Product Option gives the configurator a place to store the required choice, and the twin on Quote Line flows it into the line record that templates and the editor actually render. Product-level fields alone describe the parent rather than the chosen option, and Asset pairing serves post-sale records rather than quote output. So the Product Option plus Quote Line pairing in D is the minimal complete plumbing for showing Color on the document.

Why the others are wrong

  • A. Product plus Product Option stores the choice but leaves no Quote Line carrier for templates and the editor.
  • B. Product plus Quote Line misses the option-level capture point where the Color choice is actually entered.
  • C. Quote Line plus Asset helps post-sale records, not configurator capture and quote document display.

Certified-CPQ-Specialist exam tip

Attribute to document means twin it: capture on Product Option, carry on Quote Line with identical API name.

3Universal Containers (UC) sells licenses set up as subscription Products. A UC sales rep has closed an Opportunity associated to a Quote with a Subscription Term of 36 months. The sales rep and a customer have agreed to a Quantity of 100 licenses for the term of the Contract. The customer wants to decrease the license count to 80 licenses after the first year. After the second year, the Contract will be amended again to increase the license count to 120 licenses. After the sales rep amends the Contract to incorporate these changes, what are the respective Quantities of: • The original Subscription • The first amended Subscription • The second amended Subscription
  • 100, 80, 120
  • 80, 0, 40
  • 100, −20, 40
  • 120, −20, 40
Answer: C

The short version

C — Original 100, first amendment minus 20, second amendment plus 40. Amendment subscriptions record only the change versus the prior state, so the three records read 100 and negative 20 and positive 40 while the customer experiences 100 then 80 then 120.

Key concepts in this question

  • Amendment delta model: Each amendment subscription stores the difference from the previous quantity, not the resulting total, which keeps contract history auditable.
  • Net quantity math: Starting at 100, a drop to 80 is recorded as minus 20, and the later rise to 120 from 80 is recorded as plus 40.
  • Total versus record view: Sales users see effective totals of 100 then 80 then 120, but the underlying subscription rows in C show the 100 and minus 20 and 40 deltas.

Why C is correct

Contract amendment design creates new subscription records that represent only the incremental change, which is why the reference case stresses talking about the difference rather than the after quantity. The original subscription holds 100 for the full term. The first amendment for the year-two reduction to 80 contributes minus 20, bringing the running total to 80. The second amendment for the year-three increase to 120 from 80 contributes plus 40, bringing the running total to 120.

Why the others are wrong

  • A. Lists effective totals the customer sees, not the delta quantities stored on the amendment subscriptions.
  • B. Misstates both the starting point and the deltas, producing nets that never reconcile to 80 then 120.
  • D. Starts from 120 and misstates the second delta, which breaks the running total math from the 100 baseline.

Certified-CPQ-Specialist exam tip

Amendment quantity questions ask for deltas: new total minus old total is the stored value, negatives allowed.

4What are two ways Salesforce CPQ Advanced Approvals support obtaining approval from a group in a single Approval Step? (Choose two.)
  • Any group member may approve.
  • Approval must be obtained from one group member at a time.
  • Smart Approvals can exclude group members below the approval threshold.
  • All group members must approve.
Answer: A, D

The short version

AD — Group approval uses Unanimous mode with two threshold styles. Advanced Approvals lets one step collect approval from a defined group either by first response or by full consensus, and both A and D describe those supported settings.

Key concepts in this question

  • Advanced Approvals: Salesforce CPQ approval engine built on Approval Rule, Approval Chain, and Approver records for flexible routing.
  • Approval Step with group: A single step can target multiple approvers through a queue, public group, or set of Approver records.
  • Unanimous setting: Controls whether the step requires every assigned approver or stops after the first approval or rejection.
  • First-responder approval: Useful when any qualified manager can decide, avoiding bottlenecks during quotes with time pressure.
  • Full-consensus approval: Useful for high-risk discounts or terms where every stakeholder must sign off before contracting.

Why AD is correct

A is correct because an Approval Step assigned to a group can be configured so that any single group member approving satisfies the step and moves the chain forward. D is correct because the same step can instead be configured as unanimous, requiring all group members to approve before the quote is approved. Both behaviors come from the Unanimous flag on the approval assignment, so one step supports either first-member or all-member semantics without creating separate steps.

Why the others are wrong

  • B. Sequential one-at-a-time approval describes serial steps or chains, not the parallel group behavior asked for in a single step.
  • C. Smart Approvals auto-approves quotes that stay within thresholds, but it does not define how group members vote within one manual step.

Certified-CPQ-Specialist exam tip

Remember Unanimous unchecked means first response wins, while Unanimous checked means everyone must approve — link that flag to group steps.

5If a manager is taking a leave of absence, how can the Admin using Advanced Approval ensure that another manager will receive Approval requests during the period in which the original manager is absent?
  • On the original manager's Approver record, reference a different manager's Approver record in the Next Approver lookup field. Clear the Next Approver lookup field once the original manager returns from leave.
  • On the original manager's Approver record, set the Delegated Approver lookup field to reference a different manager's Approver record, and set the Delegation End field for the date of the original manager's return.
  • Create a new Approver record, with the Group ID field set to the ID of a Public Group that contains all of the managers. On the original manager's Approver record, click the Replace button and select the new Approver record.
  • Create an Approval Rule with an Effective Start Date and Effective End Date spanning the absence. Populate the Approver field of the rule with the substitute Approver, then add the rule to the existing Approval Chain as the first step.
Answer: B

The short version

B — Temporary absence is covered by Delegated Approver with an end date. The Approver record supports delegation so requests reroute automatically during leave and revert afterward without rebuilding rules or chains.

Key concepts in this question

  • Approver record: Represents an eligible approver in Advanced Approvals, linked to a user and usable in Approval Rules.
  • Delegated Approver: Lookup on the Approver record that redirects assigned approval requests to a substitute user.
  • Delegation End: Date field that bounds the delegation period so routing returns to the original manager automatically.
  • Approval Chain continuity: Existing rules and chains stay intact while only the assignee changes during the absence window.
  • Leave coverage: Common admin task where no new rules, groups, or replacement records should be needed for short absences.

Why B is correct

B is correct because setting Delegated Approver to the covering manager plus a Delegation End date tells Advanced Approvals to send that approver's requests to the substitute only through the leave period. The platform handles rerouting and expiry natively. This preserves audit history, keeps chains unchanged, and avoids duplicate approver or rule maintenance.

Why the others are wrong

  • A. Next Approver defines chain succession after approval, not temporary substitution, and manual clearing is error-prone and not date-driven.
  • C. Creating a group Approver plus Replace is overkill for short leave and changes approval membership rather than delegating one person.
  • D. A dated Approval Rule for the substitute alters chain logic and ordering instead of simply rerouting one approver's queue.

Certified-CPQ-Specialist exam tip

For leave think Delegated Approver plus Delegation End — Next Approver is for chain order, delegation is for absence coverage.

6Universal Containers wants to automatically generate Contracted Prices for certain Products in its catalog across all Accounts whenever a Contract is created. Which field should the Admin adjust to ensure that the desired Products have Contracted Prices created for all Accounts?
  • Set the Generate Contracted Prices field on the Quotes on these Accounts.
  • Set the Generate Contracted Price picklist on the desired Product records.
  • Set the Generate Contracted Prices field on the Opportunities on these Accounts.
  • Set the Generate Contracted Price picklist on the desired Quote Lines before creation.
Answer: A

The short version

A — Auto-create Contracted Prices across all accounts from the Quote flag. When contracts are created from quotes, the Generate Contracted Prices option drives Contracted Price creation, and setting it where quotes for these accounts originate covers the catalog-wide requirement.

Key concepts in this question

  • Contracted Price: Account-specific price that overrides list or standard pricing for a product on future quotes.
  • Contract creation flow: Contracts are typically generated from a quote, carrying quote lines into subscriptions and contracted pricing.
  • Generate Contracted Prices: Flag that triggers automatic Contracted Price records upon contracting rather than manual entry.
  • Catalog-wide coverage: Requirement here spans certain products across all accounts, not a one-off negotiated price.
  • Product versus Quote level: Product flags control per-product behavior while quote-level generation governs creation during contracting.

Why A is correct

A is correct because setting Generate Contracted Prices on the Quotes for these accounts makes Contract creation generate Contracted Prices automatically. The quote-to-contract flow is the creation point, so enabling generation on originating quotes covers the catalog across accounts without manual records.

Why the others are wrong

  • B. A product-level picklist alone does not trigger creation at contract time across every account in this quote-driven contracting flow.
  • C. Opportunity-level flags do not drive CPQ contracting logic, since Contracted Prices are created from the quote and contract objects.
  • D. Setting a picklist on individual Quote Lines before creation is manual and line-scoped, not automatic across accounts and products.

Certified-CPQ-Specialist exam tip

Link auto Contracted Prices to the contracting source — when creation happens from quotes, look for the Generate flag on the quote path.

7Which three CPQ pricing functionalities contribute to Regular Unit Price during the price calculation sequence? (Choose three.)
  • Prorate Multiplier
  • Target Customer Amount
  • Additional Discount Fields
  • Contracted Price
  • Discount Schedules
Answer: A, D, E

The short version

ADE — Regular Unit Price blends proration, contracted pricing, and schedule discounts. The calculation sequence applies time-based proration and account-specific or volume pricing before partner or subscription adjustments, so only those three feed Regular Unit Price.

Key concepts in this question

  • Regular Unit Price: Intermediate price after base adjustments but before partner discounts, customer discounts, and net calculations.
  • Prorate Multiplier: Adjusts price for partial periods or segmented terms based on start and end dates.
  • Contracted Price: Negotiated account price that replaces list price when present and applicable.
  • Discount Schedule: Tiered or range-based discount driven by quantity or amount thresholds.
  • Calculation sequence: Ordered CPQ pricing waterfall where each stage has defined inputs and later stages build on earlier results.

Why ADE is correct

A is correct because Prorate Multiplier scales the unit price for partial-term or multi-segment quotes during the Regular Unit Price stage. D is correct because Contracted Price substitutes for list price early, so it directly shapes Regular Unit Price when an account has negotiated pricing. E is correct because Discount Schedules apply quantity or amount-driven discounts in that same early stage, making them part of Regular Unit Price rather than later customer or partner discount layers.

Why the others are wrong

  • B. Target Customer Amount is a goal-seeking input used to derive a discount, not a direct contributor to Regular Unit Price.
  • C. Additional Discount fields apply after Regular Unit Price is set, affecting Customer or Net Price rather than the regular stage.

Certified-CPQ-Specialist exam tip

Memorize the early trio for Regular — prorate, contracted, schedule — and push additional and partner discounts later in the waterfall.

8Universal Containers requires its customers to commit to a new 12-month Contract Term whenever requests to modify the existing Contract are made. Which two steps should the Admin take to generate accurate Order records? (Choose two.)
  • Amend the existing Contract and extend the End Date to 12 months from today. Process the Amendment using the normal Quote > Order > Contract flow.
  • Renew the existing Contract, amend the Quote Start Date to today, and modify the Quote Lines to reflect a new 12-month term. Process the Renewal using the normal Quote > Order > Contract flow.
  • Use the Evergreen Contract feature to permit existing Contracts to be extended beyond the original term.
  • Amend the existing Contract, updating all Quote Line Quantities to zero, effectively canceling the Contract. Process the Amendment using the normal Quote > Order > Contract flow.
Answer: A, B

The short version

AB — Amend and extend the end date, or renew with today as the start for a fresh twelve months. Both flows can produce accurate Orders when every modification forces a new twelve-month term, with the choice depending on whether history must continue or restart.

Key concepts in this question

  • Amend and extend: Keeping the same contract and pushing the End Date twelve months out preserves lineage while the normal Quote to Order to Contract flow books the change.
  • Renew and restart: Creating a renewal with Start Date of today and twelve-month lines starts a clean term that also flows through Quote to Order to Contract.
  • Evergreen exclusion: Evergreen extends without a fixed end, which conflicts with the demand for a committed twelve-month term and predictable Orders.

Why AB is correct

The business rule is that any modification triggers a fresh twelve-month commitment with correct Orders, not that only one object flow is allowed. Amending the existing Contract and extending its End Date to twelve months from today satisfies the term while using the standard amendment Quote to Order to Contract path for accurate Order records. Renewing with Start Date moved to today and lines reflecting a new twelve-month term equally satisfies the term through the standard renewal path. Evergreen would leave the term open-ended, and zeroing all lines cancels rather than recommits.

Why the others are wrong

  • C. Evergreen permits extension beyond term without a fixed twelve-month commitment, so Orders stay unpredictable.
  • D. Zeroing every line cancels the contract instead of recommitting it for twelve months with accurate orders.

Certified-CPQ-Specialist exam tip

New twelve-month commitment on every change means amend and extend for continuity, or renew from today for a clean restart.

9Universal Containers (UC) has set the CPQ package settings of both Subscription Term Unit and Subscription Prorate Precision to Month. UC wants to quote a Fixed Price Subscription Product with a Start Date of June 18, 2019 and an End Date of August 21, 2020. The Product record has a Subscription Term of 12, a Pricing Method of List, and a Pricebook Entry of USD 100. What is the Prorated List Unit Price for the Quote Line?
  • USD 118.31
  • USD 116.67
  • USD 125.00
  • USD 100.00
Answer: C

The short version

C — Prorated List Unit Price is USD 125.00. With Term Unit and Prorate Precision in months, the partial June and August months each count as full months, stretching the span to fifteen months and scaling the 100 list by fifteen over twelve.

Key concepts in this question

  • Month precision: Both Subscription Term Unit and Prorate Precision set to Month means any touched calendar month counts as a whole month in the multiplier.
  • Span count: June 18 through August 21 of next year touches fifteen distinct months, not fourteen, because both partial edge months round up.
  • Prorated list math: List 100 times fifteen over twelve equals 125, which becomes the Prorated List Unit Price before waterfall discounts.

Why C is correct

Salesforce proration with Month precision does not day-count the 14-month exact span; it month-counts every calendar month touched by the Start and End dates. From June 2019 through August 2020 inclusive there are fifteen month names, since the partial June and partial August each contribute one. The multiplier is therefore fifteen over twelve, or 1.25, and 100 times 1.25 is 125. The 116.67 alternative divides fourteen by twelve, which would suit a day-precision or exact-month model but contradicts the Month precision setup. So the settled 125 in C reflects the documented month-rounding behavior.

Why the others are wrong

  • A. Uses an unsupported day-rate blend that Month precision never produces for this date span.
  • B. Divides fourteen by twelve, ignoring that partial edge months each count as full months under Month precision.
  • D. Repeats unprorated list and ignores the fifteen-month term that exceeds the twelve-month base.

Certified-CPQ-Specialist exam tip

Month precision means count month names touched, including partial edges, then multiply list by that count over twelve.

10Which two scenarios can be supported using Amendments? (Choose two.)
  • Add new Products; co-terminate to existing Contract
  • Change quantities of existing Products; maintain same discounts as original Quote
  • Change quantities of existing Products; apply different discounts than original Quote
  • Add new Products; use different End Date from existing Contract
Answer: A, B

The short version

AB — Add co-terminated products and change quantities while keeping original discounts. Amendment design preserves existing pricing integrity, so net-new lines can join the contract term and quantities can move without touching locked discounts or dates.

Key concepts in this question

  • Co-terminated adds: New products added on amendment inherit the existing Contract End Date, keeping billing and term aligned.
  • Quantity with same discount: Changing quantity on an existing line keeps its original discount intact, which respects the subscription history lock.
  • Unsupported changes: Applying different discounts to existing lines or giving added lines a different end date breaks term integrity and is blocked.

Why AB is correct

Help and Trailhead amendment material states that changing the discount or standard price fields and dates of existing lines is not supported, because that data already exists on subscriptions and cannot change retroactively. Adding new products co-terminated to the existing Contract creates fresh lines that are free to price, which A allows. Changing quantities of existing products while maintaining the same discounts only scales the locked unit economics, which B allows. Options C and D each demand the forbidden edit: C wants different discounts on existing lines and D wants a divergent end date on new lines. So the AB pair isolates exactly the two supported scenarios.

Why the others are wrong

  • C. Different discounts on existing lines fight the subscription history lock and are explicitly unsupported.
  • D. A different end date on added products breaks co-termination and turns the change into a new quote, not an amendment.

Certified-CPQ-Specialist exam tip

Amendment freedom test: new lines can be added, old lines can scale, but old prices and all end dates never move.

Want the full bank of 235 questions for Certified CPQ Specialist? See all practice exams.