Sales-Admn-202 Salesforce Certified CPQ Administrator Free Practice Exam Questions (2025 Updated)

 Scenario:

Automatically select the Diamond Warranty Option in the child bundle if Premium Container is selected in the parent bundle and no warranty is selected.

 Solution:

Child Bundle Condition Level = 1: Ensures the condition applies at the child bundle level.

Child Bundle Action Level = None: Prevents overwriting user-selected options but enables automatic defaulting when none are selected.

 Why Other Options Are Incorrect:

B & C: Setting inappropriate levels may lead to overwriting user selections or incorrect rule execution.

D: Setting both levels to None results in no action or condition enforcement.

 Salesforce CPQ Reference:

Configuration rules and child bundle handling are outlined in CPQ Bundle Configuration Guidelines ​

 Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

 Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

 Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

 Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

 Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.

In Salesforce CPQ, the Option Layout field on the Product record determines how bundle options are presented in the configurator. To allow users to view all available and selected options by scrolling on a single page, the "Sections" layout is ideal. This layout organizes options into collapsible sections based on Product Features, keeping everything visible on one page without requiring navigation steps like a wizard. Option A (Wizard) presents options step-by-step across multiple pages, which doesn’t meet the single-page requirement. Option B (assigning all options to one feature) limits organization and doesn’t address the layout requirement. Option C (Dynamic selection method) controls runtime behavior of options but doesn’t influence the single-page scrolling display. Salesforce CPQ documentation confirms that the "Sections" layout supports a scrollable, single-page view.

 Scenario Breakdown:

Product A has a base list price of $100.

A quantity of 15 is entered on the quote.

Gold Hardware Maintenance Discount applies because contracted pricing is enabled.

Discount for the quantity range (11–20) is 15% (as shown in the table).

 Net Price Calculation:

List Price = $100

Discount = 15%

Quantity = 15

Net Total Price = $100 × 15 × (1 - 0.15) = $1,275.

 Justification for Selected Discount:According to Salesforce CPQ guidelines, when contracted pricing applies, it takes precedence over other Discount Schedules. The Gold Discount Schedule is therefore applied.

 Testing and Validation:Test the configuration using a sample quote to ensure the correct schedule is applied and the net total price matches the expected value.

 Requirement:

Calculate the prorate multiplier when a subscription product’s End Date differs from the Quote’s End Date.

 Solution:

CPQ uses the Quote Line date (specific to the subscription product) to calculate the prorate multiplier. This ensures alignment with the subscription term.

 Why Other Options Are Incorrect:

A & D: Earliest or latest dates do not determine prorate multipliers.

B: The Quote date applies to the Quote as a whole, not individual subscription products.

 Salesforce CPQ Reference:

Prorate multiplier calculations are outlined in Subscription Management Guidelines ​.

The order of precedence for evaluating subscription dates is as follows

(1) Quote Line,

(2) Quote Line Group, and

(3) Quote

https://help.salesforce.com/s/articleView?id=000383503 &type=1

 Requirement:

Track individual serial numbers for each unit of Product A sold.

 Solution Details:

Asset Conversion Field determines how assets are created from Quote Lines.

Setting Asset Conversion to One Per Unit creates one Asset record for each unit sold, allowing tracking of individual serial numbers.

 Implementation:

Navigate to the Product Record for Product A.

Set Asset Conversion to One Per Unit.

 Justification:

This setup aligns with Salesforce CPQ's approach for granular tracking of Assets associated with product sales​​.

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.

 Requirement:

Ensure the price of Tiny Boxes ($0.005) is handled with proper decimal precision.

 Solution:

Adjust the Unit Price Scale to 3 in the Pricing and Calculation Package Settings, enabling Salesforce CPQ to handle prices up to three decimal places.

 Why Other Options Are Incorrect:

A: Field-level precision on Quote Line does not control pricing precision.

C: The Product record's Unit Price Scale cannot override global settings.

D: Price Rules are unnecessary for simple decimal precision adjustments.

 Salesforce CPQ Reference:

Decimal precision configuration is described in CPQ Pricing Settings ​.

 Requirement Overview:

Sales reps want the Square Footage value on a Configuration Attribute to persist when renewing a Quote.

 Twin Field Mechanism:

Twin Fields ensure that data is retained and mapped between related objects.

Creating Twin Fields on the Asset and Subscription objects allows the Square Footage value to be carried forward during renewals.

 Steps to Configure:

Create a custom field for Square Footage on the Asset and Subscription objects.

Ensure the API names of these fields match the Configuration Attribute API name.

Test the renewal process to confirm the value persists.

 Validation:

