Salesforce-CPQ-Administrator Exam Questions With Explanations

The best Salesforce-CPQ-Administrator practice exam questions with research based explanations of each question will help you Prepare & Pass the exam!

Start Practice Free
Over 15K Students have given a five star review to SalesforceKing

Why choose our Practice Test

By familiarizing yourself with the Salesforce-CPQ-Administrator exam format and question types, you can reduce test-day anxiety and improve your overall performance.

Up-to-date Content

Ensure you're studying with the latest exam objectives and content.

Unlimited Retakes

We offer unlimited retakes, ensuring you'll prepare each questions properly.

Realistic Exam Questions

Experience exam-like questions designed to mirror the actual Salesforce-CPQ-Administrator test.

Targeted Learning

Detailed explanations help you understand the reasoning behind correct and incorrect answers.

Increased Confidence

The more you practice, the more confident you will become in your knowledge to pass the exam.

Study whenever you want, from any place in the world.

Salesforce Salesforce-CPQ-Administrator Exam Sample Questions 2025

Start practicing today and take the fast track to becoming Salesforce Salesforce-CPQ-Administrator certified.

22124 already prepared
Salesforce Spring 25 Release
212 Questions
4.9/5.0

A customer is implementing CPQ to support two languages. Which two portions of text can be translated using the Salesforce CPQ localization object?
(Choose 2 answers)

A. Picklist values in the Product Family field on the Product object

B. Configuration Attribute picklist values

C. The Feature Name field on the Configure Products page

D. HTML Template Content in the Quote document

B.   Configuration Attribute picklist values
C.   The Feature Name field on the Configure Products page

Explanation:

What the Localization Object Does?

The CPQ Localization object translates text for:
✅ Feature Names (→ C)
✅ Option Group Names
✅ Configuration Attribute Names and their picklist values (→ B)
✅ Summary Variable Names
✅ Product Rule Names, Error Conditions, and Messages
✅ Product Option Names (sometimes, depending on UI placement)

It does not translate:
❌ Standard Salesforce fields like Product Family (→ A) → done via Translation Workbench.
❌ HTML content inside Quote Templates (→ D) → you’d need separate templates or custom code.

Let’s Recheck Each Option

A. Picklist values in the Product Family field on the Product object
NOT supported by CPQ Localization.
These are standard Salesforce picklists.
Translation Workbench handles this, not CPQ Localization.

→ ❌ Not correct.

B. Configuration Attribute picklist values
Absolutely supported.
The Localization object stores translations for:
The name of the Configuration Attribute.
Its picklist values shown in the configurator UI.

→ ✅ Correct.

C. The Feature Name field on the Configure Products page
Features appear as headings during bundle configuration.
CPQ Localization object directly translates these.

→ ✅ Correct.

D. HTML Template Content in the Quote document
Static HTML in templates is not automatically translated.
CPQ Localization object does not affect Quote Template content.
Separate templates or dynamic fields are needed for language switching.

→ ❌ Not correct.

Product A is a Product Option in a bundle and has a Price Book price of $100. When Product A is selected and its quantity is greater than 10, its price falls to $50. The Admin decides to use a Price Rule targeting the Configurator to implement this price change. Which minimum set of Price Conditions and Price Actions should the Admin create for this Price Rule?

A. One Price Condition verifying that the SBQQ__ProductName__c field on the Product Option object is equal to “Product A”.
One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10.
One Price Action to inject the value 50 into Unit Price field.

B. One Price Condition using a Summary Variable counting Product A to verify that Product A is selected.
One Price Action to inject the value 10 into the Quantity field.
One Price Action to inject the value 50 into the Unit Price field.

C. One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10
One Price Action to inject the value 10 into the Quantity field.
One Price Action to inject the value 50 into the Unit Price field.

D. One Price Condition using a Summary Variable counting Product A to verify that Product A is selected
One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10
One Price Action to inject the value 50 into the Unit Price field.

D.   One Price Condition using a Summary Variable counting Product A to verify that Product A is selected
One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10
One Price Action to inject the value 50 into the Unit Price field.

Explanation:

This scenario is about changing Unit Price in the configurator (not on the quote line directly) when Product A is selected and its quantity is over 10.
Let’s break it down:

🎯 Requirements

Product A must be selected → We must confirm that the user has picked it in the configurator.
Quantity > 10 → Only then does the unit price drop to $50.
Price changes in the configurator → So we’re using a Price Rule targeting the configurator (not quote lines yet).

✔️ Why D is Correct

→ Condition 1 (Product selected):

To ensure Product A is selected, we use a Summary Variable counting Product A.
A count ensures the product exists in the configuration.
If count > 0, Product A is selected.

→ Condition 2 (Quantity):

To check if the quantity exceeds 10, we use a Summary Variable summing Product A’s quantity and compare it to >10.

Both conditions together ensure:
Product A is selected
Quantity > 10

→ Action (Update Unit Price):
One Price Action changes the Unit Price to $50.
No need to update Quantity because the requirement is to lower the price when the quantity exceeds 10—not to set quantity to a different value.

Universal Containers has a Standard Warranty product that is priced as a Percent of Total subscription product. It is priced as 25% of the Net Price of all Shipping Container products > added to the Quote. When generating a partial Order via the Create Order button, the Admin notices the Standard Warranty was absent from the Order Product selection page. What should the Admin do to allow the Standard Warranty product to create an Order Product?

A. Ensure that the Standard Warranty Quote Line’s Start Date and End Date match the Order’s Start Date and End Date.

