Salesforce-CPQ-Administrator Practice Test Questions

Explanation:

When using Configuration Attributes in Salesforce CPQ, the Default Field on the Configuration Attribute record is designed to pull the default value from a field on the Quote or Quote Line object — typically a formula field.

1. This formula field is evaluated at the time the configurator loads, which makes it perfect for dynamic default values.

2. It avoids the need for a user to click "Apply Rules" or any additional step.

3. It is the standard and recommended way to default values dynamically into configuration attributes.

❌ Why not the other options?

B. Process Builder: Not appropriate here — Configuration Attributes aren’t standard records like Quote or Quote Line, and Process Builder doesn’t handle this kind of UI initialization reliably.

C. Text field on Quote Line + Price Rule: This works for pricing but not for Configuration Attributes. These don’t directly bind to Quote Line fields like that.

D. Price Rule on Product Option field: This requires user interaction (like clicking “Apply Rules”), and Configuration Attributes don’t get their default values this way. This method is less efficient and error-prone.

Explanation:

In Salesforce CPQ, if you're using Quote Line Groups to represent different delivery locations (or logical groups of quote lines), and you want to split orders by these groups, you must do the following:

1. Set the Order by Quote Line Group checkbox (field on the Quote) to TRUE.
This tells CPQ to generate separate Orders based on each group in the quote.

2. Then set the Ordered checkbox on the Quote to TRUE.
This triggers CPQ to automatically create the Order records (and splits them accordingly).

This is the automated and supported way to generate separate orders from Quote Line Groups.

❌ Why not the other options?

A. Only clicking “Create Order” is not sufficient unless the Ordered field is TRUE, especially in automated split scenarios.

B. There's no picklist field called “Order By” on the standard CPQ package — this is incorrect.

D. SBQQ_Group__c is a reference to Quote Line Group but setting that value directly without using the proper Order by Quote Line Group logic is unsupported and incorrect.

Explanation:

In Salesforce CPQ Advanced Approvals, when multiple Approval Chains are triggered for a single record (like a Quote), they are all evaluated and initiated in parallel.

1. Each Approval Chain represents an independent path of approval.
2. These chains are not sequential relative to one another.
3. Within each chain, however, the steps (Approval Steps) are executed in sequence, but chains themselves run concurrently.
4. The approval process completes only when all chains have been approved.

So, even though you see the chains left-to-right on the Preview Approvals page, the order of display has no impact on processing order.

❌ Why not the other options?

B. The left-to-right display order is only visual and does not dictate execution.

C. Each chain runs independently, so the lowest Approval Step in one chain doesn’t affect the other chains.

D. There’s no concept of "Final Approval Step" affecting cross-chain order. Each chain finishes when its last step is approved.

Explanation:

Universal Containers wants to price a product as 10% of the total of all other fixed-price products on a quote. This scenario uses Percent of Total (PoT) pricing, which is a built-in Salesforce CPQ feature.

To make Percent of Total pricing work, the product must be:
Marked as a Percent of Total product, and
Have its Pricing Method set to Percent of Total.

🔍 Analysis of Options:

✅ A. Pricing Method = Percent of Total, Subscription Pricing = blank
This is the most common and correct setup for a non-subscription product using Percent of Total.
Subscription Pricing being blank means it’s treated as a one-time product.

✅ C. Pricing Method = Percent of Total, Subscription Pricing = Custom
This is also valid, especially if this product is a subscription-based product and needs to follow custom proration or billing rules.
Subscription Pricing = Custom allows more flexibility while still honoring Percent of Total logic.

❌ Why not the other options?

B. Pricing Method = Custom, Subscription Pricing = Custom
This skips Salesforce CPQ’s built-in PoT functionality, so you'd need custom logic/rules to calculate 10% — not recommended for a standard use case.

D. Pricing Method = List, Subscription Pricing = Percent of Total
List pricing means fixed price, not dynamic.
Subscription Pricing = Percent of Total is not a valid setting — it doesn't work unless Pricing Method is already Percent of Total.

Explanation:

In Salesforce CPQ, when users view the Product Selection page, products are displayed based on their:
1. Product Family (if filtered),
2. Then by Sort Order (ascending numeric),
3. Then by Product Name (alphabetically), if Sort Orders are equal or blank.