The Square Footage value should automatically populate in the renewal Quote without manual entry by the sales rep​​.

 Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

 Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

 Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

 Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ​.

 Requirement Overview:

Universal Containers needs to send Approval Requests to both the Deal Desk and Finance teams simultaneously.

 Solution:

Use Advanced Approvals to configure multiple Approval Steps within a single Approval Chain.

Set the steps to run in parallel to minimize the time required for approval.

 Steps to Configure:

Navigate to Advanced Approvals in Salesforce CPQ.

Create an Approval Chain with two steps: one for the Deal Desk and one for the Finance team.

Configure both steps to run in parallel by assigning them the same step number.

 Simplification Method:

By adding the PDF as a required Additional Document in the Quote Template, Salesforce CPQ ensures the PDF is automatically included with each generated Quote.

 Steps to Configure:

Navigate to the Quote Template.

Add the PDF file under the Additional Documents section.

Mark it as required for automatic inclusion.

 Salesforce CPQ Reference:

The Additional Documents feature simplifies document management in Quote Templates ​.

 Requirement:

Different profiles need to see distinct sets of fields in the Quote Line Editor.

 Solution:

Create two field sets on the Quote Line object, one for each profile.

Use a text formula field named EditLinesFieldSetName on the Quote object to dynamically return the appropriate field set name based on the user’s profile.

 Why Other Options Are Incorrect:

A & B: Field sets must be created on the Quote Line object, not the Quote object.

D: This duplicates C but introduces a typo or incorrect description in the explanation.

 Salesforce CPQ Reference:

Field set configurations for the Quote Line Editor are detailed in CPQ Field Configuration Documentation ​.

 Requirement Overview:

Each sales team needs access to a specific subset of products without requiring separate Price Books.

 Solution:

Use multiple bundles with validation Product Rules to restrict access to specific products based on user criteria (e.g., Profile or custom field).

This avoids the need to create and manage separate Price Books for each team.

 Steps to Configure:

Create a bundle for each subset of products.

Use Product Rules to validate and restrict access based on sales team criteria.

 Validation:

Test the Product Selection page to ensure that each sales team can access only their specific subset of products.

 Scenario Overview:

The Custom value for the Condition Met field allows for complex logical operations using a mix of AND/OR across multiple Price Conditions.

 Use Case:

When a Price Rule has three or more conditions and requires specific combinations of AND and OR logic, the Custom option is required.

 Implementation:

Navigate to the Price Rule.

Set Condition Met to Custom.

Specify the logic (e.g., (Condition 1 AND Condition 2) OR Condition 3).

 Validation:This ensures Salesforce CPQ evaluates the Price Rule as intended, supporting mixed logical conditions.

To set a dynamic default value for a Configuration Attribute when the configuration page loads, automation must populate the associated Product Option field automatically. Option A uses a Flow to update the Product Option field tied to the Configuration Attribute, triggered upon record creation (e.g., when the Quote Line is initiated), ensuring the value is set dynamically at page load. Option B (Price Rule) requires manual user action ("Apply Rules"), which doesn’t meet the "moment the page loads" requirement. Option C (Quote formula field) isn’t directly supported as a default source for Configuration Attributes without additional customization. Option D (Quote Line field with Price Rule) lacks real-time dynamism and alignment with page load timing. Salesforce CPQ documentation highlights Flows as a robust solution for dynamic defaults.

 Scenario:

A Price Rule utilizes a Lookup Object and Lookup Queries, and multiple records meet the criteria for a single Quote Line.

 Behavior:

When more than one lookup record meets the criteria, Salesforce CPQ does not apply any value to the Target Field. Instead:

The Target Field retains its original value.

An error message is displayed in the Quote Line Editor, notifying the user of the conflict.

 Why Other Options Are Incorrect:

A & D: Salesforce CPQ does not resolve ties by sorting records alphabetically.

C: The system does not apply values based on record creation date.

 Salesforce CPQ Reference:

Lookup Queries behavior and error-handling are outlined in CPQ Price Rules Configuration Guidelines ​.

 Requirement:

Hide products with the Product Family "Software" when a Configuration Attribute is set to "Perpetual."

 Solution:

Use an Error Condition to evaluate the Product Family value on the Product Option record.

Configure a Product Action to Show all products except those with the Product Family "Software."

 Mechanism:

The Error Condition evaluates the Configuration Attribute's value against the Product Option.

The Product Action ensures visibility is dynamically controlled based on the evaluated condition.

 Salesforce CPQ Reference:

Error Conditions and Product Actions are key components of Product Rules in CPQ to implement dynamic product behavior ​.