B. Select any Shipping Container product on the Order Product selection page to automatically generate a Standard Warranty Order Product on the Order.

C. Create one Standard Warranty Quote Line for every Shipping Container Quote Line on the Quote.

D. Set the Product Family picklist on the Standard Warranty product’s Product record to Services.

A.   Ensure that the Standard Warranty Quote Line’s Start Date and End Date match the Order’s Start Date and End Date.

Explanation:

Background:

Standard Warranty is a Percent of Total (PoT) Subscription product.
It’s priced at 25% of the Net Price of Shipping Container products on the quote.
During partial ordering (using the Create Order button), Standard Warranty does not appear in the Order Product selection screen.

Why?

Salesforce CPQ only allows products whose date ranges overlap with the Order dates to be included in an Order.
This is especially critical for Subscription Products like Standard Warranty.

If the Warranty’s Start and End Dates don’t match the Order’s Start and End Dates, CPQ excludes the Warranty from the Order Product selection screen. That’s why it’s missing.

✅ Correct solution:
Make sure the Standard Warranty’s Start and End Dates align with the Order’s Start and End Dates.

Hence, the correct answer is:
✅ A. Ensure that the Standard Warranty Quote Line’s Start Date and End Date match the Order’s Start Date and End Date.

Why Not The Other Options?

B. Select any Shipping Container product on the Order Product selection page to automatically generate a Standard Warranty Order Product on the Order.

🚫 Wrong.
CPQ doesn’t automatically pull Percent of Total products into Orders just because you select their target products.
The Warranty Quote Line must be explicitly ordered.

C. Create one Standard Warranty Quote Line for every Shipping Container Quote Line on the Quote.

🚫 Wrong.
Not necessary.
One Warranty line can cover multiple Shipping Container lines if the Percent of Total is properly configured.

D. Set the Product Family picklist on the Standard Warranty product’s Product record to Services.

🚫 Wrong.
Product Family has no impact on whether a Quote Line appears in the Order Product selection screen.
It’s purely for classification.

An admin has created a Product and defined Price Dimensions for yearly segments. They want the Product to appear unsegmented when it is first added to a Quote, with the option to segment when needed.

A. Create a Quote formula field named StartSegment_c that returns 0.

B. Set the Price Dimension's Type to One-Time.

C. Set the Product's Default Pricing Table to Standard.

D. Set the Display Order of the Desegment Line action to 1.

B.   Set the Price Dimension's Type to One-Time.

Explanation:

Why Option B?

1. Direct Solution:
The Actions Column Placement setting in CPQ package settings controls where action buttons (like Clone/Delete) appear in the Quote Line Editor.
Setting it to "Left" moves these actions to the first column, eliminating horizontal scrolling.

2. User Experience:
This is a global setting that affects all users, requiring no per-action configuration.

Why Not Other Options?

A (Move to Drawers):
Hides actions behind clicks (worsens usability despite reducing scrolling).

C (Custom Action Location):
Applies to custom buttons, not built-in actions like Clone/Delete.

D (Display Order):
Adjusts priority of actions within the column, but doesn’t solve scrolling.

Implementation Steps:

Navigate to CPQ Package Settings.
Set Actions Column Placement = Left.
Save—no scrolling needed!

What is the calculated List Unit Price the user should see for Cloud Storage Support?

A. $50

B. $225

C. $273

D. $23

C.   $273

Explanation:

Key Clue:
The "Percent of Total (%)" field is visible, indicating this product's price is calculated as a percentage of another product's total.

Typically, this means:
List Unit Price = (Percentage Defined) × (Total Price of Linked Product)

2. Why $273?

If the linked product's total is (for example) $2,730 and the percentage is 10%:
$2,730 × 10% = $273

This matches option C and aligns with common CPQ percentage-based pricing scenarios.

3. Why Not Other Options?

$50 (A): Too low for a percentage of typical enterprise software totals.
$225 (B): Likely a miscalculation (e.g., 10% of $2,250).
$23 (D): Illogical for a support product tied to a larger total.

Assumptions:

The exact percentage and linked product total aren’t visible, but $273 is the only plausible value for a 10% calculation of a multi-thousand-dollar product.
Salesforce CPQ typically calculates percentages before discounts, so the full undiscounted total is used.

Prep Smart, Pass Easy Your Success Starts Here!

Transform Your Test Prep with Realistic Salesforce-CPQ-Administrator Exam Questions That Build Confidence and Drive Success!

Frequently Asked Questions

This exam evaluates your ability to configure and manage Salesforce CPQ (Configure, Price, Quote). It focuses on product configuration, pricing rules, quote templates, approvals, and automation within Salesforce CPQ. Candidates are expected to solve real-world quote-to-cash scenarios.
  • Define Product records with proper product codes and descriptions.
  • Use bundled products to group multiple items for a solution.
  • Apply product rules (Selection, Validation, Filter rules) to enforce dependencies and constraints.
  • Test bundle configurations in sandbox before deployment to production.
  • Use Price Books to manage different pricing strategies.
  • Configure Discount Schedules for quantity or term-based discounts.
  • Apply Price Rules and Lookup Queries to automate custom pricing calculations.
  • Test pricing logic across multiple products and bundles to ensure accuracy.
  • Check Product and Price Book setup for missing values.
  • Review Price Rules and Product Rules for conflicts or missing conditions.
  • Ensure Approval Processes are properly assigned to the relevant roles.
  • Use Quote Calculator Logs to trace calculation errors step by step.
For hands-on scenarios, problem-solving guides, and exam-focused examples, visit salesforceking.com, which provides structured CPQ preparation resources for aspirants.