To ensure “Shipping Plus” appears at the top, you must:
1. Set its Sort Order to the lowest numerical value among all products (e.g., 1 or 0).
2. This explicitly tells CPQ to display this product before others on the selection screen.

❌ Why not the other options?

A. Null Sort Order – If multiple products have null Sort Order, they’ll be sorted by name, not guaranteed top position.

C. Product Code – Product Code is not used in determining display order on the selection screen.

D. Null Product Code – This has no effect on the sort/display order in the Product Selection screen.

Explanation:

1. Business Requirements:
USD has two price sets (America vs. Asia Pacific).
EUR & GBP have one price set each (Europe).
Multi-Currency is enabled.

2. Why Option C is Correct:
America - USD: Separate USD prices for American customers.
Asia Pacific - USD: Different USD prices for APAC customers.
Europe - EUR & Europe - GBP: Dedicated price books for European currencies.
This ensures regional pricing differences (especially for USD) are maintained.

Why Other Options Fail:

A: Only one USD price book—cannot distinguish between America & APAC USD prices.
B: Groups by region but doesn’t account for multiple USD price sets.
D: Merges all standard prices into one book, losing regional USD differentiation.

Key Considerations:

Currency-Specific vs. Region-Specific Pricing:
Since USD prices vary by region, you need separate USD price books for America and APAC.
EUR/GBP prices are region-agnostic (Europe only), so one book per currency suffices.

Price Book Hierarchy:
Assign the correct price book based on the customer’s region + currency.

Explanation:

Step-by-Step Explanation:

1. Understand the Pricing Configuration

From the table:

Product A (Platform License):
Subscription Pricing: Fixed Price
List Unit Price: $200/month
Net Total (24 months): $2,400 (implies a 50% discount from the full List Price).

Product B (Maintenance Subscription):
Subscription Pricing: Percent Of Total
Base: Product A
Percent Of Total (%): 10% (applied to Product A's Net Total).

2. Calculate Product B’s Net Total

Since Product B is 10% of Product A’s Net Total:
Net Total (Product A): $2,400
Net Total (Product B):
10% of \$2,400 = \$240
Wait! But the options don’t include $240.

3. Recheck the Configuration
The table shows:
Percent Of Total Base: Product A (likely refers to List Price, not Net Total).
Percent Of Total (%): 10% (applied to Product A’s List Price × Term).

Revised Calculation:
List Price (Product A): $200/month

Total List Price (24 months):
\$200 × 24 = \$4,800

Product B’s Net Total (10% of $4,800):
10% of \$4,800 = \$480

4. Why Not Other Options?
B. $2,400: Matches Product A’s Net Total (incorrect for Product B).
C. $12,000: No logical basis (would require 50% of $24,000, which is irrelevant).

5. Final Answer:
A. $480.00 (10% of Product A’s full undiscounted value over 24 months).

Key Takeaway:
Percent Of Total for Product B is based on Product A’s List Price × Term, not its Net Total.
The 50% discount on Product A does not affect Product B’s calculation.

Explanation:

1. Scenario:
Prices are hidden on the Configure Products page in Salesforce CPQ.

2. Root Cause:
The Unit Price field must be included in the Option Configuration Field Set to be visible during product configuration.
Field Sets control which fields display on the configuration page.

3. Solution:
Navigate to Setup → Field Sets → Product Option → Option Configuration.
Add the Unit Price field to the Field Set.

Why Not Other Options?

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.

Explanation:

When you add a custom lookup field (e.g., to Campaign) on the Quote Line and include it in the Line Editor Field Set, CPQ allows users to search for records — but only if Salesforce CPQ knows which fields to search and display.

To enable this:
You must create a Field Set on the target object (Campaign).
The Field Set must be named exactly: CPQ_Lookup
Add fields like Name, Start Date, Status, etc. to this field set.

If this field set doesn't exist, users will get a warning message like:
"Warning: No CPQ_Lookup field set found on [Object]"

This is documented Salesforce CPQ behavior.

❌ Why the other options are incorrect:

A. Create a twin field on Campaign:
Not necessary. Twin fields are used for syncing Quote to Quote Line, not lookup resolution.

C. Add the name of the lookup field to the Quote’s Line Editor Field Set:
The field is on Quote Line, not Quote, so this has no effect.

D. Add the lookup field to the Quote Line page layout:
That only affects the record detail page, not the Quote Line Editor UI.